TL;DR; Assigning an owner to each user story in Scrum ensures clear responsibility, better communication, and accountability throughout the sprint for both teams and stakeholders.
When you are building complicated software and working with customers it is always nice for them to have some idea on who to speak to about a particular story during a sprint.
Update 14th April 2010
In order to achieve this one of the Team takes responsibility for “looking after” a story” a story and manages it to completion. They will collect all of the “Done” emails and make sure that everyone follows the Done criteria identified by the team as well as answering any Product Owner queries.
Figure: Bad example, the product owner is not sure who to speak to.
Figure: Good example, the product owner can now see who he should speak to and developers know where to send done emails.
Technorati Tags: SSW Scrum SSW Rules SP 2010 SharePoint
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Alignment Healthcare
NIT A/S
Boeing
Hubtel Ghana
Kongsberg Maritime
New Signature
Epic Games
Philips
Slaughter and May
Workday
Ericson
Big Data for Humans
Lockheed Martin
ALS Life Sciences
Flowmaster (a Mentor Graphics Company)
Deliotte
Healthgrades
Brandes Investment Partners L.P.
Washington Department of Enterprise Services
New Hampshire Supreme Court
Washington Department of Transport
Nottingham County Council
Ghana Police Service
Royal Air Force
Emerson Process Management
CR2
Illumina
NIT A/S
Ericson
Graham & Brown