When we cut scope because time is running out we ensure that the cut scope is not hurriedly thrown together or a half-baked feature is shipped. Both of these will make the software of higher quality.
By cutting scope and ensuring the quality we could reduce features that are a waste but there is a possibility of creating less valuable features.
You could combat the need of cutting features by taking your time on discovery.
Reference
Knuth, L. (2023, June 2). Work in an efficient team. https://lknuth.dev/writings/efficient_team/
Highlights or timestamps
- Cutting scope is a tool to ensure software quality
— ^3a7545 from Work in an efficient team