Your SlideShare is downloading. ×
0
INVEST in good user stories
<ul><li>Our project defines it’s requirements as User Stories </li></ul>
<ul><li>A user story is a description of what goals a user wants to achieve in the system </li></ul>
<ul><li>User stories are closely aligned to feature descriptions </li></ul>
<ul><li>User stories highlight the role of the user </li></ul>
<ul><li>The goal they are trying to achieve </li></ul>
<ul><li>And the value of that goal </li></ul>
<ul><li>As a <user type> </li></ul><ul><li>I want to <achieve a goal> </li></ul><ul><li>So that I can <get some value> </l...
<ul><li>For more information there are references at the end of this presentation </li></ul>
<ul><li>There are  good   and  bad   user stories out there. </li></ul>
<ul><li>In the tradition of  S.M.A.R.T.  goals, Bill Wake advises us to  I.N.V.E.S.T.   in user stories </li></ul>
INVEST   <ul><li>I ndependent </li></ul><ul><li>N egotiable </li></ul><ul><li>V aluable </li></ul><ul><li>E stimable </li>...
<ul><li>Avoid dependencies on other stories </li></ul><ul><li>Write stories to establish the system foundation </li></ul><...
<ul><li>Stories are not a contract </li></ul><ul><li>Too much written detail – it suggests that there is no more to explor...
<ul><li>Show what the value of the story is for the customers and other stakeholders </li></ul><ul><li>Independent </li></...
<ul><li>Sufficient detail needs to be present to estimate the work effort </li></ul><ul><li>Stories should be small enough...
<ul><li>Stories should be small enough to complete in a sprint (2 weeks) </li></ul><ul><li>The closer a story is to being ...
<ul><li>Acceptance criteria should be apparent in the user story </li></ul><ul><li>Tests should be automated wherever poss...
<ul><li>References </li></ul><ul><li>Extreme Programming Explored - William Wake </li></ul><ul><li>http://www.scribd.com/d...
Upcoming SlideShare
Loading in...5
×

Invest In Good User Stories

14,840

Published on

A little information on writing good user stories

Published in: Technology, News & Politics
3 Comments
37 Likes
Statistics
Notes
No Downloads
Views
Total Views
14,840
On Slideshare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
790
Comments
3
Likes
37
Embeds 0
No embeds

No notes for slide

Transcript of "Invest In Good User Stories"

  1. 1. INVEST in good user stories
  2. 2. <ul><li>Our project defines it’s requirements as User Stories </li></ul>
  3. 3. <ul><li>A user story is a description of what goals a user wants to achieve in the system </li></ul>
  4. 4. <ul><li>User stories are closely aligned to feature descriptions </li></ul>
  5. 5. <ul><li>User stories highlight the role of the user </li></ul>
  6. 6. <ul><li>The goal they are trying to achieve </li></ul>
  7. 7. <ul><li>And the value of that goal </li></ul>
  8. 8. <ul><li>As a <user type> </li></ul><ul><li>I want to <achieve a goal> </li></ul><ul><li>So that I can <get some value> </li></ul>
  9. 9. <ul><li>For more information there are references at the end of this presentation </li></ul>
  10. 10. <ul><li>There are good and bad user stories out there. </li></ul>
  11. 11. <ul><li>In the tradition of S.M.A.R.T. goals, Bill Wake advises us to I.N.V.E.S.T. in user stories </li></ul>
  12. 12. INVEST <ul><li>I ndependent </li></ul><ul><li>N egotiable </li></ul><ul><li>V aluable </li></ul><ul><li>E stimable </li></ul><ul><li>S ized right </li></ul><ul><li>T estable </li></ul>
  13. 13. <ul><li>Avoid dependencies on other stories </li></ul><ul><li>Write stories to establish the system foundation </li></ul><ul><li>Combine stories for a single iteration (where appropriate) </li></ul><ul><li>Independent </li></ul><ul><li>Negotiable </li></ul><ul><li>Valuable </li></ul><ul><li>Estimable </li></ul><ul><li>Sized right </li></ul><ul><li>Testable </li></ul>
  14. 14. <ul><li>Stories are not a contract </li></ul><ul><li>Too much written detail – it suggests that there is no more to explore </li></ul><ul><li>Know when you can’t negotiate – some constraints are fixed </li></ul>Independent Negotiable Valuable Estimable Sized right Testable
  15. 15. <ul><li>Show what the value of the story is for the customers and other stakeholders </li></ul><ul><li>Independent </li></ul><ul><li>Negotiable </li></ul><ul><li>Valuable </li></ul><ul><li>Estimable </li></ul><ul><li>Sized right </li></ul><ul><li>Testable </li></ul>
  16. 16. <ul><li>Sufficient detail needs to be present to estimate the work effort </li></ul><ul><li>Stories should be small enough to estimate, (but not too small) </li></ul><ul><li>Independent </li></ul><ul><li>Negotiable </li></ul><ul><li>Valuable </li></ul><ul><li>Estimable </li></ul><ul><li>Sized right </li></ul><ul><li>Testable </li></ul>
  17. 17. <ul><li>Stories should be small enough to complete in a sprint (2 weeks) </li></ul><ul><li>The closer a story is to being worked on the more specific it should be </li></ul><ul><li>Stories can start high level (epic) but they’ll need to be broken down later </li></ul><ul><li>Independent </li></ul><ul><li>Negotiable </li></ul><ul><li>Valuable </li></ul><ul><li>Estimable </li></ul><ul><li>Sized right </li></ul><ul><li>Testable </li></ul>
  18. 18. <ul><li>Acceptance criteria should be apparent in the user story </li></ul><ul><li>Tests should be automated wherever possible </li></ul><ul><li>User stories should not be commenced until they have clear acceptance criteria </li></ul><ul><li>Independent </li></ul><ul><li>Negotiable </li></ul><ul><li>Valuable </li></ul><ul><li>Estimable </li></ul><ul><li>Sized right </li></ul><ul><li>Testable </li></ul>
  19. 19. <ul><li>References </li></ul><ul><li>Extreme Programming Explored - William Wake </li></ul><ul><li>http://www.scribd.com/doc/12720/Extreme-Programming-Explored-William-Wake </li></ul><ul><li>Six features of a good user story </li></ul><ul><li>http://agilesoftwaredevelopment.com/blog/vaibhav/good-user-story-invest </li></ul><ul><li>INVEST in Good Stories, and SMART Tasks </li></ul><ul><li>http://xp123.com/xplor/xp0308/index.shtml </li></ul><ul><li>XP Practice: stories </li></ul><ul><li>http://agilesoftwaredevelopment.com/xp/practices/stories </li></ul><ul><li>User stories (in general) </li></ul><ul><li>http://agilesoftwaredevelopment.com/taxonomy/term/170/0 </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×