The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.


Games Are for Teams

Posted by admin under Scrum Basics, Scrum Discussion

I’ve been hearing more and more about Certified Scrum Trainers (CSTs) who are using lessons from outside of software development to inspire their students. Most recently, I’d heard about a presentation given by Danube CST Michael James at last fall’s Stockholm Scrum Gathering, in which he shared some fascinating findings from high-performing teams in aviation, psychology, and jazz. Not long after, I ran across this article on the SD Times web site in which Jeff Feinman reports on how some trainers are using principles from other fields to help their students better understand Scrum. For example, one trainer mentioned in the story has attendees engage in exercises drawn from improvisational theater, another leads participants through a series of stretches.

So what’s the value of teaching teams about Scrum using these methods? For one thing, it draws participants out of their shells and gets them to start talking to one another. That might not sound like a big deal, but, given that software developers are often introverted personality types, it’s a big step toward getting a team to behave like one. In a bigger sense, it gives participants experience working outside of their comfort zones. This is good practice for team members at organizations that are about to transform through Scrum. Leaving familiar working behaviors behind for new, sometimes challenging processes is scary for a lot of team members. So a no-pressure or goofy team-building exercise can break that ice and show a team member that a break from the norm can be exhilarating—or even lead a team to accomplish what they never dreamed was possible.

How has your Scrum team helped members acclimate to new processes? Have those efforts worked? How did team members respond? Please share your experiences in the comments section.



Universal Impediments

Posted by admin under Scrum Basics

Over at Computerworld’s web site, I just read an interesting interview with Christophe Louvion, who has been serving as a ScrumMaster at online ad network Gorilla Nation for about a year. Louvion doesn’t get too deep into what it takes to transform an organization to Scrum, but his answers will likely remind you ScrumMasters who read this blog that the challenges you face are not limited to your organization. For example, he had to convince management to re-organize teams to be cross-functional, regrouping teams by “product and value streams”; he still has to persuade middle-managers to be “impediment-removers,” not taskmasters; and he still prefers developers with team-friendly soft skills over genius coding knowhow. If these sound like familiar scenarios (and I’m sure they do), at least you’re not alone… 🙂