DevOps provides the ability to increase time to market to an new level. The question is no longer if we need to speed up our delivery. The challenge is to find the right „pace“ for your product. Not every organization and every product needs to run at the speed of Netflix and Spotify, even if we’d like it to be like this. We need to adjust the organization, processes and tools appropriatly and to identify the real bottlenecks in the delivery pipeline continuously. And by the way, we need to justify our investment in the DevOps mission. Are we just automating the current processes or can we use this DevOps thing to really support our business? In this talk, I’d like to discuss with you how to find the right design for your delivery process and your organization to behave as a business enabler and how you can scale DevOps within your organization without loosing agility. Let’s explore how we can listen carefully to the unknown customer out there and to build software they really like in the speed of your business.

1. First and Last Mile Innovation Platform
The Need for Speed
DevOpsCon
Berlin 2017
Marc Bauer

2. 2
About me: Marc Bauer
My role: Architect at Capgemini
My job: Agile & DevOps
My hobby:
https://www.linkedin.com/in/bauermarc
@quarkz1010
marc.bauer@capgemini.com

3. Who wants to be the next Netflix, Spotify, …

4. 4
We are looking for archetypes

5. 5
The Microservice Bubble is growing
Source: https://medium.com/netflix-techblog/
Are our company
culture & processes
ready to handle this
increased level of
complexity?

6. 6
State of DevOps 2017 survey by Puppetlabs
DevOps is about
increasing
deployment
frequency while
improving quality.
Are high performers
really the fastest
ones or those with
the best speed?

7. 7
IT Trends Study 2017 by Capgemini
Todays situation Desired Future stateRelease Frequency
Multiple Daily
Daily
Weekly
Monthly
1-2 Times / Quarter
1-3 x / Year
Don’t know

8. How to determine your target speed

9. 9
Evolution of the DevOps idea
Get rid of silos Increase
Time To Market
Gain competitive
Advantage
EVOLUTION

10. 10
There are three major speed characteristics today
Collaboration
„How can we adjust Infra and Operation Services towards
self services for Development and improve collaboration?“
Testing and Integration
„How can we avoid bottlenecks when we speed up?“
DevOps for Innovation
„How can DevOps help us in our innovation
projects“
Time to market increase
“How can we increase time to market from months
to weeks?”
Efficiency in the Digital Age
„How can we use automation to efficiently support a
large number of small and fast paced projects“
Sustain
Speed
Speed Up
Full
Throttle
Delivery Pipeline
“How can we automate the build, test & QA
process”

11. 11
DevOps is not only about high speed
Who is able to
improve and
optimize applications
by using high speed
development and
feedback cycles to
test and experiment
with user
experience?

12. 12
Focus on systems with a high urgency for change
Slow Fast Faster Fastest
Customer facing
applications
Supporting services
Enterprise integration
and middleware
Systems of records
Legacy systems
Start your DevOps
journey with
applications that really
benefit from speed &
agility.

13. 13
Is BI-Modal IT fake news?
The idea of two speed IT
often suggests that you do
not need to take care of
your old, slow, wasted
legacy applications.
… but there is still
important data in those
systems!

14. 14
The pyramid of focus and investment in DevOps initiatives
User
Experience
Business
Involvement
ITIL Alignment
NFR Testing
Delivery Reliability
Technical quality
is the foundation
for speed, but a
missing user and
business focus
will block
nessessary
investments.

15. 15
What is your schema to evaluate your target speed?
Target Market: KNOWN UNKNOWN
Technical Complexity: LOW HIGH
End User: DEFINED AUDIENCE OPEN MARKET
Goal: COST SAVINGS VALUE MAXIMATION
Planning Horizon: LONG SHORT
Quality: MODERATE HIGH
Digital Competition: NOT EXISTING THE WINNER TAKES IT ALL
UI experience: SHOULD BE NICE AWESOME
ITIL processes: NON EXISTENT RIDGID
SPEED INDICATOR

16. 16
The faster you want to be, the more you need to invest in maturity
Deployments
Technical Interdependence
End User
Involvement
Automation
Cloud infrastructure
Embedded Analytics
Closer Ops Integration
Awesome developers, engineers and architects
Empowered Product Owner
Decoupled Architecture
Teams Autonomy
Experiments
Productorientation
Decentralized Decisions

17. 17
There is a break-even point for automation
Costs
Frequency
Can you
argument to go
beyond this
point?
It is not
mandatory to
automate
everything, this
depends on
your intended
deployment
frequency

18. 18
Investments in automation might not scale as expected
The more money you invest in
more frequent delivery, the lower
the relative improvement.
Investment
est
Benefit

19. 19
Increasing speed provides insights at scale if we listen carefully!
PRODUCT
QUALITY
SUCCESS
How do you gather feedback about:
Make stakeholders curious about
insights!
CUSTOMERS

20. How to start?

21. 21
Measure your bottlenecks before starting to optimize
LEAD TIME
IDENTIFY
BOTTLENECKS
IMPROVE
Scrum – Kanban - …
MEASURE

22. 22
Perform a Value Stream Analysis on the delivery process
Create Change
Request
Deploy
Artifact
WAIT TIME:
Ø 12 Days
Wait for
Approval
EXECUTION TIME:
Ø 4 Hours
EXECUTION TIME:
Ø 3 Hours
> Automation > Process
Reengineering
> Refactoring
ERROR RATE:
20%
Understand your process and your bottlenecks before
implementing solutions.

23. 23
Evaluate solutions based on complexity and simplification
Simplification
SpeedSecurity
Complexity
Microservices
Feature based
Deployment
Automated
Security Testing
Trunk based
development
Static Code
Analysis
CI
NFR
Automation
A/B Testing
Feature
Branches
Automated
PerformanceTesting
ITIL
Automation Automated
Provisioning
PaaS
Infrastructure

24. 24
Quantify & Rate your DevOps Investment
Return on Invest =
Value
Costs
What is Value for you?
Speed Booster
Innovation
Quality Improver
How do you rank DevOps
Items in your Backlog?
…productively and creatively delivering products of the highest possible value
(Scrum Guide)

25. How to scale this in the
organization?

26. 26
Establishing frictionless delivery will affect the way you work
Platform OrganizationTeam

27. 27
Todays DevOps team challenge is about balancing power & responsibility
AUTONOMY ALIGNMENT
VS

28. 28
How much autonomy do you give to your teams?
Team Setup
Product Strategy
Infrastructure
Technology
How can the
whole
organization
benefit?

29. 29
The DevOps Platform is an ecosystem of tech, process & mindset
Frictionless
Processes
Decoupled
Architecture
Delivery Platform
Agile Mindset
DevOps
Platform

30. 30
Because we work for the teams and
measure success in value contribution!
DevOps Platforms combine reusability & agility for the sake of speed
Why are you sure that your DevOps Platform Efforts support teams better then my
favorite 1990’s Development Framework?
$
BOSS Net Promoter Score
Usage Index
Fundraising
DevOps
Guy

31. 31
Current organizational structures are designed by old hierarchical patterns
Source: scrum.org

32. 32
We need Product based organizations…
…within a protected
environment !
Engineering Services
provide DevOps
Assets & Services to
The Studio
Measurement
Services provide
insights into
Source: Scrum.org
Shared services are
the bridge to the rest
of the organization
Leadership Services
foster Agility and
Innovation

33. 33
The agile Studio Organisational Model
Shared Studio Services and Assets
Product Backlog
Product Product
Domain Domain
ProductProduct
Cross cutting Communities of Practice
Cross cutting Disciplines
Studio
Product Backlog Product Backlog Product Backlog
Engineering Services

34. 34
A sample of the Studio model for a fiction e-Commerce scenario
Backlog
Team 1 Team 2
Integration
Team
Online Shop
Team 3
Backlog
eCommerce Europe eCommerce Asia
Online Shop
…
Team
Backlog
… Team
… Backlog
Inventory
Mobile, Backend, Platform … Community of Practice
Platform Architects
Product Owner
Product Owner
Product
Owner
Shared Services and Assets
Enterprise
Architecture
Guidelines &
Best Practices
Maturity
Measures
Store Self Service
PMO Data Security
& Privacy
Finance
& Risk
Data Center
Hook
Tools &
Platform
Engineering Services
Monitoring &
2nd Level
Infra SME Infrastructure &
Automation (CI, CD …)
Cloud DevOps Engineers /
CoP

35. 35
What did not work – shared goals but still local optimization
Transcendent
Vision
Dev / IT
Ops Supplier
Business
Yes, we will work together, but first
of all we take care of ourselves…
… because we define success
different!

36. 36
Give your teams the ultimate goal which is business success
Process Execution
Lead Generation
Active Users
Market Share
Happy Customers
Quick Response Time
What you measure is what you get!
Robert Kaplan
What is success ?
Do you trust your product to just
build upon value based KPI?
Yes?
Then think about building
Software – as – a Service Model!

37. 37
Summary
Think about your individual speed
Think in products
Think of responsibility
Think about protected environments
… and make people excited about speed!

38. Thank you!