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)
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
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
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
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
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
51.
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
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
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