Project Background

Notionly, a B2B workflow software company, has asked you to lead execution across three overlapping projects in the same quarter: a CRM integration launch, an enterprise security upgrade, and a reporting dashboard redesign. You are the program manager supporting a shared team of 11 people across engineering, design, QA, and data. All three projects matter to revenue, but the team cannot fully staff them in parallel.

The urgency is high because each project has a different business driver: the CRM integration is tied to a signed partnership announcement, the security upgrade is required for two enterprise renewals, and the dashboard redesign is expected to improve self-serve conversion before the next board review.

Key Stakeholders

The VP of Product wants visible customer-facing launches this quarter. The Head of Sales is pushing for the CRM integration because it supports a $1.2M pipeline. The Chief Information Security Officer insists the security upgrade cannot slip because two top customers require SSO and audit logs by quarter-end. The Growth PM wants the dashboard redesign shipped before a marketing campaign already booked for Week 10.

Constraints

• Quarter length: 12 weeks
• Shared team: 6 engineers, 2 designers, 1 QA lead, 1 data analyst, 1 PM
• Budget remaining for contractors: $90,000
• CRM integration requires a third-party API certification that takes 3 weeks
• Security upgrade depends on legal review and customer IT validation in Weeks 5-7
• Dashboard redesign depends on new event tracking instrumentation not yet implemented

Complications

1. One senior backend engineer is allocated 40% to production support for an unstable legacy billing system.
2. The third-party CRM partner may delay certification by up to 2 weeks.
3. Sales has already told two prospects that the CRM integration will be available this quarter.

Your Task

1. Build a prioritization framework for the three projects and explain your trade-offs.
2. Create a 12-week execution plan with sequencing, staffing, and dependencies.
3. Recommend what should be de-scoped, phased, or delayed if capacity becomes constrained.
4. Define stakeholder communication and escalation points.
5. Identify the top risks and mitigation actions.