How do you measure the individual contributions of each member of an agile software delivery team?
It’s a trick question.
You can’t.
Agile software delivery is a team sport. The team succeeds or fails together.
If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.
Top comments (6)
You can measure both: success of team and contribution of each person in the team.
In highly collaborative work, which software engineering is, when done right, the ability to measure individual contributions means the team is dysfunctional.
I disagree, even in highly collaborative project implementation of each feature is done by one or couple developers. If version control system is linking to task manager system (e.g. by ticket ids in branch names) you can easily track level of commitment (e.g. by author of commit and story points of the task).
What you have described is definitely NOT highly collaborative.
You've described scatter/gather, which is very individualistic.
It's common, of course, but not highly collaborative.
Highly collaborative, by definition, means that many people are collaboratimg constantly. This may mean ensemble programming, for example.
In highly collaborative work, it's literally impossible to determine who did what.
You'll hear people say things like "I'm not sure whose idea that was" or "We built that together".
Ok, so based on your definition software engineering is not highly collaborative.
I heard may excuses like that, "I'm not sure whose idea that was" is my second favourite just after "there's no time for write tests".
No. Your version of software delivery isn't highly collaborative.
The version you describe IS common. But it's not the only way. And it's definitely not the best way in most cases.