PMP Practice: Implement Approved Changes

This scenario tests understanding of change control in hybrid environments where formal governance processes must coexist with adaptive team practices. The project has explicit governance requirements for changes affecting baselines, and this situation clearly impacts both schedule and scope. The most effective approach facilitates stakeholder alignment first—both perspectives have legitimate organizational value—then follows the established change control process. The compliance officer represents mandatory regulatory requirements while the product owner represents market value delivery. Both need to understand the tradeoffs before a decision is made. Once priorities are clear through facilitated discussion, the PM must submit the change through formal governance channels because the impact crosses the threshold requiring documented approval. This respects both the hybrid nature of the project and the organizational governance framework. The closing fact that governance requires documented approval for baseline impacts makes this the clearly correct path—attempting to handle this purely through agile backlog management would violate established controls.

**Why not A:** Adding the ESG requirements to the product backlog with high priority and beginning work immediately bypasses the governance framework that the project has explicitly established for changes affecting the schedule and budget baseline. Even though the compliance requirement is non-negotiable in principle, the project has a 15% threshold triggering formal change approval, and this change represents approximately 15% additional effort impacting the go-live date. Starting work without documented governance approval violates the hybrid project's established controls.

**Why not C:** Escalating the conflict to the project sponsor treats this as a purely strategic decision requiring executive resolution before any dialogue between the affected parties has occurred. The compliance officer and product owner have legitimate but potentially reconcilable positions—the compliance deadline is three months away, which may allow for prioritization sequencing. Bringing the sponsor in before facilitating direct discussion between stakeholders can create unnecessary organizational friction and bypasses the PM's role as a conflict facilitator.

**Why not D:** Allowing the product owner to make the final prioritization decision as a matter of agile authority misapplies the product owner's role in a hybrid project with formal governance requirements. The product owner has authority over backlog prioritization within the boundaries established by the project's governance framework, but this framework explicitly requires documented change approval for changes affecting baselines. The product owner's authority does not override formal governance controls that exist at the project level, particularly when a mandatory compliance requirement is involved.