KanBan and DevOps DO or DIE

“The contents in this presentation is prepared by Rajeev Batra in his / her personal capacity and to the best of his / her 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 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.”

About Rajeev is from Bangalore and heads Agile Practice at

OGS (Optum Global Solutions)

He is a techno manager and agile evangelist . He has

more than 10+ years experience with agile projects and

has led large scale agile transformation initiatives.

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

Flow aka KanBan Lets define Kanban and why do we adopt it

3

min

DevOps

?

DevOps DevOps is the combination of cultural philosophies,

practices, and tools that increases an organization’s ability to

deliver applications and services at high velocity : evolving

and improving products at a faster pace…….

By now you must be thinking Is this session about

how DevOps team should adopt Kanban ??

Or

how Kanban team should adopt DevOps??

Source - 2017-state-of-devops-report

So how does DevOps fit in? 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

Challenge Can you be 100% sure about

merging on the main without a

accident ?

Your

commit

Some commit after your

pull

Oh! ,

But that’s

not my

code

Challenge

To-Do Doing

Done Deploy Dev Test

Revisit(ed)

To-Do Doing

Deploy Done Dev Test

So we are talking about DevOps is a 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.

Is it possible in your world ?

Culture

Build it in

from the

Start !

Image Credit - By eastkandar (starting grid.) [CC BY 2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons

Ops

Dev

PO/BA

QA

Automaton

Smart

Infrastructure

CI - CD

Architecture

And

Replenishment

Cadence

Daily stand-

ups at the

KanBan board

Measure and

learn

Enable Continuous delivery for “Business

Agility”

Alignment across all stakeholders

Faster Value

Contact : Rajeev Batra ““The contents in this presentation is prepared by Rajeev Batra in his / her personal capacity and to the best of his / her 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 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.”

Question ? Since Scrum has been quite mainstream now, a question we

should all be asking is how does the shift from Scrum to

Kanban effect DevOps efforts?

Thank you

““The contents in this presentation is prepared by Rajeev Batra in his / her personal capacity and to the best of his / her 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 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.”

References https://www.upguard.com/blog/devops-kanban-match-heaven

https://devops.com/kanban-vs-scrum/

https://www.atlassian.com/continuous-delivery/is-your-team-

ready-for-devops

2017-state-of-devops-report

https://aws.amazon.com

Image credits to various original owners