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.
Starting with Managers Kanban - DARE13
Transcript of Starting with Managers Kanban - DARE13
Seeded Product Streams
Self-grown Product Streams
An Approach to Sustainable and Sticky Agile Journeys
This is a temporary change management pattern
Use it to test applicability of Kanban as well as seed the right kind of thinking ...
Idea to consider: Don't even talk too much about Improvement frameworks and models up front. Even organizations that will end up Continuously Improving are not receptive to the ideas when starting
Make current policies explicit
Implement Feedback Mechanisms
Leadership - Give permission and Encourage Process Innovation from any and all team members, Managers first
Job = Work + Improvement, Especially when you are a manager
Applies to Scrum as well???
First bring flow under control
Only then start talking about approach to process improvement
Challenging your comfort zone
Catalyzing improvement in technology delivery organizations in Israel and Worldwide
Is it possible that over-emphasis on change management and the "Continuous Improvement" phase is a "turn-off" for people at the beginning of their agile journey?
Presentation & Resources at:
Key Takeaways about the Pattern
When to use
When to STOP using
Fast Learning/Training of MANAGERS about Flow
Fast learning whether Managers can lead flow
Ease into Kanban
The specific boards are just for illustration...
Although they represent an emerging good practice for similar groups
Change Management Approach
change towards lean/agile by
Kanban with managers
Improve execution agility and scalability by
in cross-silo Kanban
OPTION: Considering the shape of the demand - consider creating stable Kanban value streams (and cross-functional teams)
(Notice management communication overhead goes down)
Be Agile @
Seriously good guidance!
Focus on Teams
Fake Agile - Silo Teams
Pilot Approach - Managers Outside
How change is sparked in books...
Hypothesis: Lean/Agile can help here...
What is the riskiest assumption / leap of faith in going lean/agile here?
Middle and Line Managers will understand, support, drive
Flow will work here
We will allocate capacity to improvement
We are able to stop starting start finishing, can say no sometimes, can shape demand
We can work with MMFs/MVPs to achieve early value/learning
Management Team Work
Portfolio and Features Flow
What value streams to manage?
Make room for improvement demand
Learn the ropes of Kanban
Validate the leaps of faith
Feature level Flow
How can we reflect level of involvement in Kanban Depth?
Kanban Breadth? Reach?
Build Management Understanding
and drive for flow
the whole group's ability
to manage and improve flow
This is Proxy/Representative Kanban
Work is pulled ON BEHALF of engineers by their managers
Minimum Viable Test of Change -
MANAGERs think and act
"Stop Starting start Finishing"
What "Representative Product Stream Kanban" Looks like day to day
Flow meetings 3 times a week
Discovery sessions to pull Features->MMFs and review User Stories
Mainly TLs and above attend
"kind of" Kanban Agenda Meeting (Don't tell them... ;-)
Starting Kanban – Managers First!
How I'm using kanban to spark enterprise level change
OPTION: Extend Kanban Method to cover more of the value stream
Q: How will THIS show up on a Kanban Depth chart?
What j-curve matches which pattern?
change towards lean/agile by
into Kanban with managers first
Visualize, Manage, Limit & Improve
more granular flow
(e.g. Stories not just Features)
Where the F%$K is my gantt chart??? How do I know if I'm on track?
But how do we manage until we gather data?
CFDs. Cycle Time Charts.
And most importantly reinforce fact that WIP Diet is key to earlier visibility!
Acknowledge the S-Curve
Value Stream Progress as proxy to "Working Tested Software"
Monitoring Several Queues
Use for Feedback, Questions, Ideas...
Pecha Kucha Go!
Another pass, now let me know what interests you more
Lets think how to apply this to a 1-2 of your scenarios
Lean/Kanban Brickell Key Award Winner 2013
Beyond one team?
Virtual feature teams that change often?
virtual but stable feature teams (e.g. Scrum)?
Organization structured around feature teams?
Use DARE13 50% coupon
Enterprise Lean/Agile Coach @
When is it best to
Happier more empowered people
Better chance at the RIGHT time