Stories, defects and tasks
Download as PPTX, PDF0 likes206 views
This document discusses different types of work items like stories, defects, and tests used for software development. It explains user stories should be independent, negotiable, valuable, estimable, small, and testable. Tasks must belong to either defects or stories. Acceptance criteria are used to describe what needs to be built at a high level while acceptance tests describe how it was built and ensure the right solution was implemented.
Stories, defects and tasks
- 1. Stories, Defects, Tasks and Tests
- 2. 3 types of work items
- 4. A new piece of functionality
- 5. Must always add value to the product
- 6. 3 C’sCar d Conversat ion Confirma tion Written reminder about the feature Details about the feature that we get by talking to users How to we know that we’ve built the right thing? In order to get some cash as a bank customer I want to withdraw money from an ATM “Gherkin” format List format Given a jpg or png image When I upload it Then it should be saved And it should be resized Accepts JPG images Accepts PNG images Resizes to decent size Be careful not to describe the “How”
- 7. INVESTIndependent The user story should be self-contained, in a way that there is no inherent dependency on another user story. Negotiable User stories, up until they are part of an iteration, can always be changed and rewritten Valuable A user story must deliver value to the end user Estimable You must always be able to estimate the size of a user story Small User stories should not be so big as to become impossible to plan with a certain level of certainty Testable The user story must provide the necessary information to make test
- 10. Needs enough detail that somebody who knows nothing about the product can reproduce the issue
- 11. Detailed steps to reproduce What did you expect to happen? What actually happened? Screenshots (Before and after)
- 13. Defines the solution to the problem
- 14. Defects and Stories have tasks Tasks must belong to something
- 15. Defects/bugs for open stories are tasks
- 16. SMARTSpecific What? Why? Who? Where? Which? Measurable How much? How many? How long? Assignable Must be completable by a single person Relevant Worthwhile? Right time? Time-bound When? Can it be done in the time
- 17. Acceptance Tests
- 18. Acceptance Criteria describe what needs to be built “Build the right thing” Acceptance Tests describe how it was built
- 19. Two forms of Acceptance Criteria “Gherkin” format More descriptive, but easier to incorrectly specify implementation details List format Easier to write, and easier to see gaps Given a jpg or png image When I upload it Then it should be saved And it should be resized Accepts JPG images Accepts PNG images Resizes to decent size Should never contain implementation details!
- 20. Acceptance Tests usually only use the “Gherkin” format
- 21. Example! Acceptance criteria Acceptance test (Scenario)Given a baby animal younger than its recommended selling age When we try to sell it Then we should be told it’s too young. Given a rabbit called Fluffy who is 1 ½ months old When we try to sell Fluffy Then we should be told Fluffy is too young. We should be prevented from selling animals younger than the recommended age Given a puppy called Fang who is 1 month old When we try to sell Fang Then we should be told Fang is too young.