Project Context

NotionHub, a B2B workflow SaaS company, is replatforming its permissions service from a legacy monolith to a new microservice architecture. You are the PM supporting an engineering team of 10 people (6 backend engineers, 2 frontend engineers, 1 QA engineer, 1 engineering manager) and must deliver the migration in 12 weeks before the company’s largest enterprise renewal cycle begins.

The project matters because recent Sev-1 incidents and slow release cycles have delayed enterprise deals worth $3.2M ARR. Leadership wants faster delivery, but the engineering manager insists the team must improve best practices at the same time: code review standards, test coverage, on-call readiness, and release checklists.

Key Stakeholders

The CTO wants the migration completed this quarter. The Head of Sales wants customer-facing permission improvements shipped by week 8 for renewal demos. The Engineering Manager wants to avoid cutting test automation or documentation. Security requires audit logs and access controls before launch.

Constraints

The budget is capped at $180,000, with no new headcount approved. Two senior engineers are each allocated only 50% because they also support production systems. The migration depends on Security sign-off, SRE review, and a vendor API upgrade scheduled for week 5. The launch deadline is September 30.

Complications

1. Current automated test coverage on the permissions codebase is only 42%.
2. One major enterprise customer has requested zero downtime during migration.
3. The vendor API upgrade may slip by up to 2 weeks.

Deliverables

1. Build a 12-week execution plan that balances engineering best practices with feature delivery.
2. Define which engineering practices are non-negotiable for launch versus which can be phased in later.
3. Propose how you would handle the Head of Sales’ week-8 request without creating unacceptable delivery risk.
4. Identify the top risks, dependencies, and mitigation actions.
5. Specify launch readiness criteria, success metrics, and a rollback approach.