Design a lightweight sprint planning process for a small product team.

Instruction: Design a lightweight operating model. Be explicit about cadence, ownership, artifacts, and success signals.

Context: Tests whether the candidate can design a lightweight PM operating system with clear ownership, cadence, and outputs.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

For a small team, I would keep sprint planning lightweight but still opinionated. I want one clear sprint objective, a short list of committed work, and explicit callouts for risk or dependency. That usually...

Related Questions