Slide 1

Slide 1 text

The 12 Factor Team ALEX LEY PIVOTAL 10 NOV @alexevade t

Slide 2

Slide 2 text

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

Slide 3

Slide 3 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 4

Slide 4 text

No content

Slide 5

Slide 5 text

Practices, Processes, Techniques

Slide 6

Slide 6 text

What Factors are there for a Team building a 12 Factor App?

Slide 7

Slide 7 text

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

Slide 8

Slide 8 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 9

Slide 9 text

II. Know your Dependencies

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

11

Slide 12

Slide 12 text

Mailing lists for consumers 12

Slide 13

Slide 13 text

III. Configuration Familiar environment and equipment

Slide 14

Slide 14 text

III. Configuration Common starting point.

Slide 15

Slide 15 text

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

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

VI. Share Context Share context across the team

Slide 20

Slide 20 text

20

Slide 21

Slide 21 text

VII. Durable Communication Searchable & discoverable communication

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

VIII. Accessible Be accessible to other teams

Slide 24

Slide 24 text

What is your “Port” ? VIII. Accessible

Slide 25

Slide 25 text

IX. Scale Through Interfaces Small teams, scaling through interfaces

Slide 26

Slide 26 text

IX. Scale Through Interfaces User Service Team

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

X. Expect Changing Priorities & People Maximize robustness to change

Slide 29

Slide 29 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. X. Expect Changing Priorities & People

Slide 30

Slide 30 text

XI. Enable Contribution Other teams can contribute

Slide 31

Slide 31 text

• 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

Slide 32

Slide 32 text

32

Slide 33

Slide 33 text

XII. Fast Feedback Feedback is often and actionable

Slide 34

Slide 34 text

XII. Fast Feedback

Slide 35

Slide 35 text

12 FACTOR TEAMS ENABLE 12 FACTOR APPS

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

CLOUD NATIVE?

Slide 38

Slide 38 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 39

Slide 39 text

FOR THANKS LISTENING @alexevade t