LKNL12: Kanban for the whole value stream
Upcoming SlideShare
Loading in...5
×
 

LKNL12: Kanban for the whole value stream

on

  • 560 views

You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, ...

You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, Marketing, Support all have a different language and a different view into the value stream. How can we start an organizational change without a shared model of how the company should be organized?

Those are all symptoms of a gap in our Agile community: we lack a organizational model for company-wide Agile adoption and company-wide continuous improvement. Examples of this include: no company-wide flow-model (kanban) from idea to sales to idea and so on; we have no way to evaluate where the bottlenecks are the moment they are not in “our silo”. We lack a theoretical model for designing software organizations.

A theory is something that informs day-to-day decisions and experiments (e.g. PDCA). In this talk we will explain an
organizational design concept developed over several years, and use concrete examples to describe a model that you can use in support of - not only your agile adoption - but your company improvement process and your new organizational design.

Statistics

Views

Total Views
560
Views on SlideShare
538
Embed Views
22

Actions

Likes
2
Downloads
8
Comments
0

2 Embeds 22

http://www.leankanban.nl 18
https://twitter.com 4

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    LKNL12: Kanban for the whole value stream LKNL12: Kanban for the whole value stream Presentation Transcript

    • @duarte_vasco and @lassezieglerVisualize the work – Kanbanfor the whole value stream
    • Tambako @ flickr
    • V-ModelSpiral MOdelRapid Software Development Chaotic developmentDSDM• Add buzzwords of failed modelsRational Unified ProcessFDD Danisarda @ flickr
    • Ericcastro @ flickr
    • Ken Schwaber: 75% of organizations fail to benefit from Agile/Scrum as expectedhttp://www.agilecollab.com/interview-with-ken-schwaber
    • Cayusa @ flickr
    • Would you go back to the old way of working? Large hardware + software company in nordics
    • NSN, presentation at JAOO/2010
    • Matley0 @ flickr
    • Act II – developing the action
    • Louish @ flickr
    • What is the biggest problem in your organization?
    • Zenera @ flickr
    • • Overburdden or Muri Topgold @ flickr
    • Skuds @ flickr
    • It is hard There’s a and slow to bottleneck hire good in R&D Hire more people Salaries people here are too high! Need to And then we get fasterspend time Travel and wait... R&D!!! Oh Work with with off- communication off-shore shore costs increase and near- teams shore Communication problems emerge
    • MarketMarket Here be You are here Here be dragons dragons (R&D / IT)
    • 1. Why do we have so many features in the backlog?2. What are the value stream steps that we don’t know about yet? Or don’t even understand?
    • Market Market Here be You are here Here be dragons dragons (R&D / IT) Pre- Revenueidea experiment valid To do Doing Done prodcution Production generated
    • MarketMarket Here be You are here Here be dragons dragons (R&D / IT)
    • Features left to complete Likely progress at current pace Likely release date some where there... Time Release date ...
    • Company acquired Lack of scrutiny by Product Need to add Manager or more features other <exercise forthe audience> All new Increase features are pressure on added teams
    • Make information about the system visibile ... And that’s just the start...
    • End ofFeatures in the Backlog Roadmap cycle End of End of strategy strategy cycle cycle Time
    • Stay tuned for an example...
    • Jduty @ flickr
    • <PDCA Concentric circles> Papalars @ flickr
    • Gertcha @ flickr
    • Example 1: Why do we have so little througput?
    • Stuff that is going on
    • Development Stuff inStuff that is production going on
    • Where are all these projects coming from?
    • Development Stuff inStuff that is production going on
    • Project evaluation Development Stuff inStuff that is production going on
    • Wish Project ProductionList evaluation Life-cycle Development Stuff in production
    • Wish Project ProductionList evaluation Life-cycle Development Production Stuff in production Live Maintenance
    • Example 2: The Feature Team
    • Component A Component BQueue Development Testing Development Testing
    • Component A Component BQueue Development Testing Development Testing
    • Feature Team (A + B)Queue Development Testing
    • Feature Team (A + B)Queue Development Testing Post-production Localization Documentation
    • Example 3: What happens on theProduct Management part of the chain?
    • Feature Team (A + B)Queue Development Testing Post-production Localization Documentation
    • This *was* the queue! MVP Validated Development Filtering ideas The CTO pool/ IntegrationAcquisition Customer Requests
    • Example 5: Why do we get such a big queue at specific intervals?
    • Queue Development Testing
    • Roadmap Process Output Development TestingHappens in Spring and Autumn
    • Strategy Roadmap Process Process Output Development TestingHappens in Spring and is ”reviewed” in Autumn
    • One more thing...
    • Newfrontiersmedia @ flickr
    • Act III – Turning point
    • Bazzadarambler @ flickr
    • Normanbleventhalmapcenter @ flickr
    • Zeptonn @ flickr