Lesson 9 of 19Article14 min
Manager's Perspective on CI/CD
Engineering managers use DORA (DevOps Research and Assessment) metrics to measure delivery health. Mobile teams face unique constraints — store review times, signing complexity, and device fragmentation — but the metrics still apply.
DORA metrics for mobile
Engineering managers use DORA (DevOps Research and Assessment) metrics to measure delivery health. Mobile teams face unique constraints — store review times, signing complexity, and device fragmentation — but the metrics still apply.
A mature RN CI/CD pipeline reduces 'it works on my machine' releases and makes rollback predictable.
DORA metrics influenced by CI/CD
What managers should track
- Deployment frequency: how often you ship to production (weekly is healthy for mobile).
- Lead time for changes: commit to production — target under 1 week for non-hotfix.
- Change failure rate: % of releases causing incidents — target under 15%.
- Mean time to recovery: hours from incident to hotfix in stores — target under 4 hours.
- CI cost per month: Mac runner minutes, Genymotion SaaS, artifact storage.
Investment decisions
- Staging environment ROI: one prevented bad release pays for months of CI infrastructure.
- Release cadence: weekly trains reduce batch size and make debugging easier.
- QA gates: automate regression; reserve human QA for UX, accessibility, and store listing.
- Runbooks: document hotfix procedure, on-call rotation, and store rollback steps.