This document discusses DevOps feedback loops and the importance of closing the loop between development and operations. It provides examples of where feedback comes from in operations, including from people and machines, and where feedback needs to go in development, such as to developers and development systems. The key message is that closing the feedback loop through continuous feedback is critical for DevOps in order to optimize software development and address issues quickly before they become bigger problems.

1. What is a DevOps Feedback Loop?
By Paul Peissner
Agile/DevOps Advocate

2. What is a DevOps Feedback Loop?
What is the Agile/DevOps Insanity Loop? – The BIG / little PROBLEM
BIG
little agile
enterprise

3. What is a DevOps Feedback Loop?
What is the Agile/DevOps Insanity Loop? – The BIG / little PROBLEM - 1
1) What is an Agile “cadence & culture”?
- The development PACE, App size and a more unified Dev & Ops
- Collaboration & learning vs. siloes & blame – it’s not the same culture!
Big-Bang culture change…it’s NOT smaller versions of the same
BIG
Waterfall timelines &
organizational siloes agile
little
enterprise

4. What is a DevOps Feedback Loop?
What is the Agile/DevOps Insanity Loop? – The BIG / little PROBLEM - 2
BIG
little agile
2) What is the definition of insanity?
- Agile’s short Dev patterns (Ops is too slow & disconnected to provide Dev feedback)
- Ops/Bus. long-term data monitoring (Dev’s repeated faster cycles gets little feedback)
BIG enterprise
Long timeframes to eval.
SW’s Ops support costs,
and business success
Listening and learning-sync is way off…

5. What is a DevOps Feedback Loop?
What is the Agile/DevOps Insanity Loop? – The BIG / little PROBLEM - 3
BIG
little agile
Big requests not aligned
to iterative agile goals…
…wrong interaction types
3) What is Business’ expectation from software?
- Business requesters have little knowledge about Dev’s core strengths
- Dev iterations & backlog mgt…is it a “black box of communication” to business?
Set expectations / educate the business…
enterprise

6. What is the Agile/DevOps Insanity Loop? – The BIG / little PROBLEM - 4
CEO’s measure Bus. data
to determine Dev success
What is a DevOps Feedback Loop?
little agile
4) What is the CEO’s definition of “DONE or Success”?
- Integrate the whole Dev & Ops portfolio and track data to/from Ops & business
- Agile/DevOps teams measure their projects and deployments for “success data”
“Definition of done” for Projects/Products/Businesses
BIG enterprise

7. What is a DevOps Feedback Loop?
Anticipate BIG / little PROBLEMS…expect Enterprise “Misalignment”
Optimized for
short-term agility
Accountable and connected
with long-term and
far-reaching performance
and quality expectations!
Ops feedback produces better Dev…
Quality – Security – Sustainability – Scalability

8. What is a DevOps Feedback Loop?
Where do DevOps feedback loops come from…
Where does DevOps feedback go…

9. Ops
What is a DevOps Feedback Loop?
Feedback comes from Ops PEOPLE
Where do DevOps feedback loops come from…
Ops Front Office Ops Back Office
Asset, System
or Service ID
X
End User or
Business line
(Person)
“P”
P
P2P
P
P
Support/Service
Management
(Person)
“P”

10. What is a DevOps Feedback Loop?
Feedback comes from Ops MACHINES
Ops
Feedback comes from Ops PEOPLE
Where do DevOps feedback loops come from…
Ops Front Office Ops Back Office
Asset, System
or Service ID
X
End User or
Business line
(Person)
“P”
Production, Cloud
or Data Center
(Machine)
“M”
System/Cloud
Management
(Machine)
“M”
P
M
M2M
P2P
M
P
P
M
Support/Service
Management
(Person)
“P”

11. What is a DevOps Feedback Loop?
Feedback comes from Ops MACHINES
Ops
Feedback comes from Ops PEOPLE
Where do DevOps feedback loops come from…
Ops Front Office Ops Back Office
Asset, System
or Service ID
X
End User or
Business line
(Person)
“P”
Production, Cloud
or Data Center
(Machine)
“M”
System/Cloud
Management
(Machine)
“M”
P
M
P2M
M2M
P2P
M2P
M
P
P
M
The above graphic inspired by Andi Mann’s article/image on DevOps.com:
Four key vectors for closing the DevOps feedback loop
Support/Service
Management
(Person)
“P”

12. What is a DevOps Feedback Loop?
Feedback needs to go to Dev PEOPLE
Feedback needs to go to Dev system flows?
Ops
Ops Front Office Ops Back Office
System/Cloud
Management
(Machine)
Asset, System
or Service ID
?
Dev Improve Dev
X
End User or
Business line
(Person)
“P”
Production, Cloud
or Data Center
(Machine)
“M”
“M”
Release or
Deploy ID
Support/Service
Management
(Person)
“P”
P
M
P2M
M2M
P2P
M2P
P
M
D
S
“D”
Developer
Where does DevOps feedback go…

13. Ops
Ops Front Office Ops Back Office
System/Cloud
Management
(Machine)
Asset, System
or Service ID
That is a great question!
And a longer discussion…
Release or
Deploy ID
Improve Dev
Dev Project
or Product ID
Fast-fix
traceability
Future
influence
Purge
forever
Dev
Improve Reuse
X
End User or
Business line
(Person)
“P”
Production, Cloud
or Data Center
(Machine)
“M”
“M”
Support/Service
Management
(Person)
“P”
P
M
P2M
M2M
P2P
M2P
P
M
DevOps feedback loops…
Agile feedback loops…
What is a DevOps Feedback Loop?
What is a Dev system flow? ?
Project/Flow
Template ID
Recommend
Reuse
Versioned
/Managed
Code
“D”
Developer
System
“S”
S

14. What is a DevOps “Dev System” flow? – Short Summary!
GGGiiitttEEEyyyeee
Private Cloud
Your Data Center
Public Clouds
Dashboards
Integrated portfolio, tool & process data (short-term & long-term) with traceability
Feedback
Evolving
Software
Practices
Open Source and
Accelerated
Dev Designs
Automation,
Cloud and
DevOps

15. What is a DevOps “Dev System” flow? – Short Summary!
GGGiiitttEEEyyyeee
Private Cloud
Your Data Center
Public Clouds
Dashboards
Integrated portfolio, tool & process data (short-term & long-term) with traceability
Feedback
Any/All Dev
methodologies
Any location
with real-time &
historic insights
Maximize Open Source
Instant-on libraries of
Dev tooling with ready-to-reuse
(and changeable)
project templates / flows
Maximize the use of
Automation, Cloud &
version everything!
LISTEN to everything
& everyone!
Enterprise Dev System Flows With Many Options – As Unique As The Project Requires!

16. What is Driving DevOps?
12
10
0 2 4 6 8
Automation
Various Sources:
Low
Medium
Automation
High
Automation
$ Cost
Quality
Productivity
http://www.methodsandtools.com/archive/archive.php?id=94,
http://www.infoq.com/articles/test-automation-continuous-delivery
http://devopsanywhere.blogspot.com/2013/02/sysadmin-productivity-and-chef.html
Full
Automation
Automation
Better Continuous Integration
Better Dev?
Cloud
Better Ops?
Open Source Graphic Source: Nathan Sowatskey, Cisco, DevNet Team
DevOps4Networks 2014 Presentation
Agile
Big Data / SaaS

17. The Enterprise Agile/DevOps Maturity Curve Model!

18. The Enterprise Agile Maturity Curve Model!
Agile investigation
Agile Adoption
Agile practice
Cross-discipline Agile
Agile mastery
Business Agility
Corporate Agility
Scaled Agile

19. The Enterprise DevOps Maturity Curve Model!
Dev process adoption
Open Source - Dev process experimentation
Dev standardization
Dev practice
Dev velocity
DevOps Velocity
DevOps practice
DevOps Mastery
Scaled DevOps
DevOps explored

20. What is a DevOps Feedback Loop?
Ops
Ops Front Office Ops Back Office
System/Cloud
Management
(Machine)
Asset, System
or Service ID
Dev
Release or
Deploy ID
Improve Dev
Dev Project
or Product ID
Fast-fix
traceability
Versioned
/Managed
Code
Future
influence
Purge
forever
Improve Reuse
X
“M”
M2M
P2P
Tracking Total Cost, Time, Quality and Risk…creates future Dev modeling data
End User or
Business line
(Person)
“P”
Production, Cloud
or Data Center
(Machine)
“M”
Support/Service
Management
(Person)
“P”
P
M
P2M
M2P
P
M Project/Flow
Template ID
Recommend
Reuse
More data-driven
decision-making
DevOps!
“D”
Developer
System
“S”

21. CxO – Is this Enterprise Agility?
What is a DevOps Feedback Loop?
PMO – Is this Continuous Planning?
CTO/VPE – Is this Continuous Improvement?
Ops
Ops Front Office Ops Back Office
System/Cloud
Management
(Machine)
Asset, System
or Service ID
Dev
Release or
Deploy ID
Improve Dev
Dev Project
or Product ID
Fast-fix
traceability
Versioned
/Managed
Code
Future
influence
Purge
forever
Improve Reuse
X
“M”
M2M
P2P
Tracking Total Cost, Time, Quality and Risk…creates future Dev modeling data
End User or
Business line
(Person)
“P”
Production, Cloud
or Data Center
(Machine)
“M”
Support/Service
Management
(Person)
“P”
P
M
P2M
M2P
P
M Project/Flow
Template ID
Recommend
Reuse
More data-driven
decision-making
DevOps!
“D”
Developer
System
“S”

22. Going Agile?
Going DevOps?
Stay out of the painful Insanity Loops!
Get More Feedback Loops!