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
Enterprise Product Development Kanban - LeanKit Webinar - April 2015
Transcript of Enterprise Product Development Kanban - LeanKit Webinar - April 2015
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!
ATDD/BDD and recently even ODD (Ops-Driven-Development)
Feedback, Questions, Follow-up, Guidance...
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
Enterprise Coach, CTO, Partner
Agile Testing Approaches
Lean Product Dev
The Typical Agile development view - DONE==Working Tested Software
DevOps view - DONE=Works well and useful in production
First - Visualize
Kanban is about
Measure and optimize Flow
video of jumping control chart, CFD
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,
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
Can Kanban work with the current organizational Silos?
Stories-level Dev Team Kanban Board
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)
of work items
Stories Board (With stories of current feature highlighted)
Stories Board (Seeing just the stories of current feature -
The main challenge?
"Too many chefs in the MMF kitchen"
What do you think about this Cumulative Flow Diagram (Ct FD) ? Are they doing well?
How about now, with just work in process states visualized?
This is CFD based on card size on the stories board for a ~90 people group working in around 8-10 teams typically
Let's look at the same group, now counting # of cards (stories in this case). WDYT now?
We also have an MMF board CFD...
Do you see any difference?
Are we on track to deliver the release?
So, What kind of product development organizations are doing this?
Leading global Customer Experience vendor delivering projects to majority of world-class TelCos
leading global provider of product lifecycle management (PLM) and manufacturing operations management (MOM) software
world-leader in privileged access management (cyber-security) protecting 1200 global businesses
leading provider of financial technology to banks and corporations of all sizes all around the world
Market leader in financial Crime, Risk and Compliance management
Leading Interactive Online video Advertising Vendor
Data integration leader for big data & cloud
(And these are Just the ones we helped...)
world’s #1 wireless backhaul solutions specialist