Automation index
How much of a Agile coach’s job can AI already do?
A board and a stock retro come earlier. The team stopping the fake sprint do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Agile coach
24%
AI can already do 24% of this job.
#303 / 763
View rankingAgile coach
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 |
|---|---|---|---|
Boards, metrics and the cadence design.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The real retro and the elephant in the room.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Train, unblock and the manager who will not let go.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Scale, dependencies and fake agile.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Conflict, power and not selling extra frameworks.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That they stop faking it, and not inflating velocity.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- retros
- agile cadence
- unblock teams
- flow metrics
- fake agile
- agile training
- dependencies
- velocity
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