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.
Joel Semeniuk discusses ways of making better project estimates excluding guessing as much as possible.
Russ Miles discusses the importance of having values at the foundation of one’s beliefs which in turn influence the behaviors resulting in actions.
Anne Thomas Manes discusses SOA goals and objectives used to measure a system’s success, measuring the business value, SOA project metrics, and recommendations on proving the business value of SOA.
It is possible to measure certain properties of code, and on the one hand, correlate them with project factors known to have economic merit and on the other, with programmer-pleasing practices. This session surveys emerging evidence that we can measure the effect of the technical practices of Agile development, and explores what we might be able to do about it to our benefit.
In this presentation filmed during ThoughtWorks’ Quarterly Technology Briefing, Dave Robertson and John Johnston explain what the Agile and User Centered Design’s (UCD) common denominators are, common values being the most important one in their opinion.