LKNL12: Kanban for the whole value stream

757 views

Published on

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.

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
757
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
11
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

LKNL12: Kanban for the whole value stream

  1. 1. @duarte_vasco and @lassezieglerVisualize the work – Kanbanfor the whole value stream
  2. 2. Tambako @ flickr
  3. 3. V-ModelSpiral MOdelRapid Software Development Chaotic developmentDSDM• Add buzzwords of failed modelsRational Unified ProcessFDD Danisarda @ flickr
  4. 4. Ericcastro @ flickr
  5. 5. Ken Schwaber: 75% of organizations fail to benefit from Agile/Scrum as expectedhttp://www.agilecollab.com/interview-with-ken-schwaber
  6. 6. Cayusa @ flickr
  7. 7. Would you go back to the old way of working? Large hardware + software company in nordics
  8. 8. NSN, presentation at JAOO/2010
  9. 9. Matley0 @ flickr
  10. 10. Act II – developing the action
  11. 11. Louish @ flickr
  12. 12. What is the biggest problem in your organization?
  13. 13. Zenera @ flickr
  14. 14. • Overburdden or Muri Topgold @ flickr
  15. 15. Skuds @ flickr
  16. 16. 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
  17. 17. MarketMarket Here be You are here Here be dragons dragons (R&D / IT)
  18. 18. 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?
  19. 19. 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
  20. 20. MarketMarket Here be You are here Here be dragons dragons (R&D / IT)
  21. 21. Features left to complete Likely progress at current pace Likely release date some where there... Time Release date ...
  22. 22. 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
  23. 23. Make information about the system visibile ... And that’s just the start...
  24. 24. End ofFeatures in the Backlog Roadmap cycle End of End of strategy strategy cycle cycle Time
  25. 25. Stay tuned for an example...
  26. 26. Jduty @ flickr
  27. 27. <PDCA Concentric circles> Papalars @ flickr
  28. 28. Gertcha @ flickr
  29. 29. Example 1: Why do we have so little througput?
  30. 30. Stuff that is going on
  31. 31. Development Stuff inStuff that is production going on
  32. 32. Where are all these projects coming from?
  33. 33. Development Stuff inStuff that is production going on
  34. 34. Project evaluation Development Stuff inStuff that is production going on
  35. 35. Wish Project ProductionList evaluation Life-cycle Development Stuff in production
  36. 36. Wish Project ProductionList evaluation Life-cycle Development Production Stuff in production Live Maintenance
  37. 37. Example 2: The Feature Team
  38. 38. Component A Component BQueue Development Testing Development Testing
  39. 39. Component A Component BQueue Development Testing Development Testing
  40. 40. Feature Team (A + B)Queue Development Testing
  41. 41. Feature Team (A + B)Queue Development Testing Post-production Localization Documentation
  42. 42. Example 3: What happens on theProduct Management part of the chain?
  43. 43. Feature Team (A + B)Queue Development Testing Post-production Localization Documentation
  44. 44. This *was* the queue! MVP Validated Development Filtering ideas The CTO pool/ IntegrationAcquisition Customer Requests
  45. 45. Example 5: Why do we get such a big queue at specific intervals?
  46. 46. Queue Development Testing
  47. 47. Roadmap Process Output Development TestingHappens in Spring and Autumn
  48. 48. Strategy Roadmap Process Process Output Development TestingHappens in Spring and is ”reviewed” in Autumn
  49. 49. One more thing...
  50. 50. Newfrontiersmedia @ flickr
  51. 51. Act III – Turning point
  52. 52. Bazzadarambler @ flickr
  53. 53. Normanbleventhalmapcenter @ flickr
  54. 54. Zeptonn @ flickr

×