Feedback loops – the second wayFeedback loops – the second waytowards the world of DevOpstowards the world of DevOps

Tapio Rautonen

Tapio RautonenTapio Rautonen

software architectcode craftsman

Breathing the air produced by DevOps culture.

Providing lighting fast software deliveries.

Helping businesses to win with the right software.

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

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

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

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

Feedback loop – the basic oneFeedback loop – the basic one

Dev Ops

product release

deployment failure

Build status feedback loop – in realityBuild status feedback loop – in reality

Dev

Ops

SCM

IssueTracker

1 day to 2 weeks

QA

Build status feedback loop – shortenedBuild status feedback loop – shortened

Dev

SCM

5 mins to 1 hour

CIServer

Biz

Find the real feedback bottlenecksFind the real feedback bottlenecks

Dev Analytics

Ops

sprint2 weeks deployment

2 days

BI report3 monthsre

quirements

1 week

Look for the unpredictableLook for the unpredictable

Dev Ops

demand for virtualized infra

broken loopbonus for number ofservers maintained

The time after a releaseThe time after a release

The product is released...

… but where'sthe feedback?

There's always moreThere's always more

The feedback never

ends after a release

The solutionThe solution

Minimum viable product

Lean

sta

rtup

Mon

itorin

g

User flow

analysis

A/B testing

User experience assessment

Continuous deliveryTe

st a

utom

atio

nR

etrospectives

Infra

stru

ctur

e as

cod

e

Do not try to guessDo not try to guess

if you don't know the realnumbers from production

What is the use ofperformance tests

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

Machine or HumanMachine or Human

Feedback loops

have many forms

The cost of change or bugfixThe cost of change or bugfix

Req

Design

Dev

QA

Operations

Amplify and shorten

Amplify and shorten

the feedback loops!

the feedback loops!

Continual learningContinual learning

Amplify positivepositive feedback

and learn from failurefailure

The big pictureThe big picture

is about collaborationis about collaboration

Dev

OpsBiz

QAAnalytics

User

lives for the feedbacklives for the feedback

Tel +358 10 439 7777Tel +358 10 439 7777gofore@gofore.comgofore@gofore.com

Hämeenkatu 16Hämeenkatu 16FI-33200 TampereFI-33200 Tampere

Urho Kekkosen katu 7 BUrho Kekkosen katu 7 BFI-00100 HelsinkiFI-00100 Helsinki