Do you know that every user story should have an owner?

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.

Published on 17 March 2010

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/OOCAnXLzP9r

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

Rule added to Rules to better Scrum with TFS

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

Connect with Martin Hinshelwood

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.

Our Happy Clients

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.