I don’t think there has ever been a project where there were not things that were both asked for and needed but still not delivered. This is often the area of intelligent tradeoffs and where most where the next project often gets born. Often features don’t get built because the team runs out of time and money. Sometimes the technology doesn’t exist and despite the need and the desire some portion of the needed scope just doesn’t happen. That does not mean it won’t happen in the future, just not part of this project. The challenge of course is knowing what is really needed AND what can realistically be built within time and budget constraints. Allocating resources to things that are needed, but just cannot be delivered is not a good practice and can turn a good project in to a bad one. The key here is really stakeholder management and care presentation of facts, not alt-facts, real ones. It can be really hard explaining to a key stakeholder that some badly needed feature will likely break the budget and blow the schedule, but it is often the right path. I recently did an ROI presentation on a wanted and needed feature that instantly convinced the project sponsor to drop significant scope from the project which also allowed us eliminate a major schedule risk. A small loss of scope is much better than a great loss in schedule and budget. Often the lessons learned can be applied to the “next project”.