When a project cannot be completed within time and scope is cut, one should not think this as a metric of failure. A better way of thinking would be comparing the produced work with the baseline of user experience.
As you cut scope, you ensure software quality by not releasing half baked or features that are a waste.
And don’t forget cutting features can improve a product as well.
Reference
Knuth, L. (2023, June 2). Work in an efficient team. https://lknuth.dev/writings/efficient_team/
Highlights or timestamps
- Cutting scope is not a metric for failure or success, a better metric is comparing the baseline user experience.
— ^f68a7a from Work in an efficient team