In my recent posts, we’ve looked at several ways of using metrics to help understand the delivery of teams across different aspects. Looking retrospectively is a great way of identifying ways to improve – but you also want to use your data to help you be more proactive and identify ways to better plan and predict the outcomes of your different delivery efforts. In software delivery, speed and quality mean little if outcomes are unpredictable. Leaders and stakeholders need to

My last two blog posts have focused on the importance of metrics and how to capture your data to create meaningful metrics . I now want ot turn attention to focusing more specifically on the details of the metrics themselves that you should be looking at and why. If we look at the modern expectations on software delivery, it is often about speed. How fast can you get ot the market, deliver a fix, or deploy a new feature? In software delivery, speed without flow is chaos -