Project Context
Rippling is preparing to launch a new automated payroll corrections feature for mid-market US customers. The feature recalculates taxes, deductions, and net pay when payroll inputs change after an initial run, reducing manual support work and improving customer trust. You are the program manager coordinating execution across engineering, QA, product, compliance, and customer support.
The project team includes 4 backend engineers, 2 frontend engineers, 1 QA lead, 1 product manager, 1 compliance analyst, and 1 support readiness manager. Leadership wants the feature live before the next quarterly payroll peak in 10 weeks because two competitors have recently launched similar functionality.
Key Stakeholders
- VP of Product wants the feature launched this quarter to support sales commitments.
- Head of Compliance will not approve launch if tax calculations or audit logs are incomplete.
- Engineering Manager is concerned about limited QA bandwidth and an existing backlog of payroll defects.
- Support Director wants low ticket volume at launch and clear rollback steps.
Constraints
- Timeline: 10 weeks total
- Budget: $120,000 remaining, including external tax-rule validation
- Team capacity: 9 dedicated team members, no additional headcount
- Dependency: tax engine update from a platform team due by end of Week 4
- Launch scope: must support all 50 US states at GA, not a state-by-state rollout
- Quality bar: no Sev-1 payroll calculation defects in production
Complications
- The platform team says the tax engine update may slip by 1 week.
- Historical payroll edge cases are poorly documented, and support has identified 18 high-risk scenarios from past incidents.
- Sales has already told three enterprise prospects the feature will be available by the end of the quarter.
Deliverables
- Create a testing and QA execution plan for the 10-week project, including test phases, ownership, and entry/exit criteria.
- Define launch readiness criteria and the trade-offs you would or would not accept if the dependency slips.
- Propose how you would prioritize regression, compliance, and edge-case testing within the available budget and team capacity.
- Outline stakeholder communication, escalation paths, and a rollback plan for launch week.
- Identify the top risks to quality and how you would mitigate them before GA.
