Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Kanban - a sane way towards DevOps

Talk for Velocity Barcelona 2014 + Agile India 2015
by

Yuval Yeret

on 27 March 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Kanban - a sane way towards DevOps

The IT Challenge
So you spend most of the time
FIGHTING
fires
"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
http://design4services.com/concepts/failure-demand/
So don't be surprised if people optimize accordingly
When do you celebrate/relax?
Handoff
or actual
finish line
?
Complicating things is often faster in the short run
The Expectations
Familiar?
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!
Ops-Driven-Development

Biz
Dev
Test
Ops

http://www.AgileSparks.com
yuval@agilesparks.com
Feedback, Questions, Follow-up, Guidance...
Be Flexible Enough
Minimize disappointment/surprises
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
Legacy Architecture
Heavy Build/Test/Deploy Processes
Wrong KPIs/Incentives
Biz
Dev
Test
Ops
Thank you!
Linux Kernel
Clustering Systems
Networked File Systems
C
Bash
Routers
CCIE
VMWare
Windows Networks
Netware
Network Design
TCP/IP
Agile
Modern Management
Scrum
Kanban
ScrumBan
Security Penetration Testing
Distributed Robust Systems
Open Source
Volleyball
Player
Wife+9+6
Agile
Sparks
Enterprise Coach, CTO, Partner
Developer / R&D Lead
Networking/Security Engineering Group Lead
Agile Testing Approaches
Lean Product Dev
Lean Change
https://www.linkedin.com/in/yuvalyeret
Operating Systems
Flow
http://blackswanfarming.com/cost-of-delay/
Joshua Arnold
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...
THIS IS
HARD
Kanban is about
Facing the
Pain
&
DOING
something
about it
Measure and optimize Flow
video of jumping control chart, CFD
CD
<--DevOps
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,
Limit #
AND SIZE
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
http://www.slideshare.net/yyeret/effective-agile-retrospectives
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
Epic/Feature level/Program
Kanban Board
http://www.wunderground.com/wximage/nanapoo/432
FRESH coffee anyone?
Find your
constraint/bottleneck/big batch

and
focus
on it
s
Scaling Agile - SAFe/LeSS/Whatever...
Lean Startup
http://www.javabeat.net/the-most-popular-collaborative-models/
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)
Ops?
[Net|Sec|Perl|DB]Ops?
Always?
The
3
+X
Amigos Approach
p
Full transcript