This document outlines the LeanOps transformation journey of an organization. It discusses setting up a LeanOps structure with area product owners, scrum masters, and a chief product owner to manage a global development backlog. Key aspects of the LeanOps approach covered include establishing 4-week cadences, using a Kanban board with swim lanes and WIP limits, implementing daily stand-ups and retrospectives, tracking various metrics, addressing initial challenges through eliminating waste and building quality in, and achieving improvements in areas like system availability, release duration, and customer satisfaction.
5. Product 2
Product 3
Product 1
Service 1
Service 2
FORWARD
ENGINEERING
SUSTENANCE
ENGINEERING
Production Engineering Team
Earlier Working Model
5
6. Vision
Dev’s goal is to
implement the
features/
changes
Ops goal is to
keep the site
stable and fast
C
O
N
F
U
S
I
O
N
Earlier Working Model (contd..)
6
7. Product 2
Product 3
Product 1
Service 2
Service 1
SLA
Production Engineering Team
Vision
DEV,
QA,
PEG,
BCM,
DAG,
INFRA
LeanOps Inception
7
10. 4 WEEKS CADENCECADENCE
PLANNING
Discuss the Important Area for the cadence
Set the goals for the Cadence
No SLA Violation for P01/P04
All approved CRs must be deployed within one Business day
CR cycle time should not be more than 3 days
Define/Refine WIP Limits
On-demand Backlog Grooming
CADENCE
CLOSURE
Goal Oriented Approach
10
20. Incidents created per week Incidents closed per week
CR Cycle Time Incident distribution by SLA
Metrics - Efficiency
20
21. 21
Metrics – Effectiveness, Quality & Others1
Average Effort (for incidents based on category)
% of On Time Delivery (met the SLA)
% of First Time Right
Value Add Time & Non Value Add Time
% System Availability
Customer Satisfaction
Inflow Vs Outflow of Incidents
Team Happiness Index
22. 22
Touch Time
Wait Time
Worst and Best Completion Time
Hand offs
Cumulative Flow Diagram
Mean Time To Repair
Mean Time Between Failure
# Changes per week (Trend)
Metrics – Effectiveness, Quality & Others2
24. System availability is more than 97%
Release duration is reduced from 2 months to 2 weeks
Reduced downtime from 8 hours to <2 hours
Improved quality
Reduced rework
Increased FTR
Enhanced Customer Satisfaction
Feature Teams
Achievements1
24