Back to Articles
PgMP
Case Study
PgMP Case Study: A Surprise Tax Law Landed in the Middle of a Global ERP Program
P
PMLearning Subject Matter Expert (SME)
July 02, 2026 · 2 min read
1 The Case
A global enterprise was rolling out a standardized ERP template worldwide. The program roadmap was disciplined: design and develop the global template, validate it through a pilot implementation, then deploy across regions in waves. Midway through the template's active development phase, a government unexpectedly announced a new goods and services tax (GST) mandate. Suddenly the template under construction — the foundation every future deployment would inherit — did not reflect the legal reality it would have to operate in.
The Challenge: What Would You Do?
The instinctive responses were all tactical. The development teams wanted to patch the tax logic and keep building — treat it as a scope tweak and protect the schedule. Some component leads argued for logging it as a risk and deferring the work to a later deployment wave, keeping the pilot date intact. Both paths shared the same quiet ethical problem: they treated a legal compliance mandate as an inconvenience to be managed around, rather than a change to what the program was now obligated to deliver. Shipping a template that met the original spec but not the law would have technically 'delivered scope' while failing the business — and everyone downstream would have inherited the failure at multiplied cost.
✓ The Solution
The program manager recognized the GST mandate for what it was: a strategic environmental change, not a component-level defect. Before touching schedules or backlogs, they updated the benefits management plan — because the definition of success itself had changed. The program was no longer delivering a 'standardized global template'; it was delivering a 'tax-compliant standardized global template,' and the plan had to reflect how that new requirement would be tracked, validated during the pilot, and sustained after transition. With the benefits plan re-baselined, the downstream updates — roadmap adjustments, component scope changes, pilot validation criteria — all flowed from an authoritative source instead of ad-hoc patching. Governance approved the revised plan with full visibility of the cost and schedule impact, on the record.
Exam Application & Takeaway
- ▸Regulatory change at program level is a change to the business logic of the program, not just to a work package. The professional response is to update the definition of value first — the benefits management plan — and let execution artifacts inherit from it, with governance informed transparently rather than presented with a quiet workaround. On the PgMP exam, when a regulation, law, or market shift lands mid-program, look past the tactical answers (schedule, risk register, change log) and ask: did this change what 'success' means? If yes, the benefits management plan moves first.