DevOps, Continuous Delivery and Deployment at Hyper Scale

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. |
DevOps, Continuous Delivery
and Deployment at Hyper Scale
Martin Hogg
Senior Director
Oracle Cloud
May 30, 2018
1

Scaling Your Team
2

Lean Product Development
3
• Small cross-functional team.
• Learning loop guides startups to
product market fit & growth.
• Learning loop guides later stage
companies to optimal ROI & TTR.
• Focus on reducing the cycle time.
• But how do you scale this?

Avoid Large Teams
4
Ideas
Build
Product
Measure
Data
Learn
• Communication links for a team on N
are N x (N-1) / 2
• Beyond 7 people things start to suck!
• The learning loop slows.

Try Multiple Teams
• If large teams won’t work we need
multiple teams.
• But how do we divide work between
teams?

You asked for this. So we’re building this.
• Each team builds a piece.
• Then we assemble the
car.
6
While you wait!
Avoid Component Per Team

Ideas
Build
Product
Measure
Data
Learn
Avoid Component Per Team
• Each team’s piece is of no value to
customers on its own.
• Someone needs to break the product
into components.
• Someone needs to integrate the
pieces before you have a product.
• Someone needs to test the product.
• This leads you (back) into waterfall.

Ideas
Build
Product
Measure
Data
Learn
Avoid Role Per Team
• Each team has a single role
– Product Management, Development, Test,
Documentation, Operations, Support
• Each team’s work is of no value to
customers on its own.
• Local optimization within teams.
• Wasteful handoff between teams.
• This leads you (back) into waterfall.

Try Product Per Team
• Each team has their own product.
• Each team has customers.
• Each team rapidly cycles around the
learning loop.
• Each team is independent of others
– Never depend on anything from
another teams that isn’t already
shipping in their product.
– By doing so you implicitly become
responsible for it!
9

1. Now you can go faster
because we solved the
speed problem.
2. Now with less effort
effort problem.
10
3. Now with your friends
space problem.
Try Solving a Sequence of Small Problems

Scaling Your Product
11

Accept Entropy
• Something, somewhere is always
broken.
• Any manual step will have been done
incorrectly.
• Mutable things will have been
mutated in bad ways.
• Bad things will happen.
• Awesome people, trying really hard
cannot overcome this!
12

Avoid
• Sequencing Tasks
• Mutability
• Fixing Things
• Direct Communication
• Manual Workarounds
Try
• Converging to a State
• Immutability
• Replacing Things
• Service Mesh
• High Velocity Automated Fix
Forward
13
Architect for Entropy

Avoid Running your own Platform
• Deploying a platform is very difficult.
• Running a platform is extremely
difficult.
• Finding people to do this for you is
ridiculously difficult!
• Try a managed Platform as a Service
(PaaS) so you can focus on
differentiating value.
14

Scaling Your Culture
15

Avoid
• Mandating Tools
• Mandating Process
• Separate Product Owner
• Fixed Intention
• Command & Control
Try
• Team Chooses Tools
• Team Chooses Process
• Team Owns Product
• Constant Attention
• Autonomy
16
Scaling You Culture

Avoid Pushing … Try Directing
Pushing ➡ Piloting ➡ Navigating ➡ Training ➡ Directing
17

“Any organization that designs a system
(defined broadly) will produce a design
whose structure is a copy of the
organization's communication structure. “
– Mel Conway
18
Accept Conway’s Law

“Awareness, Responsibility, Commitment .“
– John Whitmore
19
Try ARC

Team
• Avoid
– Large Teams
– Component Per Team -
Role per Team
• Try
– Multiple Teams
– Solve Sequence of Problems
Product
• Avoid
– Sequencing Tasks,
Mutability, Fixing Things,
Direct Communication,
Manual Workarounds,
Running your own Platform
• Try
– Convergence to a State,
Immutability, Replacing
Things, Service Mesh, Fixing
Forward Fast
20
Culture
• Avoid
– Mandating Tools, Mandating
Process , Separate Product
Owner, Fixed Intention,
Command & Control,
Pushing
• Try
– Team Chooses Tools, Team
Chooses Process, Team
Owns Product, Constant
Attention, Autonomy -
Directing, ARC
Recap

Thanks!
• Follow: @martinahogg
• Read: http://medium.com/@martinahogg
• Join: https://www.meetup.com/Bristol-Cloud-Native
21

Safe Harbor Statement
The preceding is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
Note: The speaker notes for this slide include
instructions for when to use Safe Harbor
Statement slides.
Tip! Remember to remove this text box.
22

DevOps, Continuous Delivery and Deployment at Hyper Scale

More Related Content

What's hot (17)

Similar to DevOps, Continuous Delivery and Deployment at Hyper Scale (20)

Recently uploaded (20)

DevOps, Continuous Delivery and Deployment at Hyper Scale

Editor's Notes