12 - Critical Path, Risk Analysis, And Integrated Schedule¶
Purpose¶
Define the requirement-level critical path, link it to quantified risks, and maintain a release-ready schedule for MVP and MSP.
Milestone Baseline¶
Milestone |
Date |
Definition |
|---|---|---|
MVP scope freeze |
2026-04-15 |
MVP requirements locked and approved |
MVP cohort launch |
2026-06-01 |
First family cohorts go live |
MVP evidence readout |
2026-08-31 |
8-12 week conversion/attendance/outcome evidence complete |
MSP feature complete |
2026-10-15 |
Commercial, retention, and trust capabilities completed |
MSP commercial launch |
2026-11-15 |
Full MSP go-live decision and launch |
Critical Path Definition¶
Critical path = sequence of tasks with zero schedule float where delay directly delays a committed milestone.
Industry Context: Critical Path Discipline¶
Netflix’s migration from DVD to streaming provides the clearest modern example. Video encoding infrastructure was identified as the single critical-path dependency — every regional launch, every device partnership, and every content licensing deal was blocked until encoding at scale was solved. Netflix moved non-critical-path storage work to AWS S3 and CloudFront specifically to remove it from the critical chain and keep engineering focused on the constraint. The organizational insight: if every workstream is treated as critical, none of them are accountable for the constraint, because a delay anywhere can always be attributed to a delay everywhere.
Zoom reached the same conclusion around codec performance during early scaling. Sales could close, marketing could run campaigns, and customer success could onboard users — none of it produced durable value if the codec degraded on low-bandwidth connections. Zoom built a proprietary codec to remove the dependency on third-party performance. That was a product and engineering investment decision made entirely because of critical-path logic, not feature preference.
CP-03 in this plan, session quality baseline, is the direct analog. Booking flow, payment processing, and tutor onboarding are all downstream workstreams. Delay CP-03 and every one of them slips — not because they failed independently, but because the constraint they depend on was not resolved first.
Critical Path Chain (MVP -> MSP-R1)¶
CP ID |
Task |
Duration |
Dependency |
Planned Finish |
Float |
Owner |
|---|---|---|---|---|---|---|
CP-01 |
Requirement baseline and scope freeze (REQ-001/003/009/010) |
3 weeks |
None |
2026-04-15 |
0 days |
Product |
CP-02 |
Tutor recruiting + continuity operating model (REQ-002) |
5 weeks |
CP-01 |
2026-05-20 |
0 days |
Tutor Ops |
CP-03 |
Session reliability hardening (REQ-003) |
6 weeks |
CP-01 |
2026-05-25 |
0 days |
Engineering |
CP-04 |
Booking + enrollment conversion flow (REQ-001) |
5 weeks |
CP-01 |
2026-05-22 |
0 days |
Growth + Eng |
CP-05 |
Consent and trust controls (REQ-009) |
4 weeks |
CP-01 |
2026-05-15 |
3 days |
Legal + Eng |
CP-06 |
Instrumentation for KPI proof (REQ-010) |
4 weeks |
CP-01 |
2026-05-18 |
2 days |
Product Ops |
CP-07 |
MVP launch readiness assembly |
2 weeks |
CP-02..CP-06 |
2026-06-01 |
0 days |
PMO |
CP-08 |
Evidence cycle execution and readout |
12 weeks |
CP-07 |
2026-08-31 |
0 days |
PM + Curriculum |
CP-09 |
Subscription plan matrix + billing readiness (REQ-006) |
6 weeks |
CP-08 |
2026-10-10 |
0 days |
Revenue + Eng |
CP-10 |
MSP launch gate closeout |
4 weeks |
CP-09 |
2026-11-15 |
0 days |
Product Council |
Visual Schedule Controls (Agile + PMBOK)¶
Critical Path Timeline (Gantt Overview)
PMBOK schedule baseline with Agile release checkpoints. Red segment marks the highest schedule risk area requiring daily monitoring.
Risk Heatmap (Probability x Impact Days)
Risk register translated to a PMBOK probability-impact matrix. Use this in weekly Agile planning to decide mitigation sprint allocation.
Tooling Examples For Critical Path Control¶
Jira Advanced Roadmaps: map dependency links across initiatives and auto-highlight any
CP-Yesrequirement that is blocked or slipping.Azure DevOps Delivery Plans: visualize cross-team dependencies, then query and pin all
P0+ critical-path items to an executive dashboard.GitHub Projects + Milestones: link blocking issues and enforce milestone ownership for each CP task to keep delay accountability explicit.
Jama Connect / IBM DOORS Next: baseline CP-linked requirements and run impact analysis when requirement changes would affect committed milestone dates.
Non-Critical But High-Value Work (Managed Slack)¶
Workstream |
Related Requirements |
Planned Window |
Float Target |
|---|---|---|---|
Attendance rescue automation |
REQ-007 |
Q3 2026 |
10 business days |
Tutor fit-change SLA automation |
REQ-011 |
Q4 2026 |
8 business days |
Group offering enablement |
REQ-012 |
Q1 2027 |
15 business days |
Risk Analysis (Schedule-Linked)¶
Risk ID |
Risk |
Prob. |
Impact (Days) |
Trigger |
Mitigation |
Contingency Owner |
|---|---|---|---|---|---|---|
RSK-CP-01 |
Requirement churn after scope freeze |
Medium |
5-10 |
New unresolved discovery issue in freeze window |
Enforce change-control board and reserve 10% contingency |
PM |
RSK-CP-02 |
Tutor capacity shortfall |
High |
7-14 |
Weekly continuity <80% in pre-launch |
Build bench capacity and accelerate screening pipeline |
Tutor Ops |
RSK-CP-03 |
Live session reliability defects |
Medium |
5-12 |
Sev-2 incidents in staging burn-in |
Reliability sprint + canary holdback |
Engineering |
RSK-CP-04 |
Progress-report data quality gaps |
Medium |
4-8 |
Metric reconciliation failure |
Instrumentation QA and fallback report template |
Product Ops |
RSK-CP-05 |
Billing integration delay |
Medium |
7-10 |
Failed acceptance tests in MSP window |
Parallel test harness and narrowed launch scope fallback |
Revenue + Eng |
RSK-CMP-01 |
Consent/compliance controls incomplete |
Low |
10+ |
Audit evidence incomplete |
Legal escalation and phased launch gating |
Legal + Security |
Integrated Schedule (Quarter View)¶
Quarter |
Schedule Focus |
Primary Deliverables |
Release Output |
|---|---|---|---|
Q2 2026 |
MVP critical path completion |
CP-01 to CP-07 |
MVP cohort launch |
Q3 2026 |
Evidence and hardening |
CP-08 + non-critical optimizations |
MVP evidence readout |
Q4 2026 |
Commercial readiness |
CP-09 and CP-10 |
MSP commercial launch |
Q1 2027 |
Scale optimizations |
Group offer, automation, partnership enablement |
MSP-R2 |
Release Calendar¶
Release |
Date |
Scope |
Gate Requirement |
|---|---|---|---|
MVP-R1 |
2026-06-01 |
Core booking, matching, tutoring, progress |
Gate G2 pass |
MVP-R1.1 |
2026-07-15 |
Attendance rescue and UX hardening |
Gate G3 readiness subset |
MSP-R1 |
2026-11-15 |
Plan matrix, retention ops, trust package |
Gate G5 pass |
MSP-R2 |
2027-02-15 |
Group option and expanded channel support |
Gate G5.1 pass |
Schedule Governance And Escalation¶
Weekly: CP status review with red/amber/green and float consumption.
Biweekly: Risk impact re-estimation in days and mitigation burn-down.
Monthly: Re-forecast milestones if cumulative float consumption exceeds 30%.
Escalation rule: Any CP task delayed >3 business days triggers executive review.