How to achieve 'Flow' in your delivery pipeline. This was an 'Ignite' session at DevOpsDaysDC 2018. Ignite sessions are 5 minutes long with 20 slides auto-advancing every 15 seconds.

1. The Muda, Mura and Muri of DevOps
‘Flow’ in DevOps
Sanjeev Sharma
IBM Distinguished Engineer
@sd_architect | sdarchitect.blog

2. 2Page© 2016 IBM Corporation
#WhoAmI
• 20+ Years in Software
Development and Delivery
• IBM Distinguished Engineer and
CTO for DevOps Adoption
• Author of two DevOps books:
• DevOps For Dummies:
https://ibm.biz/BdsPMX
• The DevOps Adoption Playbook:
http://amzn.to/2hH7rt2
• Blog: https://sdarchitect.blog
• @sd_architect

3. 3Page© 2016 IBM Corporation
Goal: Achieve Flow in your Delivery Pipeline
Product Owner
Senior Executives
Developer Domain ExpertsAuditors
QA Support Staff
External Vendor
Operations Staff
Enterprise
Architect
PMO Lead
ApproverProject Manager
Line-of-business Customer
IT
Agility - Velocity – Innovation – Cost - Quality
App Development, Orchestration, Integration, Security, Management, Governance

4. 4Page© 2016 IBM Corporation
Flow is a two-way street
Line-of-business Customer
IT
Agility - Velocity – Innovation – Cost - Quality
Continuous Feedback results in Continuous Improvement
or Kaizen
1. Improve the Deliverable
2. Improve the Environment
3. Improve the Process

5. 5Page© 2016 IBM Corporation
Kaizen
Continuous Improvement

6. 6Page© 2016 IBM Corporation
Muda
Waste
https://theleanway.net/muda-mura-muri

7. 7Page© 2016 IBM Corporation
Mura
Unevenness
https://theleanway.net/muda-mura-muri

8. 8Page© 2016 IBM Corporation
Muri
Overburden
https://theleanway.net/muda-mura-muri

9. 9Page© 2016 IBM Corporation
Mapping your Delivery Pipeline
Idea/Feature/Bug Fix/
Enhancement
Production
Development Build QA SIT UAT Prod
PMO
Requirements/
Analyst
Developer
CustomersLine of Business
Build
Engineer
QA Team Integration Tester User/Tester Operations
Artifact Repository
Deployment Engineer
Release Management
Code Repository
Deploy
Get Feedback
Infrastructure as Code/
Cloud Patterns
Feedback
Customer or
Customer Surrogate
Metrics - Reporting/Dashboarding
Tasks
Artifacts

10. 10Page© 2016 IBM Corporation
1
Identifying the Root Causes of Muda, Mura and Muri

11. 11Page© 2016 IBM Corporation
Delivering a Business Capability – Hybrid Applications, Hybrid
Platforms, Hybrid Teams
Application A
Application B
Application C
Application N
BusinessCapability
…

12. 12Page© 2016 IBM Corporation
Delivering a Business Capability – Hybrid Applications, Hybrid
Platforms, Hybrid Teams
Application A
Application B
Application C
Application N
BusinessCapability
…
Deployment
Automation and
Orchestration
Service and Test
Environment
Virtualization
ArchitecturePlanning
Release
Management
Operational
Readiness

13. 13Page© 2016 IBM Corporation
Your Delivery Pipeline
will be as fast as the
slowest Delivery
Pipeline it is
dependent on
Planning
Mura

14. 14Page© 2016 IBM Corporation
Modernizing to
Microservices based
Architecture to
reduce Batch Size
Architecture
Mura

15. 15Page© 2016 IBM Corporation
Developers are paid
to write code, not
maintain deployment
and configuration
scripts
Application Deployment and Environment
Orchestration
Muda and Muri

16. 16Page© 2016 IBM Corporation
If you are doing 2-
week Sprints, but it
takes 3-weeks to
get a Test
Environment, how
long are your
Sprints?
Test Service and Environment Virtualization
Mura

17. 17Page© 2016 IBM Corporation
It is not possible to
patch the software of
a missile AFTER it
has been launched
Release Management
Muda, Mura and Muri

18. 18Page© 2016 IBM Corporation
Shift thinking from
Mean Time Between
Failure (MTBF) to
Mean Time To
Repair (MTTR).
Operational Readiness (for SRE)
Mura and Muri

19. 19Page© 2016 IBM Corporation
Organizational Change
• Squad-Tribe-Guild Team Model
• Visibility Across functional Silos
• “Everyone is responsible for
Delivering to Production”

20. 20Page© 2016 IBM Corporation
“Everyone is
responsible for
delivering Business
Value”