The state of mobile release management.

How mobile releases really work, from the engineering managers and engineers behind them. Broken out by team size and release cadence.

Read the findings for a team like yours
Team size
How often you releaseWeekly
Small teams · Weekly releases
The stunt plane
93% of EMs lose three or more hours every week to status updates.
Read this segment
Key findings · All teams

What holds for every mobile team

These findings come from every engineering manager and engineer surveyed, across all team sizes and release cadences. For the numbers behind a team like yours, pick your segment above.

What a release costs

What a release costs mobile teams

Every release takes time out of the roadmap: EMs spend about five hours of each release cycle on status updates, and an engineer on release duty finishes about half of their sprint work. For a team releasing every two weeks, the status updates alone come to more than three working weeks of an EM's year.

Nearly every EM loses three or more hours a release cycle to status updates.

96% spend three or more hours, and the load grows with the company: 55% of EMs at companies of 5,000 to 9,999 employees spend six to 10 hours, against 13% at 500 to 999.

Hours a release cycle EMs spend on status updates
1 to 2 hours4%
3 to 5 hours68%
6 or more hours28%

An engineer on release duty finishes about half of their sprint work.

On average, EMs expect 52% of planned sprint work from whoever is acting as release manager.

Planned sprint work EMs expect from the engineer on release duty
Under 25%6%
25 to 49%38%
50 to 74%47%
75 to 90%9%

Engineers spend about half of release time on coordination busywork.

EMs estimate 48% on average, and the share rises with the number of people a release touches.

Share of release time on coordination busywork · by people per release
20 or fewer people38%
All teams48%
31 or more people54%

Get the full report.

Every finding across all six segments, ready to pass along to your team.

Benchmark your team