Vladimir TarasowAndris BarissThe Nuclear PowerUser Stories
Vladimir TarasowAbout: http://about.me/netratE-mail: netrat@netrat.euAndris BarissAbout: lv.linkedin.com/in/andrisbarissE-...
Product VisionDescribes why the project is undertaken.Describes what the desired end-state is.Shared by the Stakeholders, ...
RequirementRepresents a need.Must answer the questions What? and Why?Tries to identify with a clear sentencewhat is the pr...
User Story
User Story Example
Card
Conversation
Confirmation
User StoryRepresent a description of a “solution” —from a functional point of view.Should cut through all the layers ofthe...
User Story TemplateAs a <type of user>I want to <some goal>so that <some reason>
INVEST ModelIndependent. Easier to plan, if it has nodependencies.Negotiable. Details added via collaboration.Valuable. Pr...
Ready are you?What know youof ready?
Definition Of ReadyUser story is clear enough to start it.User story can be confirmed.User story is small enough to fit an...
Acceptance CriteriaHigh-level criteria from the perspective ofthe user or stakeholder.Define the boundaries for a User Sto...
Acceptance Criteria TemplateGiven <context>When <action>Then <expected result>
Acceptance Criteria ExampleAs an internet banking customerI want to see a rolling balance for my everyday accountsso that ...
When do you know you‘re done?A Release is done when it satisfies all thecriteria the Product Owner requires to shipsoftware...
Definition Of DoneApplies to all User Stories.Is the result of an agreement between theProduct Owner and the team on quali...
Definition Of Done ExampleNo (known) bugs.Passed unit tests.Passed automated acceptance tests.Passed user acceptance testi...
Thank You!Please, leave feedback!http://spkr8.com/t/23051
Materials used in the presentation:● Advantages of the “As a user, I want” user story template by Mike Cohn● Definition of...
This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy...
Upcoming SlideShare
Loading in...5
×

User Stories — The Nuclear Power

435

Published on

Doing agile by book is ok for the beginning. However, it's not enough. You should continue to learn by gaining new knowledge during the project. User stories and the way you're working with them are the bricks which form the foundation the better experience.

User Stories could be Your best partner and support in project, yet them could become your worst nightmare. Where and how User Stories help? When and how User Stories could become a large burden?

Next time we will dig into user story deeper. How it differs from requirements, use cases or test cases? From what parts it consists and why?

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
435
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

User Stories — The Nuclear Power

  1. 1. Vladimir TarasowAndris BarissThe Nuclear PowerUser Stories
  2. 2. Vladimir TarasowAbout: http://about.me/netratE-mail: netrat@netrat.euAndris BarissAbout: lv.linkedin.com/in/andrisbarissE-mail: andris.bariss@gmail.com
  3. 3. Product VisionDescribes why the project is undertaken.Describes what the desired end-state is.Shared by the Stakeholders, the ProductOwners, the Team and the end users.
  4. 4. RequirementRepresents a need.Must answer the questions What? and Why?Tries to identify with a clear sentencewhat is the problem to solve.
  5. 5. User Story
  6. 6. User Story Example
  7. 7. Card
  8. 8. Conversation
  9. 9. Confirmation
  10. 10. User StoryRepresent a description of a “solution” —from a functional point of view.Should cut through all the layers ofthe architecture.Must contain also Acceptance Criteria thatdescribes how the user of the story wouldaccept the implemented functionality.
  11. 11. User Story TemplateAs a <type of user>I want to <some goal>so that <some reason>
  12. 12. INVEST ModelIndependent. Easier to plan, if it has nodependencies.Negotiable. Details added via collaboration.Valuable. Provides value to the customer.Estimable. If its too big or too small, youcant estimate it.Small. Can be done in less than a week bythe team.Testable. Good acceptance criteria.
  13. 13. Ready are you?What know youof ready?
  14. 14. Definition Of ReadyUser story is clear enough to start it.User story can be confirmed.User story is small enough to fit aniteration.
  15. 15. Acceptance CriteriaHigh-level criteria from the perspective ofthe user or stakeholder.Define the boundaries for a User Story.Answer the question: How we will knowwhen we are done?Or answer the question: How to demo?Help developers and testers to derive testsThere are Positive and Negative criteria.
  16. 16. Acceptance Criteria TemplateGiven <context>When <action>Then <expected result>
  17. 17. Acceptance Criteria ExampleAs an internet banking customerI want to see a rolling balance for my everyday accountsso that I know the balance of my account after each transactionis appliedACs:● The rolling balance is displayed correctly● The rolling balance is calculated correctly for eachtransaction● The balance is displayed for every transaction for the fullperiod of time transactions are available● The balance is not displayed if a filter has been applied
  18. 18. When do you know you‘re done?A Release is done when it satisfies all thecriteria the Product Owner requires to shipsoftware to production.A User Story is done when it meets thestory acceptance criteria and the team’squality standards for being potentiallyshippable
  19. 19. Definition Of DoneApplies to all User Stories.Is the result of an agreement between theProduct Owner and the team on quality.Should be build in every single piece offlow — User Story, task…
  20. 20. Definition Of Done ExampleNo (known) bugs.Passed unit tests.Passed automated acceptance tests.Passed user acceptance testing.Code peer reviewed (if not pairprogrammed).Any build/deployment/config changesdocumented/communicated.Relevant documentation updated.
  21. 21. Thank You!Please, leave feedback!http://spkr8.com/t/23051
  22. 22. Materials used in the presentation:● Advantages of the “As a user, I want” user story template by Mike Cohn● Definition of Ready by Ken Power● Essential XP: Card, Conversation, Confirmation by Ron Jeffries● On Acceptance criteria for user stories by Sandy Mamoli● What’s Done is Done: User Stories by Daniel Gullo● User Stories, Epics and Themes by Mike Cohn● Master Yoda by ~N68CAL● Photo by Wexner Center● Photo by Paul McCarthy● Photo by Pavel Krok● Photo by Honou● Illustrations by Vladimir TarasowCredits
  23. 23. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy of thislicense, visit http://creativecommons.org/licenses/by-nc-sa/3.0/.

×