• A prioritized queue of one-line user stories
• Not a schedule. No due dates!
• Prioritization by position:
  • Order defined by client, not developers
  • Top means "do this first"
  • No priority numbers, no labels like "must have".
    • If you allow that, everything becomes top priority

• At each planning meeting, clients and developers expand the top user stories to be done for the next iteration.
  • Client picks the stories.
  • Team determines how many.
• Each story chosen must be expanded.
• Client and developers define:
  • acceptance tests, i.e., concrete examples that must work
  • user interface changes
  • ideally, planned user testing materials

• The backlog becomes a very long list of every possible story.
  • Hard to prioritize and estimate
  • Demoralizing to developers
• Top stories are unrelated to each other.
  • Few if any big victories at the end of the iteration.

• Group user stories by the scenarios they enable.
  • Scenarios are complete demos or user journeys.
  • Under each scenario, list the user stories that needed for the scenario.
• Prioritize scenarios.
• Example of a scenario backlog

• Write minimum viable scenarios.
  • Each scenario demonstrates one piece of user value.
• Write simplest user stories that will make scenario work.

<More to come!>

Thanks to Hakim El Hattab for RevealJS