You are the engineering manager leading a release that adds offline approval workflows to the Acumatica mobile app for finance and operations managers who need to approve purchase orders and expense claims while traveling. The feature is committed for the next quarterly release because several strategic customers have tied renewals to it, but halfway through execution your team discovers that the current synchronization layer cannot reliably handle conflict resolution for offline edits without a larger refactor. At the same time, one senior engineer who owns the mobile sync architecture is pulled into a production escalation on Acumatica ERP integrations, QA has found regressions in push notifications, and Product is pushing to keep the full original scope because Sales has already previewed it to customers. You need to decide what to cut, defer, or redesign while still protecting release quality, customer trust, and the broader roadmap.
| Detail | Value |
|---|---|
| Engineers | 6 total (3 mobile, 2 backend, 1 QA automation) |
| Release window | 10 weeks remaining |
| Current committed scope | 4 approval flows, offline queueing, conflict handling, audit trail |
| Key dependency | Shared sync service used by Acumatica mobile app and notifications |
| Customer commitments | 5 strategic accounts expecting delivery this quarter |
| Quality bar | No Sev-1/Sev-2 production issues at launch |
| Rollout model | Feature flag with staged release through Acumatica mobile channels |
How would you make and communicate the trade-off needed to keep this release on track, and how would you execute the revised plan so stakeholders stay aligned while launch risk remains controlled?
