One of the secrets to success for many successful project managers is a tight breakdown of roles and responsibilities.
(If you aren't familiar with the Role Assignment Matrix (which is probably a clearer and less ambiguous technique than a RASCI) you can read more about it here and here.)
So, what's up for a scrum team? How do you assign responsibilities to a group of people? By making everyone responsible aren't we making no-one responsible? Isn't this the underlying problem behind the tragedy of the commons?
Well, no actually. Because people are part of a community. And groups can be accountable.
What does matter is the size of the group and the culture that links them. Small groups are better able to build a strong culture. People talk about groups of 5-9 as optimal sizes for working together on common tasks. After that size the communication overhead breaks down. And so does the group identity. All of a sudden there are two groups, and divergences in culture start to emerge as people identify with one group over another.
But.
Small teams can be accountable for outcomes. And of the culture is supportive, large groups can work well together also. Use judgement to size a team. See if there are groups or factions emerging and think about breaking it into multiple teams.
1 April 2010
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
I'm a massive Lord of the Rings fan. Every year, I spend part of my holiday vacation rewatching the 12 hours of the blu-ray extended edit...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...

Regardless of the size of the team, the key is to make the individual members of the team feel responsible for its success or failure, and to instill a common sense of direction in each team member.
ReplyDeleteD