scope-cutting

To reduce project scope within a fixed delivery cycle, apply an appetite-first methodology by defining a strict time budget before considering features, then systematically questioning each component's necessity to ensure work fits the constraint.

Scope hammering in agile product development is a technique that systematically questions each feature's necessity by evaluating must-have versus nice-to-have elements, checking if the product is shippable without it, and comparing against a baseline of having no feature.

To define an MVP using Shape Up methodology, set a fixed time appetite ranging from one to two weeks for small batches or up to six weeks for large batches, then shape down the project scope by cutting breadth rather than quality.

You should cut breadth instead of quality during feature trimming when a project exceeds its allocated time budget, which involves removing entire user surfaces or time-bounding edge cases to ensure a valuable increment ships on schedule.

Unfinished work at the end of an agile cycle is canceled by default under the circuit breaker principle, which prevents zombie projects from carrying over and ensures teams only ship completed, valuable increments within the fixed timebox.

Scope-cutting works for large feature sets by applying appetite-first constraints to identify and remove non-essential components, ensuring that a valuable, albeit smaller, increment is shipped on time within the defined cycle.