scope-check

You can quantify scope creep by comparing your baseline feature or sprint plan against the current codebase and git history. This analysis calculates a bloat score and identifies added items to determine net scope change.

A bloat score in project triage is a calculated metric that quantifies the net scope change between an original plan and current implementation. It helps assess schedule, quality, and integration risks caused by scope creep.

To get actionable recommendations for cutting scope creep, analyze the variance between baseline plans and current development progress. This yields prioritized guidance to cut, defer, keep, or flag items for producer decisions.

Scope management analysis requires no specific dependencies or external components. It operates as a read-only analysis tool, locating baseline plans in expected design paths and scanning git history to evaluate implementation state.

You should run a scope creep assessment during sprint reviews, feature planning, and milestone check-ins when you suspect work has expanded. It helps determine whether to cut additions or escalate concerns to producers.

The best way to assess schedule and integration risks from git log analysis is to compare current commits against the baseline planned scope. This flags unexpected additions and produces a clear PASS, CONCERNS, or FAIL verdict.