pm-scope-cut

To prioritize backlog items into MVP scope, classify candidate features into Must, Should, and Not now categories based on core user jobs and delivery constraints. This method enforces problem framing to yield a defensible, actionable scope for a development cycle.

Cutting broad feature requests involves enumerating candidate items and applying practical delivery constraints to organize them into Must, Should, and Not now lists. This pruning process ensures the resulting MVP scope remains lean and actionable.

The Must Should Not now framework works by framing core user problems and categorizing candidate backlog items against delivery constraints. It produces a prioritized set of lists with explicit reasons for each item, making the MVP scope defensible during scoping conversations.

Yes, you can use scope cutting during backlog grooming to evaluate candidate items against practical delivery constraints. Providing a backlog of candidate items allows the method to classify features into Must, Should, and Not now lists for the next cycle.

To generate a lean MVP scope, you need to provide a backlog of candidate items and your delivery constraints. This input allows the scope framing process to identify core user jobs and categorize items into Must, Should, and Not now lists.

You should avoid using Must, Should, Not now prioritization when you cannot define core user jobs or practical delivery constraints. The method relies on enumerating candidate items and framing the core problem to yield a defensible MVP scope.