Handbook
Wizard 201 — Resume and advance
Mission mode: foundation work exists; you need the next chapter (for example MVP to scale).
What it is
Mission mode: foundation work exists; you need the next chapter (for example MVP to scale).
Parent: Wizard 201 — Mission modes.
When to use it
When the initiative is mid-flight and you need a coherent run plan for the next increment—not a reset.
Outcome
Updated artifacts and a run plan that continues the story.
When not to use it
Avoid this mode when the team needs a reset or repair posture — if the same inconsistency keeps failing review, use Repair stage. If the initiative is cancelled, close the session narrative explicitly rather than “advancing” fictionally.
Inputs you need before the session
| Input | Why |
|---|---|
| Prior session artifacts or exports | Continuity for Scope and Run plan |
| What changed in the world since last time | Prevents replaying an outdated plan |
| Definition of “done” for this increment | Separates this chapter from the backlog |
Map to Wizard 101
Wizard 101 lists all twelve steps. For Resume and advance, you will lean on Scope selection, Run plan, Review & generate, and Recheck / repair more than early discovery steps.
Common mistakes
| Mistake | What to do |
|---|---|
| Rewriting history | Carry forward facts; add a short “what changed” preface |
| Mixing this increment with the whole roadmap | Use Scope selection to cut scope |
| Ending without agreement on “done” | Align stakeholders in Review before handoff |
Example scenario (mission mode)
| Starting situation | MVP shipped; scale and SRE need a plan; you must not rewrite history. |
| Action taken | Focus Scope selection and Run plan on the next increment; carry forward artifacts from prior sessions. |
| Expected result | Run plan for the next increment with explicit risks and owners. |
| What to check | Stakeholders agree what is “done” for this increment vs deferred. |