scope-check

Formal scope trimming involves inventorying sprint plans, assessing capacity, applying MoSCoW categorization, and documenting cut proposals. This process enforces scope reduction to match available resources and timelines, preventing milestone slips during planning.

MoSCoW prioritization categorizes sprint items into must-have, should-have, could-have, and won't-have items. It enables structured scope assessment by evaluating urgency and capacity, ensuring teams formally identify and cut non-essential features to protect milestones.

Decide what to cut by running a scope check for crisis re-planning, applying MoSCoW categorization to inventory scope and assess capacity. This generates formal cut proposals isolating must-have items, updating documentation and preserving critical milestones.

Yes, the scope check process applies to milestone reviews and design docs. It inventories current scope across sprint plans and design documents, assesses capacity, and updates plans to ensure deliverables stay aligned with available resources and timelines.

Yes, scope trimming requires a formal decision log for documentation updates. Enforcing a formal process for cut proposals and documentation updates records all scope reductions and MoSCoW categorizations to preserve critical milestones.