Optimizing Release Processes For Growing Mobile Teams

Transcript

2. Optimizing Release Processes for Growing Mobile teams Annunziata Kinya Organizing Droidcon Kenya The Techie Garage
3. Engineering Manager Product Manager Android Team QA Testers Web Team Backend Team UI/UX Design Team Product The Moving Parts
5. Overall Goal • Deliver VALUE to the end users of the product
6. Case Study: Kyosk
7. Kyosk: Minimum Viable Product (V1)
8. V1 Features
9. Engineering Manager Product Manager Android Team QA Testers Web Team Backend Team UI/UX Design Team Engineering Structure
10. Android Code Workflow
11. Kyosk: Multiple Product Versions (Version ‘n’)
12. Version ‘n’ Features
13. Version ‘n’ Features
14. Engineering Manager Product Manager Android Team QA Testers Web Team Backend Team UI/UX Design Team Engineering Structure Engineering Manager Product Manager Android Team QA Testers Web Team Backend Team UI/UX Design Team Engineering Manager Product Manager Android Team QA Testers Web Team Backend Team UI/UX Design Team Feature A Team Feature B Team Feature C Team
15. Android Code Workflow
16. Problem • Teams being blocked from releasing by other teams due to: ◦ Untested work ◦ Interdependencies from other teams e.g. backend APIs • False negatives from regression tests
17. Solution • Feature flags • A hybrid release strategy (feature-based + release trains) • Individual develop branches for teams
18. Android Code Workflow
19. ‘House Keeping’ • Ownership and regular cleanup of feature flags • Regular merges from RC into individual develop - Automate a CI/CD workflow ✅
21. Thank You!