Comments on: Updated Scrum Board Cheat Sheet with Story Owner http://maxheapsize.com/2009/03/12/updated-scrum-board-cheat-sheet-with-story-owner/ Oliver Wehrens on Programming and Agile Sun, 24 Jul 2011 10:50:52 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Oliver http://maxheapsize.com/2009/03/12/updated-scrum-board-cheat-sheet-with-story-owner/comment-page-1/#comment-32 Oliver Fri, 13 Mar 2009 07:11:03 +0000 http://maxheapsize.com/?p=119#comment-32 This story owner is there to more or less have an overview what kind of resources this story needs. Since at least 70% of the team is working on the top most story almost everybody knows what to do. If more resources are needed people from the next story will switch to this one and help out. It's the duty of the story owner to bring them up to speed. Writing down one person is hopefully avoiding dialogs like: 'I thought you did it", "Na, I thought you talked to Joe". The story owner role can be fulfilled by anyone working on that story the whole time. If this person goes away from some reason someone else can take over with no problems. This story owner is there to more or less have an overview what kind of resources this story needs. Since at least 70% of the team is working on the top most story almost everybody knows what to do. If more resources are needed people from the next story will switch to this one and help out. It’s the duty of the story owner to bring them up to speed. Writing down one person is hopefully avoiding dialogs like: ‘I thought you did it”, “Na, I thought you talked to Joe”.
The story owner role can be fulfilled by anyone working on that story the whole time. If this person goes away from some reason someone else can take over with no problems.

]]> By: j pimmel http://maxheapsize.com/2009/03/12/updated-scrum-board-cheat-sheet-with-story-owner/comment-page-1/#comment-31 j pimmel Fri, 13 Mar 2009 00:04:20 +0000 http://maxheapsize.com/?p=119#comment-31 You might find that once the team develops a degree of comfort in delivering finished work of high enough quality that you can indeed rotate ownership and collectively own the stories. A major downside of any individual owning a story through its life is that if that person is otherwise called away for other duties, is sick or away, the void cannot easily be filled by the ream. Collective ownership is best experimented with once you have some momentum and maturity as a team to move onto more challenging <a href="http://www.agileinaction.com/2008/04/people-do-pair-programming.html" rel="nofollow">collective ownership</a>. I would also couch the above by saying that it would be much harder to achieve collective code/story ownership without continuous pair-programming. You might find that once the team develops a degree of comfort in delivering finished work of high enough quality that you can indeed rotate ownership and collectively own the stories.

A major downside of any individual owning a story through its life is that if that person is otherwise called away for other duties, is sick or away, the void cannot easily be filled by the ream. Collective ownership is best experimented with once you have some momentum and maturity as a team to move onto more challenging collective ownership.

I would also couch the above by saying that it would be much harder to achieve collective code/story ownership without continuous pair-programming.

]]>