Trawling for Requirements (1, page 43)
Imagine gathering requirements as like fishing. You don’t want to catch every single fish in one haul as the processing of that would mean that some fish would go off. Focus on catching the big fish first by using a wide net, then later you can use a finer net to catch the smaller fish. This is the same with requirements as with the big requirements you can use them to understand the product direction better.
Building the Initial Backlog Techniques
Idea Generating Workshop (2, page 50)
- Use the liberating structure, 25/10 Crowd Sourcing
- Ask the room to use the ‘What’s the most important feature this product needs to be successful?’ question
- The output of the session can be used by the Product Owner to form the initial Product Backlog
User Story Mapping (4)
- Break down a user journey into outcomes and stories using the opportunity and user needs as a guide
- See User Story Mapping Workshop
Impact Mapping (3, page 86)
Technique for connecting PBIs back to the goals they are intended to meet.
- User Stories Applied by Mike Cohn
- Fixing Your Scrum by Ryan Ripley and Todd Miller
- Mastering Professional Scrum by Stephanie Ockerman and Simon Reindl
- User Story Mapping by Jeff Patton