Fred Brooks once stated so wisely "How does a project get to be a year late? … One day at a time." Lean Development and queuing theories offer help so that this won't happen. The suggested remedy is to implement a steady flow in order to achieve maximum productivity. However, most teams and organizations are far from reaching that goal and moreover it is often unclear which approach leads to what kind of delay. In-depth examination shows how generally accepted concepts such as Definition of Ready, Clean Code, or experts in a team can lead to costs of delay. In this session Jutta presents simple tools and methods for uncovering hidden costs of delay. These tools and methods can be applied in various contexts: In small and large teams as well as in co-located and distributed teams. Using an agile approach will help to make these cost visible.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

- Defining the Context - Metrics - Increasing Efficiency - Summary

Learning Outcome

Attend this session in order to achieve for example the following learning objectives: - Understand cost of delay - Learn about analysis of value stream and cycle times - Recognize the effect experts have on team productivity

Target Audience

Product Owner, Scrum Master, Project Manager, Portfolio Manager

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal