Kanban India 2023 www.kanbanindia.org

1. Information Classification − Public
Date & Time :
2nd Dec 2023
KanBan India 2023
Continuous Improvement
aligned to Business Value
Streams
Mohit Anand

2. Information Classification − Public
www.kanbanindia.org
So why are we here?
To have a discussion giving everyone the chance to understand:
2
Common
Gaps
Success
Model

3. Information Classification − Public
www.kanbanindia.org
Common Gaps
Pre – Requisite to lead us to required success model
3
What Why How
Business
value
streams

4. Information Classification − Public
www.kanbanindia.org
Purpose of Business Value Stream
4
Value
Idea Value Stream

5. Information Classification − Public www.kanbanindia.org
Common Challenges?
What?
 Improvement not
appreciated by Business
 Difference in definition of
improvement
 No consistent way of
reporting improvement
Why?
 Lack of clarity on alignment to
Business OKRs
 Lack of clarity on prioritization
 Lack of transparency of progress
 Lack of understanding of
dependencies to align time/effort
from teams
 Lack of understanding of measures
 Lack of tools to report/measure
improvement

6. Information Classification − Public www.kanbanindia.org
Adopt KanBan to cater challenges
Challenges
Lack of clarity on alignment to
Business OKRs
Lack of clarity on prioritization
Lack of transparency of progress
Lack of understanding of
dependencies to align time/effort
from teams
Lack of understanding of
measures
Lack of tools to report/measure
improvement
Resolution Steps
Align Engineering/Tech OKRs to
Business OKRs
Prioritize Backlog aligned to OKRs
Limit Work in progress
Allow Work to be visualized
Organize and Visualize the Work
Understand and Visualize
dependencies
Measures to focus on Flow
Continuous improvement around flow
Organize the people around Work

7. Information Classification − Public www.kanbanindia.org
Establish alignment
Business OKRs -> Tech OKRs
7
Business outcomes Tech Outcomes
Business objectives Tech objectives
Tech KRs
Business KRs

8. Information Classification − Public www.kanbanindia.org
Business OKRs ->Tech OKRs
(Example)
8

9. Information Classification − Public www.kanbanindia.org
Establish Transparency
Portfolio -> Program
9

10. Information Classification − Public www.kanbanindia.org
Organize and Visualize the work
10

11. Information Classification − Public www.kanbanindia.org
Measures to Focus of Flow
 Portfolio -> Epic Lead Times, Epic cycle Times
 Program -> Feature Lead Time, Feature Cycle
Time
 Team -> User story lead Time, User story Cycle
Time, Lead time for Change
11

12. Information Classification − Public
www.kanbanindia.org
Continuous Improvement – Best Practice
Automated Extraction of measures
12
Domain
Feature Team
ART
 Hierarchy to report metric drill down and roll-up view
 Metrics menu card - Configure and measure
against agreed Goals and baselines
 Provides variety of Visualisations
Franchise
 Other Features
 Automated and configurable Customer Satisfaction
Survey
 Automated and customisable Team Engagement
Survey
 Automated Commentary to Trends

13. Information Classification − Public
www.kanbanindia.org
Continuous Improvement Implementation contd..
Metrics Snapshot
13
Program Execution Efficiency - ART Throughput - Team
Engineering capability - Team
Stability - Platform

14. Information Classification − Public
www.kanbanindia.org
Continuous Improvement
( 9 Step Success Model)
14
4. Proposed Measures against
Growth Plan
5. Agree Measures / metrics
6. Extract metric data from trusted
sources
7. Proposed Baselines based on
historical data
8. Agree Goals with OKRs
Monthly /
Agreed Cadence
Collect Report & Analyse
Identify area of focus
Plan/
Prioritise
Implement
9. Report and Analyse Metrics to improve
1. Perform Engineering maturity and/or DevOps maturity Assessment
2. Agree OKRs for each Engineering Maturity dimension
3. Prioritise DevOps/ Engineering capability dimension to prepare Growth plan to improve
aligned to Business goals/OKRs

15. Information Classification − Public
www.kanbanindia.org
Business Benefit
(Example from a platform that adopted the model)
15
KPI progress reported on agreed KRs

16. Information Classification − Public
www.kanbanindia.org
Conclusion
16
Adoption of Kanban Challenge catered
Change in Business
Mindset
Alignment between Business
OKRs and Tech OKRs
Lack of clarity on alignment to
Business OKRs
Business appreciating the
impact of Tech OKRs
Transparency across Work
Taxonomy / Limit the Work in
progress
Lack of clarity on
prioritization/progress
Reduce friction in
prioritization/ delivery
Visualize the dependency and
Bottlenecks
Lack of understanding of
dependencies to align
time/effort from teams
Better agreement on
incremental value and
manage risks
Measure to focus on flow of
Work
Lack of understanding of
measures
Business partnering in
agreeing measures and
associated baselines, goals
Report continuous
Improvement of flow
Clarity of meeting definition on
success/acceptable
improvement
Improvement appreciated
by Business

17. Information Classification − Public
Thank you