Sam McAfee outlines an approach they are using at Neo to help their clients integrate business metrics and probabilistic modeling into their prioritization process.
Chris Young explains how he is using Little’s Law to estimate a project’s delivery rate.
Dan Brown explains the difference between forecasting and estimating, and how one can better forecast delivery with less effort and more accuracy than with estimation.
Chris Trevarthen discusses how to reduce the amount of time spent estimating, providing more meaningful estimates, and building trust with the business.
Seb Rose wonders if estimates are worthwhile and discusses what business people – Steve McConnell, Demarco, Lister, Disraeli - have to say about this.
Chris Chapman teaches delivering software without estimates through the Great Canadian #NoEstimates Puzzle Experiment, asking the participants to collaboratively build a jigsaw puzzle.
Neil Killick exposes the risks inherent to the estimation culture, proposing practical alternatives for the project and spring level.
Craig Smith, Renee Troughton discuss improving visual management: different types of story walls, ways to visualize the product backlog, the important of queue columns and WIP limitation, etc.
Neil Killick proposes ways to reduce risk and uncertainty, calculate a product’s price, determine delivery dates and roadmap, do Scrum and XP without using estimates.
Steve Lawrence showcases several agile metrics supporting an organization’s objectives, but also addresses some of the bad metrics and the 7 sins of Agile measurements.
Patrick Debois discusses the current state of monitoring and metrics, how developers and the company can benefit from them, and how to improve the collection of metrics and the monitoring process.
Erik Dörnenburg shares techniques for estimating code quality by collecting and analyzing data using the toxicity chart, metrics tree maps, size&complexity pyramid, complexity view, code city, etc.