How-To-Demo

Ever struggle to split a User Story? Most of us familiar with the industry standard “SPIDR” method (Spike, Path, Interface, Data, Rules) for splitting User Stories. But have you tried the "How-To-Demo" technique?

 The rule is simple: Reverse engineer your User Story at the end-of-sprint Demo. If you can't explain how to Demo your User Story in 3 steps or less, the User Story is too big. Split it!

 How to Apply:

·       The Happy Path: Start by demoing the Happy Path. Demo the simplest way to finish a task first. Handle edge cases, errors or alternative paths in the next Demos.

·       One Data Type First: Demo using only one data type before adding others. Support for other data types in later Demos.

·       Logic Over Style: Demo a basic UI to prove the logic works, then advance styling it in later Demo.

·       Simplify Rules: Ignore complex rules initially and show the basic functionality. Add the rule-based logic in a follow-up Demo.

·       Documents: Even finishing a piece of documentation or test cases can be part of your Demo goals.

 This approach creates a crystal-clear “Definition of Done” and ensures you always have something valuable to show and Demo.  It is s an easy way to keep your team focused and your sprints manageable. Try it in your next sprint!