Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Writing Good User Stories (Hint: It's not about writing)

1,025 views

Published on

User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.

Published in: Technology
  • Hello! Who wants to chat with me? Nu photos with me here http://bit.ly/helenswee
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Writing Good User Stories (Hint: It's not about writing)

  1. 1. writing good Building Sustainable Agile Solutions one80services.com | info@one80services.com | 1-844-80-AGILE. hint: it not about writing Andre Simones Nick Kramer user stories
  2. 2. one80services.com Building Sustainable Agile Solutions The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Working software over comprehensive documentation Individuals and interactions over processes and tools Customer collaboration over contract negotiation Responding to change over following a plan
  3. 3. one80services.com Building Sustainable Agile Solutions A Quick History Lesson I need… okay, cool.
  4. 4. card conversation confirmation a brief, simple statement from the perspective of the user a story is an invitation for a conversation each story should meet all expectations one80services.com Building Sustainable Agile Solutions User Stories
  5. 5. card conversation confirmation one80services.com Building Sustainable Agile Solutions Not Documentation User Stories a brief, simple statement from the perspective of the user a story is an invitation for a conversation each story should meet all expectations
  6. 6. story title as a <type of user> I want to <action> so that <benefit> w w w who what why one80services.com Building Sustainable Agile Solutions User Stories
  7. 7. User Stories story title a <type of user> wants to <action> In order to <benefit>, w w w who what why one80services.com Building Sustainable Agile Solutions (Alternate Format)
  8. 8. I N V E S T independent negotiable valuable estimable small testable Follow the INVEST guidelines for good user stories! one80services.com Building Sustainable Agile Solutions
  9. 9. one80services.com Building Sustainable Agile Solutions The “Agile Requirements” Hierarchy (Kinda) Security Secure Connection User Management User Access Login Forgot Password Theme Epic Story
  10. 10. Scrum Master Product Owner Developers one80services.com Building Sustainable Agile Solutions Who “Writes” User Stories?
  11. 11. one80services.com Building Sustainable Agile Solutions Exercise: What’s wrong with these stories?
  12. 12. one80services.com Building Sustainable Agile Solutions Exercise: What’s wrong with these stories? As a customer service rep, I need an interface so that I can access customer data. As a user, I need to administer accounts so that I can control account access. story one story two
  13. 13. one80services.com Building Sustainable Agile Solutions As a developer, I need to build a form so online shoppers can place orders. As the Product Owner, I want social networking to be part of the application. story three story four Exercise: What’s wrong with these stories?
  14. 14. one80services.com Building Sustainable Agile Solutions The user needs to be able to send messages. The system needs to route messages to the recipient story five story six Exercise: What’s wrong with these stories?
  15. 15. one80services.com Building Sustainable Agile Solutions When Should You Decompose Stories? You can’t complete the story in one iteration. The User Story seems “vague” or can’t be estimated. A common technique is to split this into two stories. One “research” or “spike” story that is time-boxed and the other story to implement.
  16. 16. one80services.com Building Sustainable Agile Solutions User Story Slicing Techniques Operation or action: • View • Add • Delete • Modify Business rules: • Reset password with link • Reset password by answering security questions
  17. 17. one80services.com Building Sustainable Agile Solutions User Story Slicing Techniques Simple first, more complicated later: • Create account by entering username password • Create account by signing in with Facebook DON’T slice by “system”, i.e. don’t slice “horizontally”.
  18. 18. one80services.com Building Sustainable Agile Solutions Definition of Ready I Follows INVEST guidelines Sized by the team Just enough acceptance criteria Value is clearly understood SME contacts Ready (Other)
  19. 19. one80services.com Building Sustainable Agile Solutions Definition of Done Automation done at appropriate levels All tests pass User Documentation updated as necessary Pair programming preferred (peer reviewed at minimum) Code checked in and associated with item in TFS/Git, etc. Done Reviewed by PO in integration environment (Other)
  20. 20. writing good Building Sustainable Agile Solutions one80services.com hint: it not about writing thanks for joining us today! Andre Simones Nick Kramer user stories

×