The document discusses the principles of DevOps, emphasizing the importance of systems thinking, feedback loops, and a culture of continual experimentation and learning. It outlines that DevOps is not merely a role or set of tools but emphasizes collaboration among all participants to improve software delivery processes. The focus is on amplifying and shortening feedback loops, understanding customers, and fostering risks and learning to enhance overall business performance.

1. Feedback loops – the second wayFeedback loops – the second way
towards the world of DevOpstowards the world of DevOps
Tapio Rautonen

2. Tapio RautonenTapio Rautonen
software architect
code craftsman
Breathing the air produced by DevOps culture.
Providing lighting fast software deliveries.
Helping businesses to win with the right software.

3. What is DevOps notWhat is DevOps not
● It's not job title, role, team or single person
– calling something DevOps doesn't help anything itself
● It's not tools and automation
– tools and automation are required to achieve the common goals
● It's not NoOps
– the role and requirements of ops is just evolving
● It's not just Dev and Ops
– all participants should collaborate from the beginning
● It's not everything
– DevOps plugs operations into collaborative and agile culture

4. The Three Ways – The First WayThe Three Ways – The First Way
Systems Thinking
– The First Way emphasizes the performance of the entire system,
as opposed to the performance of a specific silo of work. The
focus is on all business value streams that are enabled by IT and
finally delivered to the customer as a form of a service.
– The outcomes of putting the First Way into practice include never
passing a known defect to downstream work centers, never
allowing local optimization to create global degradation, always
seeking to increase flow and to achieve profound understanding
of the system.
The Three Ways: The Principles Underpinning DevOps
- Gene Kim

5. The Three Ways – The Second WayThe Three Ways – The Second Way
Amplify Feedback Loops
– The Second Way is about creating the right to left feedback
loops. The goal of almost any process improvement initiative is
to shorten and amplify feedback loops so necessary corrections
can be continually made.
– The outcomes of the Second Way include understanding and
responding to all customers, internal and external, shortening
and amplifying all feedback loops, and embedding knowledge
where we need it.
The Three Ways: The Principles Underpinning DevOps
- Gene Kim

6. The Three Ways – The Third WayThe Three Ways – The Third Way
Culture of Continual Experimentation and Learning
– The culture fosters two things: continual experimentation, taking
risks and learning from failure; and understanding that
repetition and practice is the prerequisite to mastery. Both are
equally needed.
– The outcomes of the Third Way include allocating time for the
improvement of daily work, creating rituals that reward the team
for taking risks, and introducing faults into the system to
increase resilience.
The Three Ways: The Principles Underpinning DevOps
- Gene Kim

7. Feedback loop – the basic oneFeedback loop – the basic one
Dev Ops
product release
deployment failure

8. Build status feedback loop – in realityBuild status feedback loop – in reality
Dev
Ops
SCM
Issue
Tracker
1 day to 2 weeks
QA

9. Build status feedback loop – shortenedBuild status feedback loop – shortened
Dev
SCM
5 mins to 1 hour
CI
Server

10. Biz
Find the real feedback bottlenecksFind the real feedback bottlenecks
Dev Analytics
Ops
sprint2 weeks deployment
2 days
BI report
3 monthsrequirem
ents
1 week

11. Look for the unpredictableLook for the unpredictable
Dev Ops
demand for virtualized infra
broken loop
bonus for number of
servers maintained

12. The time after a releaseThe time after a release
The product is released...
… but where's
the feedback?

13. There's always moreThere's always more
The feedback never
ends after a release

14. The solutionThe solution
Minimum viable product
Leanstartup
M
onitoring
Userflow
analysis
A/B testing
User experience assessment
Continuous delivery Testautomation
RetrospectivesInfrastructure
as
code

15. Do not try to guessDo not try to guess
if you don't know the real
numbers from production
What is the use of
performance tests

16. Know your usersKnow your users
UXUser
If you don't know what
your users are doing
or what they want
you can not optimize
the funnels

17. Machine or HumanMachine or Human
Feedback loops
have many forms

18. The cost of change or bugfixThe cost of change or bugfix
Req
Design
Dev
QA
Operations
Amplifyandshorten
Amplifyandshorten
thefeedbackloops!
thefeedbackloops!

19. Continual learningContinual learning
Amplify positivepositive feedback
and learn from failurefailure

20. The big pictureThe big picture
is about collaborationis about collaboration
Dev
Ops
Biz
QA
Analytics
User

21. lives for the feedbacklives for the feedback
Tel +358 10 439 7777Tel +358 10 439 7777
gofore@gofore.comgofore@gofore.com
Hämeenkatu 16Hämeenkatu 16
FI-33200 TampereFI-33200 Tampere
Urho Kekkosen katu 7 BUrho Kekkosen katu 7 B
FI-00100 HelsinkiFI-00100 Helsinki