PMP Practice: Anticipate future budget challenges

The most effective approach is to prepare a detailed cost comparison that directly addresses the sponsor's skepticism with evidence. By showing the previous project's estimated versus actual costs broken down by work package, Ember can demonstrate exactly where underestimation occurred and explain how the current budget incorporates those lessons learned. This approach uses historical data as a learning tool rather than as a constraint, which is the proper application of lessons learned in budget estimation. The scenario establishes that Ember has access to final cost reports and lessons learned, making this the most immediate and compelling way to justify the budget increase. This demonstrates professional competence in using organizational process assets to create defendable estimates while managing sponsor expectations through transparent, data-driven communication.

**Why not A:** Requesting the sponsor meet with the previous project manager is an indirect approach that delays budget justification. Ember already has access to the historical data needed and should take ownership of presenting the evidence directly. This approach also places an unnecessary burden on the sponsor's time.

**Why not C:** Agreeing to use the previous project's insufficient budget as a starting point ignores the lessons learned and sets the project up for the same cost overruns. More aggressive cost controls cannot compensate for fundamentally underestimated work packages. This approach sacrifices accurate estimation to avoid a difficult conversation.

**Why not D:** Escalating to the PMO for historical metrics introduces unnecessary delay and provides generic industry data rather than project-specific evidence. Ember already has the most relevant data available—the previous project's actual cost reports and lessons learned—which are far more compelling than organizational averages.