User Stories: Stories for Grown-Ups

  • View
    7.736

  • Download
    2

Embed Size (px)

DESCRIPTION

Douglas Talbot & Sandy Mamoli One of the most fundamental problems facing a project is how you decide on, document, and manage your requirements. Obviously Agile software development promotes handling this very differently than a Waterfall approach. One mechanism used by Agile projects to track requirements is the "User Story" - but what are they, how are they created, who uses them, when and how, within the development cycle?

Text of User Stories: Stories for Grown-Ups

  • 1.Stories for Grown-ups Inspired by Mike Cohn and Kelly Waters thank you

2. Fixed written requirements 3.

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

Agile Values 4. Communications challenge 5. Collaboration 6. A continuum 7. User stories: an improvement 8. Timeline Epics & Stories Stories & Tasks Stories & Tasks Implemented Stories 9. Getting to User Stories 10. Epics

  • Compound epics
  • Complex epics
  • Placeholder story
  • Way down the backlog

11. Now we can have user stories! 12. What is a user story?

  • A concise, written description of a piece of functionality that will be valuable to a user(or owner) of the software.

13.

  • Discovered at planning stages
  • Discovered during the project
  • Continuously emerge/change and disappear
  • For sizing the project and sprint
  • For prioritising what to do next
  • Monitored each sprint
  • For the development team and owner

Stories are: 14. When

  • Some are done at an initial planning stage
  • Some are done later
  • Continuously emerge/change and disappear
  • Worked on throughout the project

15. Stories are for sizing 16. Stories are for prioritising 17. Stories are monitored 18. Stories are monitored 19. Stories are monitored 20. Stories are monitored 21. Stories are for the team and product owner 22. Stories have 3 parts

  • Card :A description, Priority and Estimate
  • Conversation :A section for capturing further information about the user story and details of conversations
  • Confirmation :A section to convey what tests will be carried out to confirm the user story is complete and working as expected

Source: XP Magazine 8/30/01, Ron Jeffries. 23.

  • As amusic lover
  • I want tosubmit payment by credit card
  • so thatI can purchase the album

Card: The Description 24. Card 25. Card 26. A section for capturing further information about the user story and details of conversations The Conversation 27. A section to convey what tests will be carried out to confirm the user story is complete and working as expected The Confirmation 28. 6 attributes of a good user story 29.

  • I ndependent
  • N egotiable
  • V aluable to users or purchasers
  • E stimatable
  • S mall
  • T estable

30. Independent 31. Negotiable 32. Valuable 33. Estimatable 34. Small 35. Testable 36. A word of warning

  • Dont use stories in a sequential fixed process
  • Dont make a contract out of stories
  • Dont write stories in isolation

37. What next? Challenges Tasks Spikes Feedback 38.

  • Still alive? Any questions?

[email_address] [email_address] 39. Challenges 40. Iteration 0 41. Non-functional requirements 42.

  • The system will connect to the database through a connection pool
  • We need to use Akamai caching
  • The system shall be written in Java
  • The system needs to be able to store 700 million records
  • We need to set up a VISTA development box

Customer value? 43. Spikes