Automation index
How much of a Scrum master’s job can AI already do?
A board and a retro template assemble. Unblocking a team and holding a director do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Scrum master
25%
AI can already do 25% of this job.
#297 / 763
View rankingScrum master
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Facilitate ceremonies, boards and notes.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 45% | +9 |
Flow metrics and impediment reports.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 38% | +6.1 |
Team coaching and internal conflict.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 15% | +2.7 |
Protect the sprint from interruptions.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
Train PO and managers in the method.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Change the system, not just the ritual.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Facilitate ceremonies, boards and notes
- Flow metrics and impediment reports
- Team coaching and internal conflict
- Protect the sprint from interruptions
- Train PO and managers in the method
- Change the system, not just the ritual
- scrum master
- agile coach
Sources for this job· O*NET 13-1111.00· ESCO/ISCO 2421
IS WORK OVER?
Backend developer
27%
#151 / 763
View rankingBackend developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512