Applying the 12 Factor principles to teams, as well as apps

Delivered at Continuous Lifecycle London - May 4th 2016

Transcript

1. The 12 Factor Team ALEX LEY PIVOTAL 4th May @alexevade t
2. http://12factor.net/ The Twelve Factor App
3. Codebase Dependencies Config Backing Services Build, Release, Run Processes Port Binding Concurrency Dev / Prod Parity Logs Admin Processes Disposability
4. “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. We want scalability, simplicity, consistency, robustness and clear communication for teams too!
8. Lots of small teams Across many offices With different timezones And many companies contributing
9. What would the 12 Factors be for a Team?
10. I. Codebase One codebase tracked in revision control, many deploys 1. Team Repository One location, tracked in revision control, many contributors
11. 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.
12. II. Know your Dependencies
13. II. Dependencies Who does your team depend on? Who depends on you?
16. Mailing lists for consumers 16
17. III. Configuration Familiar environment and equipment
18. III. Configuration Common starting point.
19. IV. Attach expertise as needed Experts can rotate onto the team and add value
20. IV. Attach expertise as needed Exploratory Testers Security Experts People Managers
21. V. Build, release, run Be responsible for build, release, run stages
22. Who likes getting PagerDuty alerts? V. Build, release, run
23. V. Build, release, run Learn, improve, automate
24. V. Build, release, run “High-performing IT organizations deploy 30x more frequently with 200x shorter lead times; they have 60x fewer failures and recover 168x faster” State of DevOps Report - 2015
25. VI. Share Context Share context across the team
27. VII. Durable Communication Searchable & discoverable communication
29. VIII. Accessible Be accessible to other teams
30. What is your “Port” ? VIII. Accessible
31. IX. Scale Through Interfaces Small teams, scaling through interfaces
32. IX. Scale Through Interfaces User Services Team
33. IX. Scale Through Interfaces API User Profile Team User Search Team
34. IX. Scale Through Interfaces
35. X. Expect Changing Priorities & People Maximize robustness to change
36. • 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. • Explain WHY X. Expect Changing Priorities & People
37. XI. Enable Contribution Other teams can contribute
38. • Visible roadmaps / backlogs 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
40. XII. Fast Feedback Feedback is often and actionable
41. XII. Fast Feedback
42. XII. Fast Feedback Five positive comments for every constructive comment
44. 12 FACTOR TEAMS ENABLE 12 FACTOR APP SUCCESS
45. Your app is “12 Factor” but is your Team?
46. CLOUD NATIVE?
47. Migrating to Cloud Native Application Architectures by Matt Stine http://pivotal.io/platform/migrating-to-cloud- native-application-architectures-ebook Free O’Reilly eBook
48. Beyond the Twelve-Factor App by Kevin Hoffman http://pivotal.io/beyond-the-twelve-factor-app Free O’Reilly eBook
49. FOR THANKS LISTENING @alexevade t