Doug Talbot explains the importance of measuring to the Lean feedback cycle providing advice on what to measure and how often.
Richard Rodger discusses measuring the benefits of using microservices from a business perspective in order to evaluate their impact on an organization.
Bill Yetman and Jeremy Pollack discuss using Agile techniques -start simple, get going, iterate- and the “measure everything” principle to create the architecture behind the Family History website.
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.
Graham Brooks explores internal measurements used in a continuous delivery feedback mechanism in order to improve a system's design.
David J. Anderson explains how to use predictability, measurement and change management to balance the factors of observed capability, staffing, and delivery targets to achieve predictable outcomes.
Justin Sheehy explains the principles behind concurrent distributed systems: no global state, no ACID but rather BASE, no RPC but protocols over APIs, prepare for failure, degradation, measurement.
Next Generation of Business-Driven SOA: The Convergence of Performance-Driven Business and Service-Orientation
John DesJardins believes that the new SOA will measure their businesses alignment with IT in order to asses the impact of services or of changes or new initiatives, up-time, response time, etc.
The presentation shows how to project realistic completion dates based on empirical observations based on Velocity for iterative methods and on Cumulative Flow for non-iterative methods.
Metrics at every level of the Agile organization receive scrutiny: Measuring value, team performance, progress, quality, and even code design attributes will be taken into consideration.