Overview of Agile Stories This presentation is licensed under a  Creative Commons Attribution 2.5 License , which means yo...
Story
Confirmation As a wiki author I want to be able to bold text so that I create visually appealing content for my readers. C...
What is a Story? <ul><li>Functionality that provides value </li></ul><ul><li>Written in business (domain) language </li></...
Story Card <ul><li>The “headline” for some new functionality. </li></ul><ul><li>It is an “invitation to a conversation”. <...
Story Conversation <ul><li>Exchange of thoughts, opinions, and feelings. </li></ul><ul><li>Takes place over time, particul...
Story Confirmation <ul><li>Story tests are acceptance tests for the product owner </li></ul><ul><li>Product owner specifie...
Upcoming SlideShare
Loading in …5
×

Agile Stories

2,074 views

Published on

A quick overview of Agile stories as a preamble to the Waterloo Agile/Lean User Group session on Agile User Stories: http://waterlooagilelean.wordpress.com/2008/12/19/2008-12-16-user-story-session-notes.

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,074
On SlideShare
0
From Embeds
0
Number of Embeds
30
Actions
Shares
0
Downloads
69
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Questions - your role (tester, developer, manager, other) - your situation (agile, waterfall, hybrid) What do you want out of this?
  • Agile Stories

    1. 1. Overview of Agile Stories This presentation is licensed under a Creative Commons Attribution 2.5 License , which means you can share and adapt it, including commercial and derivative works, as long as you include attribution to Declan Whelan. Declan Whelan [email_address]
    2. 2. Story
    3. 3. Confirmation As a wiki author I want to be able to bold text so that I create visually appealing content for my readers. Card Conversation
    4. 4. What is a Story? <ul><li>Functionality that provides value </li></ul><ul><li>Written in business (domain) language </li></ul><ul><li>Ideally < 2 days work </li></ul><ul><li>“ As a < role >, I want to < feature > so that < benefit >” </li></ul>
    5. 5. Story Card <ul><li>The “headline” for some new functionality. </li></ul><ul><li>It is an “invitation to a conversation”. </li></ul><ul><li>Written in business (domain) language. </li></ul><ul><li>It is not a specification … specifications are documented using story tests. </li></ul><ul><li>Stories can be used to drive additional work such as building test scripts/frameworks </li></ul>
    6. 6. Story Conversation <ul><li>Exchange of thoughts, opinions, and feelings. </li></ul><ul><li>Takes place over time, particularly when the story is estimated. </li></ul><ul><li>Conversations also occur at the iteration planning meeting when the story is scheduled for implementation. </li></ul><ul><li>Supplement with documents as needed. </li></ul>
    7. 7. Story Confirmation <ul><li>Story tests are acceptance tests for the product owner </li></ul><ul><li>Product owner specifies the story tests but will collaborate with team to create them </li></ul><ul><li>Team can add additional tests </li></ul><ul><li>Most tests can and should be automated (e.g. FIT, xBehave, xSpec, stress tests, load tests) </li></ul>

    ×