Top PMP Interview Questions & Answers (2026)

A CPI of 0.85 means we get 85 cents of planned value for every dollar spent, so we're over budget. An SPI of 1.05 means we've done slightly more work than planned by now, so we're ahead of schedule. Together that often means we bought speed with overtime, extra contractors or expedited deliveries. If the trend holds, a simple estimate at completion is budget divided by CPI, so a 1 million dollar budget heads toward about 1.18 million. I'd find the cause, check whether being ahead actually helps the business, slow the spending if it doesn't, and tell the sponsor now with options rather than at the end.

I start in planning with a workshop: the team, a couple of subject experts and the sponsor, working from the WBS, assumptions and lessons from similar projects. Each risk gets a cause, event and effect so it's specific, an owner, and a rough probability and impact so we can rank them. For the top threats I pick a response: avoid by changing the plan, transfer through a contract or insurance, mitigate to reduce probability or impact, or accept with a contingency reserve. Opportunities get the mirror set: exploit, share, enhance or accept. Then risk review is a standing item in every status meeting, owners report on triggers, and new risks get added.

First I listen and capture the request clearly, including why they want it. I don't say yes in the hallway. Then I assess the impact with the team: scope, schedule, cost, quality, risk and any contracts. On the predictive parts, that goes to whoever holds change authority under our governance, often a change board or the sponsor, with options such as do it now and move the date, do it in a later release, or swap it for something of similar size. On agile work, the Product Owner reprioritizes the backlog, and that is the change process. Either way the decision is recorded, the baseline or backlog updated, and affected people told.

I agree up front what they care about, usually the outcome, the date, the money and anything that needs their decision. My weekly update fits on one screen: overall status with a one-line reason, progress against the next milestone, forecast against budget, the top three risks or issues with owners, and decisions I need from them with a deadline. I use the same format every week so changes stand out. I avoid letting status jump from green to red without warning, and if something turns red I call before the report goes out. Detail lives in a linked dashboard for anyone who wants it.

In most matrix organizations I don't control salaries or reviews, so I rely on clarity, relationships and making the work easier. Everyone knows what they own and why it matters, usually through a RACI agreed with the functional managers. I build relationships with those managers because they control people's time, and I bring them problems early instead of escalations. With the team, I set ground rules together, remove blockers fast and give credit publicly, including feedback to their managers at review time. If someone keeps missing commitments, I talk to them privately first and understand the cause, and only then involve their manager, with specifics.