12 Factor Team

The '12 Factor App' principles are agreed on as the foundation of Cloud Native applications, but can the same principles be applied to teams? This talk explores if the 12 factors can be re-purposed to create high functioning teams that are ready to build and support Cloud Native applications.

Transcript

1. The 12 Factor Team ALEX LEY PIVOTAL 10 NOV @alexevade t
2. http://12factor.net/ The Twelve Factor App
3. “Are suitable for deployment on modern cloud platforms” “Minimize divergence between development and production, enabling continuous deployment” “Can scale up without significant changes” “Have a clean contract with the underlying operating system, offering maximum portability between execution environments” http://12factor.net/
5. Practices, Processes, Techniques
6. What Factors are there for a Team building a 12 Factor App?
7. I. Codebase One codebase tracked in revision control, many deploys 1. Team Repository One location, tracked in revision control, many contributors
8. I. Team Repository •Your team's `repository`, a goto place for information. •Checklists, play books, documentation links. •Everyone contributes. •Treat it like a codebase, cleanup and clear out, refactor. •GitHub wiki feature is great.
9. II. Know your Dependencies
10. II. Dependencies Who does your team depend on? Who depends on you?
12. Mailing lists for consumers 12
13. III. Configuration Familiar environment and equipment
14. III. Configuration Common starting point.
15. IV. Attach expertise as needed Experts can rotate onto the team and add value
16. IV. Attach expertise as needed Exploratory Testers Security Experts People Managers
17. V. Build, release, run Be responsible for build, release, run stages
18. Who likes getting PagerDuty alerts? V. Build, release, run
19. VI. Share Context Share context across the team
21. VII. Durable Communication Searchable & discoverable communication
23. VIII. Accessible Be accessible to other teams
24. What is your “Port” ? VIII. Accessible
25. IX. Scale Through Interfaces Small teams, scaling through interfaces
26. IX. Scale Through Interfaces User Service Team
27. IX. Scale Through Interfaces API User Profile Team User Search Team
28. X. Expect Changing Priorities & People Maximize robustness to change
29. • Daily standup that highlights issues and dependencies. • Weekly planning meetings with the whole team. • Start new work by hosting an Inception. • Reach milestones by reducing scope. X. Expect Changing Priorities & People
30. XI. Enable Contribution Other teams can contribute
31. • Visible roadmap to spark discussion. • Tag stories that are suitable for Pull Requests. • Provide timely feedback on contributions and say ‘THANK YOU’. • Cross-team pairing! XI. Enable Contribution
33. XII. Fast Feedback Feedback is often and actionable
34. XII. Fast Feedback
35. 12 FACTOR TEAMS ENABLE 12 FACTOR APPS
36. Your app is “12 Factor” but is your Team?
37. CLOUD NATIVE?
38. Migrating to Cloud Native Application Architectures by Matt Stine http://pivotal.io/platform/migrating-to-cloud- native-application-architectures-ebook Free O’Reilly eBook
39. FOR THANKS LISTENING @alexevade t