Project · ATLAS-2-0 · Customer Platform
Atlas 2 0 — forecast slip 4 days
Connected to Jira (ATLAS), GitHub, Figma and Teams. Health recomputed every 5 min.
Health3%
74
of 100
Velocity6%
42 pts
rolling 3 sprints
Open risks33%
4
1 critical
Forecast4%
Dec 13
vs Dec 09 target
Milestones
Critical-path · slip risk highlighted
- Discovery completeOct 04
- Design lockOct 22
- API contracts frozenNov 06
- Code completeNov 25
- Beta launchDec 09
- GAJan 14
Team
Allocation % this sprint
| Person | Role | Alloc | Load |
|---|---|---|---|
| Priya Natarajan | Tech Lead | 142% | |
| Maya Chen | Sr. Designer | 95% | |
| Hannah Weiss | QA Lead | 80% | |
| Felix Romero | Backend Eng | 100% | |
| Yuki Tanaka | Frontend Eng | 88% |
AI Insight
delivery-risk-v4.2
Forecast slipped from Dec 09 → Dec 13 because 3 of the last 5 sprints overran on backend tickets owned by Priya N.
Highest-leverage move: shift 20% of Priya's load to Helios backfill — pulls forecast back to Dec 10.
Risks
- HighCritical-path staff engineer over-allocated (142%)Resource model v1.6
- Med3 design tickets blocked on legal reviewJira: ATLAS-481
- MedSalesforce sync intermittent failures this weekIntegration health
- LowTest coverage 71% (target 80%)CI · GitHub
Activity
- Sprint 18 closed · 42 pts shipped
- New blocker: API contracts on /v2/profile
- Release branch atlas/release-2.0 created
- Design lock approved by Sarah R.