At QCon London 2009, Jospeh Pelrine gave a talk about coaching self organizing teams. The main point behind the talk was a metaphor comparing coaching to cooking chicken soup. The team is the ingredients and the coach is the cook. The cook has to constantly control the heat. There are several stages:
1. Burning (stressed, burn out, keep fighting).
2. Cooking (border of chaos or anarchy). This is when the team is most creative.
3. Stagnating. What was good is becoming bad and moldy. People stop coming to meetings, no one writes tests, and everybody is procrastinating.
4. Congealing. It’s like jelly. There is still some flexibility, but it is starting to take hard shape. Team is disinterested, there is no ongoing discussion.
5. Solid/Frozen. This is the way things get done here, 9 to 5, no initiative, do my job and leave.
The high and low stages show similar behavior patterns. The key is to control the heat and to keep the team cooking by managing time and tasks.
This presentation is available on InfoQ at http://www.infoq.com/presentations/coaching-self-org-teams
Showing posts with label QCon2009. Show all posts
Showing posts with label QCon2009. Show all posts
Friday, November 13, 2009
Monday, August 17, 2009
Navigating the Rapids - Real World Lessons in Adopting Agile
Sam Newman talks about lessons learned while transitioning clients to agile practices. He 1st recalls a story where he failed to educate stakeholders upfront that he will share with them the good news and the bad news on a regular basis in hope that they can step in and help with the bad news when needed. Next he discusses how when adopting agile productivity 1st goes down as the team is adapting to the new practices. Patience is needed before there is a clear sign of productivity increase. Finally he describes how different clients prefer to see data in different ways.
He summarizes the lessons learned as:
1. Educate stakeholders about early signs of pain
2. Bite of something small – Earn trust early: Need to show that things are better (hard numbers, metrics).
3. Track your data and know how to present it
This presentation is available on InfoQ at http://www.infoq.com/presentations/navigating-agile-rapids
He summarizes the lessons learned as:
1. Educate stakeholders about early signs of pain
2. Bite of something small – Earn trust early: Need to show that things are better (hard numbers, metrics).
3. Track your data and know how to present it
This presentation is available on InfoQ at http://www.infoq.com/presentations/navigating-agile-rapids
Subscribe to:
Posts (Atom)