|
Notes from presentations are available on this site (if the presenter has provided
us with his/her materials). Simply go to the PROGRAM link and click on the session. |
The Business Case For Agility: The Lean-Agile Connection
Alan Shalloway (Net Objectives)
Talking Heads · Process
Thursday, 14:00, 1 hour 30 minutes | Auditorium
Download Presentation
Mary and Tom Poppendieck put forth 7 principles of lean software development in their seminal text: Lean Software Development: An Agile Toolkit for Software Development Managers. These 7 principles are: deliver fast optimize the whole eliminate waste build integrity in create knowledge respect people defer commitment This seminar presents the case for why we must develop software consistent with the agile methods of Scrum and Test-Driven Development. Four aspects of agile methods in particular are investigated: 1. Iterative development. The best way to eliminate waste is to not build things that aren't needed. This implies an iterative process where priorities are continuously re-examined. 2. Scrum. Lean's workcell concept is manifested in Scrum's cross-functional team. Scrum's emphasis on team also includes the principles of amplifying learning and localizing responsibility. 3. Automated testing. Test-Driven Development is consistent with the Lean's autonomation principle of a smooth flowing production line that is stopped anytime there is an error to get at the root cause of the problem. This follows the principle of build integrity in. 4. Writing quality code that can be refactored. Deferring commitment is an integral part of agile coding. By writing just what you need now, you don't build in structure until you later discover what is truly needed. This seminar provides insights into how Lean guides many current agile processes. This provides both a business case for agile methods as well as giving developers insights into how to better follow agile methods. Outline: * The seven principles of Lean Software development Eliminate waste * Deliver fast * Optimize the Whole * Eliminate waste * Build integrity in * Create knowledge * Respect people * Defer commitment * The Lean-Agile Connection * How Lean implies an iterative process * Lean and Scrum: Work cells and cross-functional teams. Building code as an integrated process of analysis-design-code-test. * Automated testing: Building code only after its acceptance requirements have been specified * Eliminating waste by managing change. * Conclusions






