scope-management

Defining MVP scope requires establishing clear boundaries for what features are included and excluded in the initial delivery. This Skill generates a scope contract for each milestone to keep product management focused on the core viable product.

Detecting scope creep involves monitoring project execution for unapproved feature additions. This Skill identifies signs of expanding scope and uses a parking lot pattern to capture new ideas without derailing the current project management workflow.

Communicating scope tradeoffs requires clear documentation of what changes mean for the project timeline and deliverables. This Skill provides a template to articulate these tradeoff decisions effectively during product management discussions.

Scope management principles apply to software development, product management, and general project management workflows. The techniques for defining MVPs and detecting scope creep are adaptable to any structured product delivery context.

The parking lot pattern captures new ideas and feature requests for future consideration without allowing them to expand the current scope. It prevents scope creep by deferring non-essential additions while maintaining a backlog of stakeholder input.

A scope contract should be generated for each project milestone or delivery to define explicit boundaries. This ensures project management alignment and provides a baseline to measure against when detecting scope creep during execution.