際際滷

際際滷Share a Scribd company logo

All About Those User Stories

Download as PPTX, PDF
N
NetSuite

This document discusses user stories, which are short descriptions of a software feature written from the perspective of an end user. User stories help plan requirements in an agile development process. They are not technical specifications, but instead focus on the user's goal and how it provides business value. Good user stories have a clear user role, function or behavior, and acceptance criteria to define when the story is complete. The document provides guidelines for writing effective independent, negotiable, valuable and estimatable user stories.

1 of 14
Download to read offline
All About Those User Stories Carlo Ibarra
Requirements
What is a User Story? a written description of the story used for planning and as a reminder to discuss detail of the story tests that convey and document details and used to test if story is complete system of managing requirements in an iterative development 3 Cs - Card, Conversation, Confirmation
What Stories are NOT? NOT a detailed requirement NOT a technical specification NOT a documented contract NOT a software development plan (not SCRUM) NOT IEEE 830 NOT Use Cases NOT Scenarios
Parts of a User Story Description User role Business function/behaviour Business value Constraints Details Acceptance criteria
What Makes a Good Story a central character (user role) a plot - (function/behaviour) an ending - (test criteria) a lesson - (value to customer)
Writing User Stories Independent Negotiable Valuable to Customer/User Estimatable Small Testable
Independent Loosely coupled Stand-alone Avoid dependencies
Negotiable Emergent Encourages conversation Avoid creating "should have" or "must have"
Valuable (to Customer) Avoid technical requirements Aim for conversation Avoid zero-sum game
Estimatable Stories uses domain parlance and is understood by everyone Avoid jargons Helps development
Small and Testable Right size Clear criteria for doneness functional
Guidelines for Good User Stories Start with Goal Stories Slice the Cake Write Closed Stories Put Constraints on Cards Size the Story to the Horizon Keep the UI Out as Long as Possible Some Things Arent Stories Include User Roles in the Stories Write for One User Write in Active Voice Customer Writes Dont Number Story Cards Dont Forget the Purpose
Story Smells Stories Are Too Small Interdependent Stories Goldplating Too Many Details Including User Interface Detail Too Soon Thinking Too Far Ahead Splitting Too Many Stories Customer Has Trouble Prioritizing Customer Won't Write and Prioritize the Stories

More Related Content

All About Those User Stories

  • 1. All About Those User Stories Carlo Ibarra
  • 3. What is a User Story? a written description of the story used for planning and as a reminder to discuss detail of the story tests that convey and document details and used to test if story is complete system of managing requirements in an iterative development 3 Cs - Card, Conversation, Confirmation
  • 4. What Stories are NOT? NOT a detailed requirement NOT a technical specification NOT a documented contract NOT a software development plan (not SCRUM) NOT IEEE 830 NOT Use Cases NOT Scenarios
  • 5. Parts of a User Story Description User role Business function/behaviour Business value Constraints Details Acceptance criteria
  • 6. What Makes a Good Story a central character (user role) a plot - (function/behaviour) an ending - (test criteria) a lesson - (value to customer)
  • 7. Writing User Stories Independent Negotiable Valuable to Customer/User Estimatable Small Testable
  • 8. Independent Loosely coupled Stand-alone Avoid dependencies
  • 9. Negotiable Emergent Encourages conversation Avoid creating "should have" or "must have"
  • 10. Valuable (to Customer) Avoid technical requirements Aim for conversation Avoid zero-sum game
  • 11. Estimatable Stories uses domain parlance and is understood by everyone Avoid jargons Helps development
  • 12. Small and Testable Right size Clear criteria for doneness functional
  • 13. Guidelines for Good User Stories Start with Goal Stories Slice the Cake Write Closed Stories Put Constraints on Cards Size the Story to the Horizon Keep the UI Out as Long as Possible Some Things Arent Stories Include User Roles in the Stories Write for One User Write in Active Voice Customer Writes Dont Number Story Cards Dont Forget the Purpose
  • 14. Story Smells Stories Are Too Small Interdependent Stories Goldplating Too Many Details Including User Interface Detail Too Soon Thinking Too Far Ahead Splitting Too Many Stories Customer Has Trouble Prioritizing Customer Won't Write and Prioritize the Stories