avoid-feature-creep

Prevent feature creep by enforcing explicit MVP scope definitions and maintaining strict backlog discipline. Use decision logs to document feature requests, rationale, and trade-offs, ensuring scope expansion is governed during releases.

Manage backlog scope by applying governance rules like the 48-hour rule and rigorous prioritization. When stakeholders request extra features, defer them with a clear impact analysis and document the decision in a scope decision log.

Define MVP scope by explicitly outlining what is included and referencing what is strictly out of scope. Lock the current sprint MVP scope and log the decision to prevent uncontrolled feature growth and ship faster.

Yes, enforcing MVP scope works across software and product teams, including AI-assisted development workflows. It applies to planning, reviews, and backlogs, requiring clear scope definition and governance to prevent expansion.

Apply the 48-hour rule during backlog governance to force deferred evaluation of new feature requests. This prevents immediate scope expansion, allowing teams to prioritize properly and maintain focus on shipping the core MVP.