Why are so many organizations stuck in the “middle” of DevOps evolution? What’s preventing them from achieving higher levels of performance despite all the automation, tooling, and good practices in place?
Puppet’s State of DevOps Report 2021 provides important research-based clues to answer these questions, supported by the patterns and recommendations in Team Topologies.
In this talk we cover the self-imposed limitations of blindly following some “myths” around DevOps. Almost 80% of organizations are stuck in the “frozen middle” of DevOps evolution because of lack of organizational sensemaking abilities. The margin for growth for these organizations is tremendous, but they need to think beyond technical capabilities to unlock the potential of their teams to deliver with more autonomy and a sense of purpose.
The data shows that Team Topologies provides the necessary organizational and team interaction patterns that help organizations achieve performance metrics such as delivering a new customer change request to live in under one hour, or diagnosing and recovering from a serious issue in production in under an hour.
Fundamentally, we need to supercharge the fundamental principles of DevOps: fast feedback loops, minimal waste, removing bottlenecks, and continuous learning & improvement.
2. Team Topologies
5
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press, 2019
teamtopologies.com/book
3. Remote Team Interactions
Workbook
7
Using Team Topologies
Patterns for Remote Working
Matthew Skelton & Manuel Pais
IT Revolution Press, 2022
teamtopologies.com/workbook
4. “Team Topologies provides a practical
set of templates for addressing the key
DevOps question that others leave as
an exercise for the student”
- Jeff Sussna
8
8. 12
“Success at scale requires optimizing
not for the individual, and not for the
team, but for the wider organization -
the “team of teams”.
Highly evolved organizations have
discovered the patterns that work
well for a fast flow of change”
16. 23
“Organizations should not expect to
become highly evolved just because
they use cloud and automation…
They are held back by organizational
structure and dynamics”
19. “Devops was always as much about
org structure and incentives as any of
the technical details.”
- Andrew Clay Shafer
26
20. 27
Organizations where teams have
strong identities that are well
understood, with clearly defined
responsibilities, are far more likely to
be higher performing
28. 36
“if you simply adopt the team types,
you’re missing one of the key
takeaways... which is paying attention
and being deliberate about teams’
setup and their desired interaction”
47. 57
Adopt: Platform
engineering product
teams
“We consider platform
engineering product teams to be
a standard approach and a
significant enabler for
high-performing IT.”
-- ThoughtWorks Tech Radar, Vol.24, p.9
48. We have an ecosystem of
loosely coupled teams that
promotes fast flow &
continuous learning
58
High perf
52. 62
We have a platform team
that solves common
problems for teams
Mid perf
53. 63
“the existence of a platform team
does not inherently unlock
higher evolution DevOps”
54. “A digital platform is a foundation of
self-service APIs, tools, services,
knowledge and support which are
arranged as a compelling internal
product.”
– Evan Bottcher, 2018
64
Source: https://martinfowler.com/articles/talk-about-platforms.html
55. 65
“Successful platform teams treat
their platform as a product. They
strive to create a compelling value
proposition for application teams”
63. 73
“[Highly evolved platform teams]
understand their internal customers
and offer a curated set of
technologies for infrastructure and
development capabilities”
68. 78
Hold: Platform
engineering product
teams
“We’re seeing the ‘platform
team’ label applied to teams
dedicated to projects that don’t
have clear outcomes or a
well-defined set of customers.”
-- ThoughtWorks Tech Radar, Vol.26, p.18
69. We treat the platform as a
product, a curated
experience for our users
79
High perf
70. Platform as a Product is hard work!
80
● Metrics are stacked against you
● Customer-centricity mindset takes time
● Trust is hard to gain (esp in remote context)
● Adoption lifecycle = “you’re never done”
● Shared services legacy that doesn’t go away
72. 82
“the key to escaping the middle
phase is a successful platform team
approach, which makes sense given the
fact that implementing a platform
approach well requires well-defined
team responsibilities and interactions”