How do YOU compare to others in Mobile DevOps Performance, Productivity, and Maturity?
- 1. How do YOU compare to others in Mobile DevOps Performance, Productivity, and Maturity? Anna BÁTKI
- 3. Mobile DevOps, Performance, Productivity, and Maturity Assessment Simplified version at the booth
- 4. 1 4 Creation How long does it take for a scoped feature to be deployed to the app stores? Monitoring How long does it take, when necessary, to release a bug fix after launching a new version of your app? 2 Testing Approximately what percentage of your releases are hotfixes? 3 Deployment How frequently do you deploy new versions of your app to the app stores? 5 Collaboration On a scale of 1-10, how would you rate the level of collaboration across your Mobile Product Organization?
- 5. Platforms (all) 61% native iOS 56% native Android 24% React Native 16% Flutter Company size (Android) 51% - 11 to 250 people the rest about evenly Top 3 app categories Business Finance Health and Fitness Respondents (1k+)
- 6. Top performers / Cutting Edge They perform the best in at least 3 of the performance questions. This covers 16% of our Android sample. 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 🟨 1 4 Creation How long does it take for a scoped feature to be deployed to the app stores? Monitoring How long does it take, when necessary, to release a bug fix after launching a new version of your app? 2 Testing Approximately what percentage of your releases are hotfixes? 3 Deployment How frequently do you deploy new versions of your app to the app stores? 5 Collaboration On a scale of 1-10, how would you rate the level of collaboration across your Mobile Product Organization? 3/5
- 8. 1 Creation
- 9. 1 Creation Deploying new versions of the app to the app stores Cca 35% deploys every 15 to 30 days Cca 30% deploys every 30 to 90 days
- 10. 1 Creation How the top performers manage their dependencies They tend to audit and update all their dependencies regularly (62%) Those who are not in this group are more likely to do it less frequently. (50%)
- 11. 2 Testing Approximately what percentage of your releases are hotfixes? On average, 24% of respondents’ releases are hotfixes, the median is 16% Most of the users do less than 50% hotfixes, based on the standard deviation.
- 12. 2 Testing Top performers and technologies for testing Top performers more likely to use: - Automated UI tests - Contract testing - Snapshot testing than the other companies Tiny bit less likely to do static security analysis.
- 13. 2 Testing Top performers and technologies for testing Top performers more likely to use: - Automated UI tests - Contract testing - Snapshot testing than the other companies Tiny bit less likely to do static security analysis. Top performers trust their automated tests They are more confident in their automated tests before a release than the other companies.
- 14. 2 Testing Top performers mostly focus on doing: - 88% - Unit tests - 66% - automated UI tests - 43% - code coverage analysis - 33% - performance testing - 31% - static security analysis - 31% - snapshot testing
- 15. 2 Testing Top performers mostly focus on doing: - 88% - Unit tests - 66% - automated UI tests - 43% - code coverage analysis - 33% - performance testing - 31% - static security analysis - 31% - snapshot testing Top performers and device testing They are more likely to try to test on as many devices as possible, but at least test on the most popular ones in their user base/potential audience. (57% vs 42%) Top performers tend to test on as many devices as possible twice likely.
- 16. 3 Deployment
- 17. 3 Deployment Top performers deploying new versions of the app - delivery velocity Top performers are more likely to deploy a new version of their app in under 14 days: - 34% of them every 7 days or more frequently - 42% of them every 8 to 14 days.
- 18. 3 Deployment
- 19. 3 Deployment
- 20. 4 Monitoring
- 21. 4 Monitoring
- 22. 4 Monitoring
- 23. 5 Collaboration
- 24. 5 Collaboration
- 25. 5 Collaboration Top performers Tend to be able to relate business impact (downloads, active users, monetisation) to specific releases of - or changes in - their app more likely than the rest. Tend to deliver more likely what the product team initially envisioned. Tend to reuse tools, processes, and practices across multiple mobile teams in their organization.
- 26. The future of MODAS ● define what the what the stages of Mobile DevOps maturity look like ● analyzing: native vs cross-platform ● automated results and suggestions