scope-check

You detect scope creep by comparing original planned scope from design documents against current implemented features, generating a bloat score with percentage change. This comparison highlights unplanned additions and calculates timeline risks to support immediate replanning decisions.

A bloat score quantifies the net unplanned scope additions and removed items compared to your original baseline. It serves as a measurable risk indicator to determine if iterative software development timelines remain viable.

Yes, baseline scope comparisons apply directly to game development milestone audits. The process pulls original planned scope from design documents to identify unplanned feature additions and generate prioritized cut or defer recommendations for the milestone.

You prioritize feature cuts by generating a structured triage report that assesses risk and outputs prioritized recommendations. This identifies which unplanned additions to cut, defer, or send for stakeholder approval to keep core deliverables on track.

No, scope creep detection does not require external dependencies or components to function. It operates independently to scan codebase and git history data, establishing a baseline from existing milestone files and sprint plans.

You should perform a milestone audit for feature scope changes mid-sprint or during active development to check if unplanned requests push timelines beyond acceptable limits. Early detection prevents unplanned additions from silently derailing budgets and resource allocation.