In this session, I talk about how empirical data (which I’m calling agile numbers) can serve as signposts on our journey to reach the goal of delivering customer value faster with maximum reliability and minimum issues. I’ll show how agile numbers can help us determine if a practice is worth the investment and whether it will improve our team’s performance. I will also share examples of agile numbers that can assist you in your agile journey. Those numbers are pulled from different sources like scientific studies, research from Google, and the 2017 State of DevOps Report.
The talk explores what empirical data tells us about what works and what doesn’t in software delivery:
* What is the best team structure that leads to high IT performance?
* What is the best architecture that leads to high IT performance?
* Do skills, experience and personalities on a team what distinguishes great teams?
* What leadership attributes are tied to high IT performance?
Is estimation scientifically valid?
* Do code review works? How much time should we spend on them?
* How long is too long for a branch?
* And much more