scope-check

To detect scope creep in a project sprint, compare your original baseline documentation against the current codebase and git history. This quantifies additions, dropped items, and schedule variance to produce a bloat score and a clear risk verdict.

Quantifying feature triage changes requires scanning git evidence and TODO signals against original planned work. This calculates net change metrics and outputs decision-ready recommendations with a PASS, CONCERNS, or FAIL status for your milestone.

Yes, you can assess schedule risk for a milestone by reading git history and active plan signals to find current scope. Comparing this against original requirements reveals bloat and variance, which informs the overall risk assessment.

Requirements analysis prevents scope creep during sprint reviews by establishing a documented baseline. Comparing this baseline to actual codebase implementation highlights unauthorized additions and dropped items, yielding a quantified bloat score.

Yes, baseline documents are required to check for scope creep. The process depends on finding the original planned work by feature name, sprint number, or milestone in your expected documentation locations to measure against current implementation.

Your feature triage shows a high bloat score because current implementation scanned from the codebase and git evidence significantly exceeds the original planned work in your baseline documents. This net change triggers a CONCERNS or FAIL verdict with actionable next steps.