How to justify the gap between the initial estimate and the actual Project?
How can you justify the gap between the initial estimate and the actual Project when almost all projects developed in the last decade have been done in Agile mode, which is a good thing because short delivery cycles are implemented, which implies a better communication with the Customers.
This management approach works like a charm with IT people who understand the impact of this management philosophy in terms of cost, time, and scope on a project: fixed time and cost with variable scope.
However, while developers and IT teams have a good grasp of the subtleties of Agile, this is far from always being the case for other Managers and Senior Management for whom, everything should be fixed: time, cost, and scope!!!