Payroll Replacement in a Regulated, Contract-Constrained Environment
Your PMO assigns you to lead a payroll replacement for a 2,400-employee manufacturer operating in three provinces. The CFO signed a fixed-price SaaS contract before requirements were baselined. A new tax-reporting regulation takes effect in 11 months, and late compliance triggers daily penalties. The IT director wants two-week sprints; HR insists on waterfall requirements sign-off because payroll errors are highly visible. The vendor requires a single configuration freeze eight weeks before go-live. The PMO mandates stage gates at initiation, design, and readiness, but defines them only for waterfall projects. Two business units use different overtime rules, and a third is acquiring a site with union-specific pay codes. You have 1.5 business analysts and no dedicated change manager. The sponsor wants a lifecycle recommendation at next week’s steering committee.
1. Identify the environmental factors and organizational process assets that constrain the lifecycle choice, and explain how each should influence your recommendation.
Read the worked answer
Environmental factors (EEFs) include the tax regulation and its 11-month penalty-backed deadline, provincial labor rules and the union pay codes, and the vendor’s configuration-freeze method. These push toward a fixed outer date and controlled baselines. Organizational process assets (OPAs) include the PMO’s waterfall-only stage gates and the already-signed fixed-price contract; they constrain how much iterative delivery can be used unless the gates are tailored. The HR concern is not merely cultural: payroll errors are highly visible, so requirements and parallel-run criteria need formal gates. Recommendation: hybrid-predictive governance gates for regulatory compliance, contract scope, and payroll parallel run, with iterative configuration increments inside design and build. Do not choose pure agile because the contract and stage gates would create false control; do not choose pure waterfall because two-week feedback is needed for configuration. Tailor gate criteria rather than bypassing them, and document the tailoring in the project management plan.
2. Recommend a tailoring approach and the first three governance actions you would take.
Read the worked answer
First, tailor the three PMO gates: the initiation gate confirms charter, regulatory traceability owner, and decision rights; the design gate requires baselined payroll rules, union pay codes, and vendor configuration assumptions; the readiness gate requires parallel-run accuracy thresholds and cutover rollback criteria. Second, establish a joint HR-IT-vendor requirements baseline with a traceability matrix so the contract’s fixed scope can be managed through change control. Third, create a stakeholder and change plan: use the 1.5 business analysts as payroll process leads, recruit unit-level payroll champions, and schedule two-week configuration demos for HR. Also assign a single risk owner for regulatory compliance and a single owner for vendor configuration freeze. The reasoning is that the gates provide control while the demos provide feedback; neither replaces the other. Escalate to the sponsor only if the PMO refuses tailored gate criteria, because the PMO process is an OPA that can be tailored with governance approval.
3. What contractual and scope risks arise from signing before baselining, and how would you handle them without reopening the contract?
Read the worked answer
Signing before baselining creates scope ambiguity, vendor assumptions, and change-order exposure. The contract may cap scope to the vendor’s standard configuration, while the provinces’ overtime rules and union pay codes may require customization. Handle it without reopening the contract by (1) running structured requirements workshops with HR, IT, and the vendor; (2) documenting assumptions and gaps in a requirements traceability matrix; (3) using the contract’s change-control clause for any gap that is truly outside scope; (4) agreeing acceptance criteria and parallel-run tolerances early; and (5) tracking vendor dependencies and configuration freeze dates in the schedule. Do not verbally accept extra scope. If the vendor claims the union pay codes are out of scope, ask for a written impact assessment and escalate to the sponsor with options: pay for customization, change payroll process, or accept manual workaround. The key judgment is to protect the regulatory date while making scope and cost trade-offs visible, not to pretend the contract is complete.