Summary
Our three reporting teams met their sprint goal in 15 of 18 Q3 sprints, an 83% hit rate. Velocity stayed steady for Claims Platform and Policy Platform. Agent Experience was steady until sprint 6, when an incident and its follow-up took two people for most of the sprint.
Charts
- Claims Platform
- Policy Platform
- Agent Experience
Findings
- Claims Platform met every sprint goal, at an average velocity of 42 points. The team refines two sprints ahead, so it rarely starts a sprint with unclear items.
- Policy Platform missed one sprint goal, in sprint 3, when a dependency on another team arrived late.
- Agent Experience missed two sprint goals, in sprints 2 and 6. Its sprint 6 velocity fell to 20 points after the Sep 15 Agent Portal incident.
- Velocity measures a team against itself. We use it for planning within each team, not to compare teams.
Actions
- Scrum Masters: share Claims Platform's two-sprints-ahead refinement practice at the next Scrum Master community meeting.
- Agent Experience Product Owner: plan Q4 sprint 1 at a lower velocity while the incident follow-up actions finish.
- Policy Platform Scrum Master: confirm cross-team dependency dates at sprint planning, as the sprint planning playbook asks.
Data
| Team | S1 points | S2 points | S3 points | S4 points | S5 points | S6 points | Average velocity | Goals met | Hit rate |
|---|---|---|---|---|---|---|---|---|---|
| Claims Platform | 40 | 43 | 41 | 44 | 42 | 42 | 42 | 6 of 6 | 100% |
| Policy Platform | 36 | 38 | 35 | 39 | 37 | 37 | 37 | 5 of 6 | 83% |
| Agent Experience | 31 | 30 | 30 | 31 | 32 | 20 | 29 | 4 of 6 | 67% |
Source: Pecos Mutual sprint tracker export (fictional). As of September 25, 2026. All figures are fictional demo data.