Mike Griffiths
asserts that when everyone on a
team is recognised and treated as a volunteer their productivity
far exceeds that of team members working for reward. He uses the
diagram below to illustrate the scale of an individual's
contribution to the team. (I've included Mike's descriptions):
- Undermining/Resistance : People negatively impact the project, either intentionally or through misguided objectives and actions, their presence on the team actually has a net drain on project productivity.
- Passive Compliance : People do generally work on to-do items, but without much thought and without any passion for the task or goal. (This is all too common in large organizations where for team members feel like cogs in a machine they have very little say in.)
- Active Participation and Committed Dedication : This is where the good work starts getting done. People are engaged personally instead of merely by job obligation and are truly thinking about how best to solve problems and find new solutions. With brain engaged and a sense of ownership for task, the net contribution to the project are orders of magnitude higher than Passive Compliance contributors.
- Passionate Innovation : This occurs when the task becomes the all consuming passion for those involved. Usually witnessed in start-ups and by partners in a business who's vision is being executed, passionate innovation can bring exceptional results and solutions.
2 Comments
What if they are volunteered on something that is not completely aligned with what the team need?
Of course there will be A LOT of work going on but what about waste?
Volunteers tends, by nature, to work VERY HARD but on what they personally feel is good, it might be the case this is not completely correct.
PierG
http://pierg.wordpress.com
I'm not sure you meant: "they are volunteered onto something". This suggests they are told to work on something by someone else, which, of course, is not volunteering. I'll assume you meant: "they volunteered to work on something not completely aligned with what the team need". It shouldn’t be about what the team needs. The priority is to deliver what the customer wants. This should be captured in a goal for each iteration to which everyone on the team publicly commits. It's the scrum master's job to ensure the team has everything they need to do deliver that.
In a jelled team, there exists a social responsibility - a powerful force that holds the team together and helps prevent individual team members following their own course. Collectively, the team holds each team member accountable.
Work that doesn’t contribute to the iteration goal should not get through the planning game. And if someone has decided, on their own, to do some work that is not part of the iteration (when there is other value delivering work to be done to which the team committed), the team must take appropriate action to get that person back working towards the shared iteration goal.