Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Kanban - a sane way towards DevOps
Transcript of Kanban - a sane way towards DevOps
So you spend most of the time
"The RIGHT thing" is a hard to nail moving target
"I'm losing sleep over whether we are actually doing the right thing in this big project and not wasting our time" IT Director in a major telco
So don't be surprised if people optimize accordingly
When do you celebrate/relax?
Complicating things is often faster in the short run
REALLY Agile Projects - Islands of Success
How? by shortening the feedback loop
by Dev&Ops working closely together
by reducing the batch size through all processes including Release/Deployment
Measure "Work in Process" Inventory and
Go on a "WIP Diet"
Slice work into valuable integrative testable chunks that can really flow to feedback fast
Why wait? Bring feedback to the front!
Feedback, Questions, Follow-up, Guidance...
Be Flexible Enough
Deliver lots of value
Harder and Harder to deliver
Visualize E2E work & Flow using Kanban boards
Manage and Improve Flow - Stop Starting Start Finishing
Break the waterfall - work in smaller batches
Implement reasonable fix for this speed
Leverage the Friction/Pain in order to improve
Tighten the loop
Sense/Identify what hurts
e.g. deploy too labor-intensive
Reduce Batch Size
e.g. automate part of deploy
Silos, Politics, Turf Wars
Heavy Build/Test/Deploy Processes
Networked File Systems
Security Penetration Testing
Distributed Robust Systems
Enterprise Coach, CTO, Partner
Developer / R&D Lead
Networking/Security Engineering Group Lead
Agile Testing Approaches
Lean Product Dev
TIP: Understand and Quantify the Cost of Delays/Queues/Large batches in order to justify investments/improvements
The Typical Agile development view - DONE==Working Tested Software
DevOps view - DONE=Works well and useful in production
First - Visualize
BUT don't stop here... the really good stuff is yet to come...
Kanban is about
Measure and optimize Flow
video of jumping control chart, CFD
I know my transaction and operation costs but have no clue about my "Holding Costs"...
Retrospectives - Sense & respond to flow/feedback problems
Reduce WIP / Accelerate delivery loop to surface next opportunities for improvement, collaborate in studying the system and designing/running experiments
Mix Gradual/Revolutionary change according to the context,
of work items
Start thinking of the IT as a "design factory" and apply flow principles
Use Smaller integrative valuable slices of work
Bring Ops feedback up front (Operations Driven Development)
Bring Biz + Dev + Test + Ops + X to work together all the way
Increase frequency of Delivery
You CAN have a cadence of Retrospectives when doing Kanban
(and probably Should!)
Measure Flow/Cycle Time and aim to reduce average and variability
Prefer Pull over Push
Can DevOps work with Component teams?
Stories-level Dev Team Kanban Board
FRESH coffee anyone?
Scaling Agile - SAFe/LeSS/Whatever...
Remember to think about:
How will we test this? (ATDD)
How will we deploy/operate it? (ODD - Ops Driven Development? )
How will we know we achieved our outcome? (Lean Startup)