Agile teams have a responsibility to help the business understand the financial costs of potential work. By estimating how long a project will take, the total cost is primarily a function of how much time it will take to complete the work.
In this webinar, we explored various techniques that Agile teams use to generate estimates that help everyone make responsible choices.
Bernie Maloney: Bernie’s first position was designing devices that protect telephone networks from lightning strikes. Across his 25 years of engineering and leadership experience, Bernie has worked with firms including Bell Telephone Laboratories, HP, TiVo, Cisco, and many more. In addition to his client work, he teaches Agile Product Development at Stanford Continuing Studies. Leading through influence rather than authority, Bernie believes that Accelerating Genius is possible in any leader, team, or business and can lead to success at work.
Luke Hohmann: Luke Hohmann is the founder and CEO of Conteneo In.(formerly the Innovation Games Company). Conteneo's enterprise software platforms and professional services merge collaboration frameworks, data analytics, and domain expertise to help organizations optimize decision making in the areas of strategy, innovation, sales, product development, and market research. Luke is also co-founder of Every VoiceEngaged Foundation, a 501(c) 3 nonprofit that helps citizens, governments, and other nonprofit organizations collaborate at scale to solve technical and wicked problems.
Answer: Try developing a list of factors you͛d like your team to consider when developing their estimate (try using the factors we discussed in the webinar – risk, complexity, and so forth). Use this list to develop your estimates and then compare your estimates to your actuals. Use the variances to reflect on your checklist and see if you can improve your checklist.
Answer: As we outlined in the webinar, Risk is one of the attributes that feed into both estimates of effort and the sequencing of work. At Conteneo, when we͛re undertaking new development, we like to tackle risky items first, then fun items.
Answer: Although Scrum does not recommend the use of a roadmap, we believe that roadmapping is essential for effective products and services, especially in B2B markets where buyers need to engage in long-term planning choices. We find that T-Shirt sizing of roadmap items works well. See the Collaboration at Scale webinar on Agile Roadmapping for more details.