The Scrum Master Persona
Backlog, sequencing, and flow
The Scrum Master persona takes the approved story list and sequences it into a deliverable backlog, identifying dependencies, blocking risks, and the minimum viable increment that can be shipped first.
The Scrum Master persona is responsible for taking a list of approved stories and turning it into a sequenced, deliverable backlog. Its inputs are the PM's story list and the Architect's document. Its outputs are: an ordered backlog with dependency mapping, a definition of the minimum viable increment (the smallest subset that delivers real value), and a risk log for anything that could block delivery.
Sequencing is the SM's primary decision. Stories with shared dependencies must be ordered correctly. Stories that de-risk the architecture — proving a technology integration works, for example — should generally come before stories that build on that integration. The SM does not add or remove stories; that is the PM's scope. It does flag stories sized incorrectly for single-session implementation.
In AI-driven development, the SM's risk log is particularly important. Risks that a human team would manage through daily standups need to be made explicit in advance, because there are no standups with an AI. If a story depends on an external API being available, that dependency must appear in the backlog as a prerequisite story, not be discovered mid-implementation.
Key Concepts
- Backlog sequencing based on dependencies and risk-reduction ordering
- Minimum viable increment — the smallest shippable subset of the story list
- Risk log makes implicit blockers explicit before implementation begins
- SM flags incorrectly sized stories without removing or rewriting them
- SM does not write or prioritise stories — that scope belongs to the PM