Stories <ul><li>&quot;Code is nothing, stories are everything!&quot; </li></ul>
No Not that Kind of Story
This kind of story... Title: Comment Page - Thank you page Description: As a stakeholder  In order to let my customers kno...
What? User Stories seek to find a balance between written and verbal requirements, relying on collaboration between team m...
Why? <ul><li>To figure out what we want to do </li></ul><ul><li>To schedule things to be done </li></ul><ul><li>To figure ...
How?
I.N.V.E.S.T > stupid acronym to help us along the way and is made up of a bunch of the “able” words
Independent
Negotiable
Valuable
Estimable
Small
Testable
Acceptance Criteria <ul><li>What are the required fields? </li></ul><ul><li>What are the required buttons? </li></ul><ul><...
Lets do an Exercise
The Advanced Search Box
Describe it! <ul><li>How would you describe what you want the developer to produce for you? </li></ul><ul><li>Take a few m...
Story? <ul><li>Can someone share their narrative? </li></ul><ul><li>How many stories did people come up with? </li></ul><u...
Decomposition <ul><li>10 stories with 3 placeholder stories indicating we need more information. Will generate additional ...
Why Decompose? <ul><li>Decomposing the “widget” into smaller stories makes it easier for the developers to estimate.  </li...
Why Continued.. <ul><li>Allows the stakeholder to pick and chose what is important.  </li></ul><ul><li>Makes the developer...
Pivotal Tracker <ul><li>Lets look at what these stories look like in Pivotal Tracker. </li></ul>
What about stories that don’t come from a mockup?
Title: SEO - County Search Page Updates Description: In order to accomplish higher rankings by search engines, as the SEO ...
Is it a Story? OR Is it a Epic?
Epic? <ul><li>A high level description of a feature that is represented the same way a story is but is large and fuzzy. </...
Image
Lets Recap the Guidelines <ul><li>Follow the principals of INVEST to the best of your ability </li></ul><ul><li>Follow a t...
Upcoming SlideShare
Loading in …5
×

Agile Storycarding

1,841 views

Published on

An awesome process flow for storycarding. Much thanks @desi and @hashrocket

Published in: Technology, Design
  • Be the first to comment

Agile Storycarding

  1. 1. Stories <ul><li>&quot;Code is nothing, stories are everything!&quot; </li></ul>
  2. 2. No Not that Kind of Story
  3. 3. This kind of story... Title: Comment Page - Thank you page Description: As a stakeholder In order to let my customers know I appreciate them providing feedback I would like them to receive a thank you page letting them know we received their comments and appreciated them. Acceptance Criteria: A thank you page should be displayed upon customer submission of a comment.
  4. 4. What? User Stories seek to find a balance between written and verbal requirements, relying on collaboration between team members to clarify details near the time of development.
  5. 5. Why? <ul><li>To figure out what we want to do </li></ul><ul><li>To schedule things to be done </li></ul><ul><li>To figure out what is really providing value </li></ul><ul><li>To provide information to the developer and others without having to do lengthy requirements docs </li></ul>
  6. 6. How?
  7. 7. I.N.V.E.S.T > stupid acronym to help us along the way and is made up of a bunch of the “able” words
  8. 8. Independent
  9. 9. Negotiable
  10. 10. Valuable
  11. 11. Estimable
  12. 12. Small
  13. 13. Testable
  14. 14. Acceptance Criteria <ul><li>What are the required fields? </li></ul><ul><li>What are the required buttons? </li></ul><ul><li>Where should the user go when a button is clicked? </li></ul><ul><li>What are the calculations? </li></ul><ul><li>Examples? </li></ul>
  15. 15. Lets do an Exercise
  16. 16. The Advanced Search Box
  17. 17. Describe it! <ul><li>How would you describe what you want the developer to produce for you? </li></ul><ul><li>Take a few minutes to write down how you would describe the functionality. </li></ul>
  18. 18. Story? <ul><li>Can someone share their narrative? </li></ul><ul><li>How many stories did people come up with? </li></ul><ul><li>Are your stories estimable? </li></ul><ul><li>Does it clearly tell the developer what you want from them? </li></ul>
  19. 19. Decomposition <ul><li>10 stories with 3 placeholder stories indicating we need more information. Will generate additional stories. </li></ul>
  20. 20. Why Decompose? <ul><li>Decomposing the “widget” into smaller stories makes it easier for the developers to estimate. </li></ul><ul><li>Allows developers to focus on small chunks of deliverables. </li></ul><ul><li>Reveals questions ahead of time mitigating delay in actual dev cycle. </li></ul>
  21. 21. Why Continued.. <ul><li>Allows the stakeholder to pick and chose what is important. </li></ul><ul><li>Makes the developers think about what it will actually take to implement the functionality. </li></ul>
  22. 22. Pivotal Tracker <ul><li>Lets look at what these stories look like in Pivotal Tracker. </li></ul>
  23. 23. What about stories that don’t come from a mockup?
  24. 24. Title: SEO - County Search Page Updates Description: In order to accomplish higher rankings by search engines, as the SEO person, I would like to have the new county search page (/search/county/) updated so that the title, the meta description, and the H1 tags are more relevant. Acceptance Criteria: Title should have the following:<COUNTY NAME> County Home Rentals, Apartments for Rent, Homes or Houses for rent in <COUNTY NAME> County <STATE ABBR> | RentalHouses.com Meta Description should have the following:Home Rental Listings in <COUNTY NAME> County <STATE NAME>. Information and listings for available homes for rent in <COUNTY NAME> County <STATE ABBR>. Find the perfect house for rent in <COUNTY NAME> County to fit your monthly house rental budget on RentalHouses.comH1 should have:<COUNTY NAME> County Home Rental Listings
  25. 25. Is it a Story? OR Is it a Epic?
  26. 26. Epic? <ul><li>A high level description of a feature that is represented the same way a story is but is large and fuzzy. </li></ul><ul><li>Epics should not be estimated because it will be wrong. </li></ul><ul><li>Epics are okay for high level product planning but can not be worked on until they become proper stories. </li></ul>
  27. 27. Image
  28. 28. Lets Recap the Guidelines <ul><li>Follow the principals of INVEST to the best of your ability </li></ul><ul><li>Follow a template </li></ul><ul><ul><li>As a <role> I want <goal> so that <reason> </li></ul></ul><ul><ul><li>In order to <reason> as a <role> I want <goal> </li></ul></ul><ul><li>Check with yourself and others to make sure its understandable, not too small, not too big, and is testable (clear acceptance) </li></ul>

×