Agile Works So Why Do Large Enterprises Fail So Often?Steve Elliott
schedule 2 years agoSold Out!
We would all agree that Agile is mainstream, agile is the future and that Agile DOES work. So why then do we see so many failed or moderately successful large scale transformations? The answer is complex but there are many things that can be done to improve your odds of success.
In this talk we will explore 7 proven methods to help you see bottlenecks, clear land mines and drive better results. The seven points we will explore include:
- Methods to scale up collaboration (above the team level) using agile principals
- New methods to scale up estimation by combining standard methods like WSJF, Points, T-Shirts, Team Weeks with Monte Carlo what-if simulations.
- Objectives as work packages
- Value streams in a three tier model with a RACI twist
- Agile Ghantt-ification and other scaled-up visualizations
- The effects of WIP discipline at the portfolio level
- How calculate capitalization regardless of team methods (cycle time, points, hours)
How much ($) and how long (time) of Large-Scale Agile Projects: The Estimation ChallengeSatish Thatte
schedule 2 years agoSold Out!
Estimating how much a project would cost and how long it would take has always been a challenge. These are critical business questions, and not answering them is not an option. Estimating large-scale projects is even more difficult and complicated not only because of their large scale and distributed nature, but also due to faulty estimation methods widely used today. Large-scale agile projects consist of several teams (organized into programs and portfolios). Teams are often distributed. If you are doing story point estimations and generating reports for large-scale agile projects in blissful ignorance of the fact that story point scales used by different teams may not be the same, you will make wrong decisions caused by wrong estimates and metrics.
All Agile Lifecycle Management tools expect and assume that the story points entered by you in the tool are "normalized" across teams, i.e., they follow the same scale. Story points entered into the tool without normalization (garbage-in) will generate meaningless reports and metrics (garbage-out).
You may also be hard pressed to estimate portfolios and programs when their stories are not even defined. This is like estimating something that is unknown!
I will present solutions to these and other estimation challenges for large-scale agile projects.
I will present the Calibrated Normalization Method (CNM) for scalable estimation, which I have developed and applied in my client engagements since 2010. CNM promotes local, decentralized, and autonomous decision making at the team level by allowing teams to use their own story point scales, and normalizing team story points with a novel technique. I will also contrast and compare CNM with centralized methods and the SAFe method for estimation.
I will demonstrate the use of a normalization calculator for doing normalization math needed for bottom-up as well as top-down estimations in large-scale projects. This calculator has been developed and refined with actual usage; it makes story point normalization calculations very quick and easy, and avoids human errors.