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

Slide 1

Slide 1 text

The 12 Factor Team ALEX LEY PIVOTAL 4th May @alexevade t

Slide 2

Slide 2 text

http://12factor.net/ The Twelve Factor App

Slide 3

Slide 3 text

Codebase Dependencies Config Backing Services Build, Release, Run Processes Port Binding Concurrency Dev / Prod Parity Logs Admin Processes Disposability

Slide 4

Slide 4 text

“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/

Slide 5

Slide 5 text

Practices, Processes, Techniques

Slide 6

Slide 6 text

We want scalability, simplicity, consistency, robustness and clear communication for teams too!

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

Lots of small teams Across many offices With different timezones And many companies contributing

Slide 9

Slide 9 text

What would the 12 Factors be for a Team?

Slide 10

Slide 10 text

I. Codebase One codebase tracked in revision control, many deploys 1. Team Repository One location, tracked in revision control, many contributors

Slide 11

Slide 11 text

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.

Slide 12

Slide 12 text

II. Know your Dependencies

Slide 13

Slide 13 text

II. Dependencies Who does your team depend on? Who depends on you?

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Mailing lists for consumers 16

Slide 17

Slide 17 text

III. Configuration Familiar environment and equipment

Slide 18

Slide 18 text

III. Configuration Common starting point.

Slide 19

Slide 19 text

IV. Attach expertise as needed Experts can rotate onto the team and add value

Slide 20

Slide 20 text

IV. Attach expertise as needed Exploratory Testers Security Experts People Managers

Slide 21

Slide 21 text

V. Build, release, run Be responsible for build, release, run stages

Slide 22

Slide 22 text

Who likes getting PagerDuty alerts? V. Build, release, run

Slide 23

Slide 23 text

V. Build, release, run Learn, improve, automate

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

VI. Share Context Share context across the team

Slide 26

Slide 26 text

Slide 27

Slide 27 text

VII. Durable Communication Searchable & discoverable communication

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

VIII. Accessible Be accessible to other teams

Slide 30

Slide 30 text

What is your “Port” ? VIII. Accessible

Slide 31

Slide 31 text

IX. Scale Through Interfaces Small teams, scaling through interfaces

Slide 32

Slide 32 text

IX. Scale Through Interfaces User Services Team

Slide 33

Slide 33 text

IX. Scale Through Interfaces API User Profile Team User Search Team

Slide 34

Slide 34 text

IX. Scale Through Interfaces

Slide 35

Slide 35 text

X. Expect Changing Priorities & People Maximize robustness to change

Slide 36

Slide 36 text

• 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

Slide 37

Slide 37 text

XI. Enable Contribution Other teams can contribute

Slide 38

Slide 38 text

• 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

Slide 39

Slide 39 text

Slide 40

Slide 40 text

XII. Fast Feedback Feedback is often and actionable

Slide 41

Slide 41 text

XII. Fast Feedback

Slide 42

Slide 42 text

XII. Fast Feedback Five positive comments for every constructive comment

Slide 43

Slide 43 text

Slide 44

Slide 44 text

12 FACTOR TEAMS ENABLE 12 FACTOR APP SUCCESS

Slide 45

Slide 45 text

Your app is “12 Factor” but is your Team?

Slide 46

Slide 46 text

CLOUD NATIVE?

Slide 47

Slide 47 text

Migrating to Cloud Native Application Architectures by Matt Stine http://pivotal.io/platform/migrating-to-cloud- native-application-architectures-ebook Free O’Reilly eBook

Slide 48

Slide 48 text

Beyond the Twelve-Factor App by Kevin Hoffman http://pivotal.io/beyond-the-twelve-factor-app Free O’Reilly eBook

Slide 49

Slide 49 text

FOR THANKS LISTENING @alexevade t