The Rules of Scrum: PBIs are written as User Stories (“As a ___ I can ___ so that ___”)

The User Story is a tool developed with Extreme Programming that is almost universally accepted as part of Scrum.  The User Story format is an effective way of communicating end user value to the Scrum Team.  The first blank is a user (a person, not a system), the second blank is the action of the story (unique), and the third blank is the benefit (for any stakeholder, and outside the system).  A User Story is made up of three “C’s”: Card, Conversation and Confirmation.  The Card is the written version of the story (usually a physical card on the wall).  It is considered to be an “invitation to a conversation”.  The Conversation is where the real value resides and potentially involves all stakeholders. The Conversation can cause changes to the Card.  Confirmation is the acceptance criteria that, when tested against, confirms the valuable result of the story.  A User Story is an extremely effective way of creating light and conversational PBIs – this is why many Scrum teams use them.  Another way to view User Stories is that it tells any reader the “who”, the “what”, and the “why” – who cares about this, what is the need/action, and why does the person want this.  This is just enough information to make sure that an effective conversation occurs.

Affiliated Promotions:

Try our automated online Scrum coach: Scrum Insight - free scores and basic advice, upgrade to get in-depth insight for your team. It takes between 8 and 11 minutes for each team member to fill in the survey, and your results are available immediately. Try it in your next retrospective.

Please share!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.