mvp-scope-guard

To prevent MVP scope creep, evaluate proposed features against defined MVP goals using a Scope Decision Matrix. This process systematically determines whether a feature request should be INCLUDED or DEFERRED to maintain focus on learning objectives.

The best way to evaluate feature requests for an MVP is to assess them against defined MVP objectives during planning reviews. Applying a Scope Decision Matrix helps decide whether to INCLUDE or DEFER features and label non-essential ideas for later phases.

To tag deferred features during project planning, apply a tagging workflow that marks non-essential ideas for later phases. This preserves delivery speed by keeping the current MVP scope focused while retaining valuable ideas for future development.

Yes, you can integrate MVP feature evaluation with spec-driven planning. The Scope Decision Matrix workflow integrates with project-vision-normalizer to guide the spec-driven planning stage and streamline decision-making during MVP definition.

You should defer a feature request when it does not align with the defined MVP goals and learning objectives. Evaluating the request against the Scope Decision Matrix identifies non-essential features to tag for later phases to preserve delivery speed.