• Like
Crafting Great-User-Stories for CapitalCamp DC
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Crafting Great-User-Stories for CapitalCamp DC


Manager of Technical Delivery Shannon Lucas gave this how to guide on constructing renowned user stories for CapitalCamp DC.

Manager of Technical Delivery Shannon Lucas gave this how to guide on constructing renowned user stories for CapitalCamp DC.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Crafting Great User Stories Shannon Lucas July 23rd, 2011
  • 2. OutlineWhat and whyWriting storiesUser roles & personasThings that aren’t storiesTracking storiesExamples
  • 3. What a user story isn’t
  • 4. FunctionalRequirementsDefined by IEEE 830Contractual in natureExample:3.4) The product shall have a gasoline-powered engine.3.5) The product shall have four wheels. 3.5.1) The product shall have a rubber tire mounted to each wheel.3.6) The product shall have a steering wheel.3.7) The product shall have a steel body.
  • 5. Use CasePart of Rational Unified Process (RUP)Large in scopePermanent artifactsPurpose is to document agreement
  • 6. Interaction ScenarioDetailed description of a user’s interactionwith a systemLarger in scope than a use caseEmphasis on realism and detailCharacteristics: Setting Actors Goals Events
  • 7. What a user story is
  • 8. What a User Story is Expresses functionality in terms of value to customers or users Uses the language of the customer Cross-cuts technical concerns Emphasizes shared understanding
  • 9. Cross-cuttingconcerns Single User Story
  • 10. Cross-cuttingconcerns Single User Story
  • 11. Why userstories?
  • 12. Benefits of storiesFocus is on user goals rather than systemattributesDefer detail till neededPromote tacit knowledge across teamHumans remember storiesNo illusion of precisionStories are not contractual obligations
  • 13. Writing stories
  • 14. Structure of a UserStoryWritten Description As a <user role>, I want to <goal> so that <benefit>.ConversationConfirmation
  • 15. Acceptance criteriaConditions of satisfactionNeed to be specified by the customerWritten before the programmer beginscodingShould clarify the intent of the story to thedevelopersMust be testable
  • 16. Qualities of a UserStoryFit on an index cardWritten for a single userWritten in active voiceWritten in language of the businessAvoid UI and technical details
  • 17. Qualities of a UserStoryI - IndependentN - NegotiableV - ValuableE - EstimableS - SmallT - Testable
  • 18. User roles & personas
  • 19. User RolesThere’s no generic “user”Each role is a single userCan be humans or other systemsAbusersExtreme characters
  • 20. PersonasImaginary representation of a user roleHas a name, a photo, and a bioHas an explanation of their motivations forusing the product
  • 21. Things thataren’t stories
  • 22. Things that aren’tstoriesConstraintsModels & WorkflowsStoryboardsWireframes
  • 23. Storing &tracking stories
  • 24. Storing and trackingstoriesSpecialized toolsPost-It notesSpreadsheets
  • 25. Example Stories
  • 26. Abuser StoryAs l33th@x, I want to put malicious contenton the home page so that I can embarrass thecompany for not hiring me.
  • 27. Bad User StoryAs a user, I want to register for a volunteerevent so I can begin fundraising.
  • 28. Good User StoryAs a volunteer, I want to create an account sothat I can share my availability forvolunteering to event planners.
  • 29. Bad User StoryAs a volunteer I want to create an account soI can log in.
  • 30. Good User StoryAs a donor, I want to donate to my friendsfundraising event online, so I can support hercharity efforts.
  • 31. Bad User StoryAs a staff member, I want to be able to trainnew staff quickly and efficiently using print oronline resources, so that they can feelcomfortable quickly.
  • 32. Good User Story?As a political candidate, I want to participatein online discussions with potential voters sothat I can understand whats really importantto them.
  • 33. Questions?
  • 34. Thank you!
  • 35. ResourcesScrum.org - http://www.scrum.org/Scrum Alliance - http://www.scrumalliance.org/All Things Product Owner - http://www.romanpichler.com/blog/user-stories/User story tools: http://www.userstories.com/productsUser Stories Applied by Mike Cohn