The Secret of Flow - My AgileIL11 Talk
•Download as PPTX, PDF•
3 likes•2,434 views
Journey towards better software development management using lean/kanban flow approaches - especially focused on service delivery in software sustainment. Trying to provide a somewhat fresh view of how to get to kanban thinking, but based on the current recipes (e.g. David Anderson recipe for success)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Secret of Flow - My AgileIL11 Talk
Similar to The Secret of Flow - My AgileIL11 Talk (20)
More from Yuval Yeret
More from Yuval Yeret (20)
Recently uploaded
Recently uploaded (20)
The Secret of Flow - My AgileIL11 Talk
- 1. The Secret of Flow http://www.flickr.com/photos/yuvalyeret/265568342/in/set-72157594323037021/ The journey towards better software development management using lean/kanban flow approaches Yuval Yeret
- 3. Application maintenance teams are an increasingly important contributor to service delivery and user satisfaction, but they are also a growing component of the IT budget. CIOs will find that paying attention to application maintenance teams delivers good rewards throughlower costs and targeted results Gartner, August 2010 Maintenance == Over 90% of lifetime costs http://users.jyu.fi/~koskinen/smcosts.htm
- 4. Most of maintenance work is managed as projectswe are USED TO manage Projects
- 5. Is there an alternative?
- 7. Enter FLOW based development also called Service Delivery
- 9. Step #1: identify and work with minimally valuable features
- 10. TIP #1: LimitSIZE!
- 11. Can all work items be the same size?
- 12. Step #2: Visualize Flow
- 13. Step #2: Visualize Flow
- 14. Tool: The Cumulative Flow Diagram
- 15. Mushon Inbar Inbar Elad Mushon Elad Inbar Elad Mushon How to do a CFD 15
- 16. How to do a CFD 16
- 17. What can teams learn from Cumulative Flow? Total Scope Dev Burnup Work in Process (WIP) Done Burnup Real Done Burnup 17 Average Cycle Time
- 18. A B Which is BETTER?
- 19. A B Manage FLOW to get from A to B
- 20. Question: What are those Steps?
- 21. quick roundtimefor short trips – no waits More efficient But longer time and queues TIP: Do what MAKeseconomic sense
- 22. A Kanban board – Not a Must for Flow But will SIGNIFICANTLY improve it
- 23. Time to Complete Smaller Features - is this Pull/Flow? Parallel - WIP R D C T R D C T R D C T R D C T DONE R D C T R D C T Time Moving to smaller units of work is NOTenough
- 24. Step #3: Control Flow RECIPE: Limit amount of Work in Progress
- 25. DONE R D C T R D C T R D C T R D C T R D C T R D C T DONE R D C T R D C T Requirements Design Code Testing DONE R D C T Time R D C T Requirements Design Code Testing R D C T Requirements Design Code Testing R D C T Time Requirements Design Code Testing Requirements Design Code Testing RECIPE: Limit WIP When PLANNING Requirements Design Code Testing Time
- 26. Collective ownership TIP: Versatility enables lower Work in process limits and minimizes price of surprises
- 27. RECIPE: Limit WIP When EXECUTING
- 28. Limiting WIP – pull according to the bottleneck DONE R D C Hardening R D C T R D C T R D C T R D C T R D C T Time
- 29. Say NO! to BAD project-level Multi-Tasking Tip: Freeze 50% of projects/activities Focus/Swarm on the remaining ones
- 30. Accurate WIP Limit / Freeze amount is not that important... ½ the WIP, ½ the batch size, can be a good start... Based on ReinertsenProduct Development Flow
- 31. limiting WIP / freezing SLACKTIME ??? * No coaches were idle due to the preparation of this presentation
- 32. RECIPE: use TOC 5 Focusing Steps
- 33. Feature Freeze Coding Done DONE Hardening R D C T R D C T R D C T R D C T R D C T R D C T
- 34. 3 1 5 Work with minimally valuable features Limit Work in progress Focus on bottlenecks 4 2 Visualize flow using CFD Improve versatility
- 36. Traditional priorities might not be enough Start thinking about COST OF DELAY Mike Burrows http://positiveincline.com/?p=769
- 37. Track cycle time per class of service to manage SLAs If I need a green one – how early should I schedule it for work?
- 38. Now lets complicate life a little...
- 39. Enter the Shared Resource...Test lab?
- 40. The Shared Experts DBA Platform/INFRA UX/UI DESIGN Security
- 41. Will visualizing and managing flow in each of those roads be enough?
- 42. Need to visualize and manage the global end to end flow across shared resources
- 43. When dealing with shared resources... we need to apply the flow techniques at the level at which they are shared
- 45. 3 Use Kanban boards to Visualize and manage end to end flow
- 46. How can I take this to my context?
- 47. Add flow charts to your existing work tracking system Something like... HP QualityCenter Microsoft TFS IBM Lotus Notes JIRA Excel...
- 49. Why FLOW Tuned for Service Delivery (80% of software development in the world is V>1.0) Pragmatic approach to change focused
- 50. 4 1 6 Limit Work in progress Focus on bottlenecks Work with minimally valuable features 7 5 2 8 3 Classify by COST OF DELAY Visualize flow using CFD Improve versatility Scale to shared resources Use Kanban Boards
- 52. COLLAGE FROM KANBAN TRAINING Advanced Topics in Kanban Kanban for Managers/Leaders Kanban for Scrummers Kanban Primer Kanban for IT/SUPPORT Operations JOIN A KANBAN WORKSHOP
- 53. Limitwork in process: Stopstarting, startfinishing 53
- 54. 4 1 6 yuval@agilesparks.com Get the slides at http://www.slideshare.net/yyeret @yuvalyeret http://yuvalyeret.com Limit Work in progress Focus on bottlenecks Work with minimally valuable features Questions? 7 5 2 8 3 Classify by COST OF DELAY Visualize flow using CFD Improve versatility Scale to shared resource Use Kanban Boards
- 55. Images Attribution http://www.flickr.com/photos/yuvalyeret/265568342/in/set-72157594323037021/ www.slideshare.net/wnazzaro/agile-it-and-the-business-community http://www.freefoto.com/images/41/03/41_03_4---Weight-Limit-Sign_web.jpg?&k=Weight+Limit+Sign http://www.flickr.com/photos/maisonbisson/267746261/sizes/o/in/photostream/ http://www.flickr.com/photos/malavoda/4195215934/sizes/l/in/photostream/ http://www.flickr.com/photos/njj4/5044361592/sizes/l/in/photostream/ http://www.flickr.com/photos/grafixer/3527166081/sizes/l/in/photostream/ http://www.flickr.com/photos/librarygoblin/4307610546/lightbox/ http://www.flickr.com/photos/orinrobertjohn/2188280583/sizes/l/in/photostream/ http://www.flickr.com/photos/kwl/4809326028/ http://www.flickr.com/photos/justin_case/54087334/sizes/o/in/photostream/ http://www.flickr.com/photos/noneck/869906174/sizes/l/in/photostream/ http://www.flickr.com/photos/wendycopley/1332359314/ http://www.flickr.com/photos/frumbert/307532180/sizes/l/in/photostream/ http://www.flickr.com/photos/tgillin/4599272187/ http://www.flickr.com/photos/rolleh/3475746680/sizes/o/in/photostream/ http://www.flickr.com/photos/pamilne/3401930511/sizes/l/in/photostream/ http://www.flickr.com/photos/batintherain/112826092/sizes/l/in/photostream/ http://sherisays.files.wordpress.com/2010/08/drivers-stuck-in-traffic-jam-for-9-days-in-china.jpg
Editor's Notes
- Over 90% of the cost of software development is software maintenance (cite). This alarming trend was predicted as early as 1972. McKinsey suggests that CIOs should spend no more than 40-60% on maintenance. Gartner’s IT Spending and Demand Survey (2002) reports that CIOs are spending 80% of their budgets on maintenance (p12 of presentation). Agile development can help reverse this trend.
- Vote:Who here is working on V<1.0?Of those – who knows up front the majority of the scope of V1.0? The rest should care.On those working
- Vote:Who here is working on V<1.0?Of those – who knows up front the majority of the scope of V1.0? The rest should care.On those working
- SyncSpeed
- Introduced in Lean Product Development by Don Reinertsen and David AndersonVisualize where the Features/Stories are in the workflow across time
- What does it mean to manage flow? Managers take action to stop the line in case of high WIPIdentify bottlenecks and divert resources / focusManagement attention
- What does it mean to manage flow? Managers take action to stop the line in case of high WIPIdentify bottlenecks and divert resources / focusManagement attention
- If our policy/behavior is early start of everything“Working on many things in parallel will ensure high utilization”“Everything is important”“Each engineer has his own baby feature, they don’t want to collaborate, and there is a high collaboration overhead”Batch size is still HIGH
- TODO – NEW PICTURE
- TODO – summarize the tools/tips until nowPut the tips on the screen
- DBA TeamUX ExpertsFoundation/Platform
- TODO – summarize the tools/tips until nowPut the tips on the screen
- TODO – emphasize the shared resources
- Best approach for service delivery (80% of software development in the world is V>1.0)Pragmatic approach to changeEnd to end optimization
- TODO – summarize the tools/tips until nowPut the tips on the screen
- TODO – summarize the tools/tips until nowPut the tips on the screen