TPM Sprint under Capacity Shock

Free Review to certify

TPM Sprint under Capacity Shock

Run a sprint at −30% capacity with an emergency insert — re-plan and protect the demo date.

Skills you'll learn

Sprint planning Board management Standup rhythm Unblocking Demo readiness

~130 min · +65 pts

SCENARIO: Mid-sprint, one engineer is out sick (≈−30% capacity). Product inserts an urgent "share-to-WeChat" ticket.
Demo to mentors is Friday — non-negotiable for this lab.

Template: /assets/templates/tpm-pack/02-sprint-board.md
Rubric: /assets/templates/tpm-pack/RUBRIC.md

Must produce:
1) Backlog 8–12 tickets with S/M/L + acceptance criteria (before the shock)
2) Board columns: To do / Doing / Blocked / Done
3) Shock response: what you drop, what you keep, impact on Demo
4) Decision on the emergency insert (accept / defer / time-box) with rationale
5) Three standup notes including the shock day
6) Demo checklist (show / hide / known bugs)

Submit: board + notes (link/screenshots) + reflection.

Environment setup (start here)

Document lab. Use 02-sprint-board.md. Simulate −30% capacity + WeChat insert; protect Friday demo.

Browser only

Pick your OS and follow from step 1:

Windows macOS

1) Copy /assets/templates/tpm-pack/02-sprint-board.md.
2) Fill baseline backlog, then apply the shock section.
3) Optional: mirror the board in Trello/GitHub Projects and screenshot.
4) Submit board + notes + reflection.

Same as Windows — Markdown first, optional Trello/GitHub Projects screenshots.

How do I know it worked?

Shock response and insert decision are filled; demo checklist lists show/hide/bugs.

Common issues

If you accept every ticket after −30%, restart — demo date must force cuts.