Remember in school, there was a guy who always looked for feedback for everything he did? He checked in to make sure it was cool with the group. If the group liked his action, he did it more and, if not, he tried something else. I found him annoying. I always thought the rebels were cool.
But I’m wondering if this feedback-seeking personality is actually good in the context of Agile? From pair programming, TDD, continuous integration, stand ups, sprints, retrospectives and so forth, Agile philosophy is built on communication and feedback. That guy would be a natural in this environment. He would be a role model. As for the rebel dude, he would be working at KFC making double downs.
“W00t!! Just found a team that’s working on one story at a time to completion!! HAPPY HAPPY JOY JOY!!”
There are 8 people in the team including the product owner.
I tweeted him back and we agree that this approach makes the team better than taking on more stories. This is a great exercise of a newly formed team. The benefits are:
1. Everyone shares the same experience through the whole process — from start to finish. When all 8 people are in it together, it builds team confidence and trust.
2. When all 8 people are working on one story, team dynamics get sorted out faster than if the team is working on multiple stories (you can avoid/defer conflict by choosing to work on a story with the team member that you like).
3. Knowledge on the development process is shared faster.
4. More than likely, the team will go out for drinks after a story is done, which means more team building. Yeah!
This great presentation reminds me that sometimes stopping is just as valuable as forging head.
An agile team is made sustainable because there is a deliberate pause built into the development process. This allows the people involved in the project to reflect on the progress — what went well, what needs to be improved, etc. Similar to a person, a team can have a full system failure without some pauses.