Great User Stories can be used with the INVEST principle. The acronym INVEST helps to remember a widely accepted set of criteria, or checklist, to assess the quality of a user story.
The INVEST principles can be applied to all both business persona stories and “technical stories”. Which are becoming increasingly intertwined, as most companies turn into software companies with bigger digital footprints.
API’s are good example where they can be the digital bonding digital bonding within and between enterprises that can create dynamic ecosystems, new markets and and categories of business . With typical use case’s driven by increasing service capabilities requiring companies to open up their information systems
The criteria for a good user story need’s to be consistently applied to all types of user stories, to protect team velocities. If the story fails to meet one of these criteria, the team may want to reword it, or even consider a story rewrite. A good user story should be:
- Independent of all others so each of them could be developed and delivered separately. Each story should be an end-to-end independent slice of value. For technical user stories this can help reduce technical debt and tracking dependent parts
- Negotiable not a specific contract for features
- Valuable or vertical in adding value to customers.Why does it matter to the business or user. Where the user can be a persona or a machine
- Do not include implementation details, that is the teams job
- Estimable and understandable enough so could be divided into the task and could get estimated and delivered at a predictable pace
- Small so as to fit within a sprint or 40 hours of work
- Testable with an have acceptance criteria to test if they full fill customer’s needs