Kanban India 2022 www.kanbanindia.org

1. “The contents in this presentation is prepared by Raman Sidhu in his personal capacity and to the best of his knowledge. No liability whatsoever
for the accuracy and completeness of the above information is howsoever assumed. The opinions/ contents expressed/ provided in this article
are the author's own and do not reflect the views of the Optum (“company”). Neither company nor the author shall not be held liable for any
improper or incorrect use of the information described and/or contained herein and assumes no responsibility for anyone's use of the
information.”

2. Internal
• Rajeev is from Bangalore and is Head of
Product Engineering - System Solution Digital
and Site Leader Bangalore, ZF Group
• He is a techno leader and agile evangelist.
• He has more than 15+ years experience with
agile projects and has led enterprise scale
agile transformations.
• Rajeev is married to Swati and has a son
Dhrishit and daughter Kashvi
• In his free time, Rajeev loves to read about
business strategies and technology, likes to
travel and binge watch movies.

3. Internal
What to
expect
(Agenda)
 Define Connected Automotive wolrd
 Define Flow / Kanban
 The (secret ) sauce of success and myths
 Walk the talk – Case studies
 How to harvest the benefits

4. Internal

5. Internal
 Put for SCALAR ??? A video
 https://www.youtube.com/watch?v=HPHm8CWdR8Y

6. Internal
 Lets define DevOps and why do we adopt it
Or click on QR code
slido.com with #S192
to
share
your
responses
3
min

7. Internal
 Lets define Kanban and why do we adopt it

8. Internal

9. Internal
 Is this session about
 Connected Automotive World
Or
 how DevOps team should adopt Kanban ??
Or
 how Kanban team should adopt DevOps??
Source - 2017-state-of-devops-report

10. Connected Automotive World ??
Or
how DevOps team should adopt Kanban ??
Or
how Kanban team should adopt DevOps??
ⓘ Start presenting to display the poll results on this slide.

11. Internal
 As teams embrace Kanban with the want to complete work and deliver functionality
continuously, businesses and team want it be available for customers at the earliest
and thus it should also be deployed continuously , i.e. as it get ready!
This is what makes it a natural fit 

12. Internal

13. Internal

14. Internal
 Can you be 100% sure about merging on
the main without a accident ?
Your
commit
Some commit after your
pull
Source - State of DevOps 2022

15. Internal

16. Internal
Challenge 2

17. Internal

18. Internal
Source - State of DevOps 2022

19. Internal

20. Internal
 Incorporation of DevOps cultural attributes into the
development mindset which when married to Kanban unifies
these two (Dev and Ops) at a cultural level to help organization
achieve accelerated realization of value for customer.
Challenge 3
How to make it possible in your organization

21. Internal
DevOps (Modern)

24. Internal
Study 1
 Before Adoption
 Team(s) operated only in the inner loop (aka the
classical way) and used to claim the functionality is
“Done” once the work for implementation is done
 Post DevOps Adoption
 Moved to Factory model where we had 2 loops
 Pipeline were introduced to enable CI and was the
only way to move code to higher environments with
automated checks in place .
 Segregation between Deploy and Release was
established
 Automated Test harness Sanity and Smoke test suits
were incorporated into the pipeline along with SAST.
 Testing == bench and field testing
 Release was only done post all levels of test and
based once metrics and field data were found to be
good.
 Measure
 Increase in throughput by ~15%
 Reduced Lead time by ~21%
 Quality ~ 10 %

25. Internal
Study 2  WIP

26. Internal
 Isn’t Kanban Just a Board?
 DevOps only works with SCRUM
 Kanban only works in small support
teams.
 You have to overboard WIP to go
faster
 Each stage cant be a loop in itself

27. Internal

29. Thank You!

30. Internal