Your question is Deliver PolicyCenter Upgrade On Schedule. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are the engineering manager leading a Guidewire PolicyCenter upgrade for a large insurer that wants the new release live before peak renewal season. The upgrade includes core rating changes, ClaimCenter and BillingCenter integration updates, and a new producer workflow that Sales has already previewed to field teams. The date is under executive scrutiny because the customer has tied renewal operations and a contract milestone payment to this launch, but your team is carrying defect backlog from the prior release and one of the few engineers who understands the integration layer is splitting time on a production issue. QA is warning that regression coverage is incomplete, while the account team is pushing to keep every committed feature in scope.
| Detail | Value |
|---|---|
| Deadline | 14 weeks to production cutover |
| Team | 6 engineers, 2 QA engineers, 1 product owner, 1 architect shared 30% |
| Systems in scope | PolicyCenter, BillingCenter, ClaimCenter integrations |
| Existing backlog | 18 open Sev-2/Sev-3 defects from prior release |
| Customer users impacted | ~1,200 internal users across underwriting and operations |
| Release window | One weekend cutover; no second production window for 30 days |
| Quality requirement | No Sev-1 defects at launch; rollback plan required |
| Budget | No additional headcount approved |
How would you ensure the team delivers this release on time without sacrificing quality, and how would you handle scope, risk, and stakeholder pressure as the deadline approaches?