PMP Practice: Determine Compliance Actions

When facing a tradeoff between compliance and schedule constraints, the project manager must first gather complete information about both requirements before determining the best path forward. The scenario indicates the compliance requirement takes effect in nine months, but the launch is in four months — this timing gap is critical information that needs exploration. Meeting with both stakeholders together allows Mateo to clarify whether the feature must be in the initial release or could be added before the nine-month compliance deadline, and whether phased implementation or post-launch enhancement would satisfy both needs. This collaborative approach respects both legitimate concerns while seeking a solution that serves the project's dual success criteria. The closing fact that the compliance deadline is nine months away while launch is in four months suggests there may be viable options that satisfy both constraints if properly explored.

**Why not A:** Approving the carbon offset feature immediately because the sustainability reporting requirement is mandatory would be acting without sufficient information. The compliance deadline is nine months away while the launch is only four months out, creating a timing gap that may allow for phased implementation. Immediately approving a change that delays integration testing by three weeks and risks missing the contractual go-live date conflates the regulatory deadline (nine months) with the launch deadline (four months) without exploring whether both can be met through sequenced delivery.

**Why not B:** Escalating directly to the project sponsor to decide between compliance and schedule treats this as a binary choice before the full picture is understood. The compliance officer and procurement manager may be working from incomplete information about each other's constraints—the compliance officer may not know that the deadline is nine months away while the procurement manager may not know whether a phased approach is feasible. Escalating without first gathering this information hands the sponsor an unnecessarily difficult decision when a working session might reveal a solution that satisfies both success criteria.

**Why not C:** Adding the carbon offset feature to the backlog as lower priority for a future post-launch release assumes the compliance deadline is incompatible with the launch date without verifying this assumption. If the nine-month compliance deadline provides sufficient time for a post-launch feature release, this might actually be a viable path—but choosing it without consulting the environmental compliance officer could result in a missed regulatory obligation if the feature requires integration testing that is only possible before the initial deployment.