How can we measure the impact of our improvement changes?
Understanding the impact of the changes is not only important to see how successful improvements are, it can also motivate the team to continue making improvements. Additionally an unsuccessful change can be treated as a positive learning opportunity and you can inspect and adapt where needed.
When you gauge the impact of improvement, you can measure if the Scrum Team is improving at their purpose, which is to deliver a valuable, usable Increment every Sprint in pursuit of the Product Goal. Two dimensions to consider are: if the team is improving at their capability to deliver value and if the value of the product is improving for the customer.
The Evidence-Based Management (EBM) Guide suggests different measures in its appendix like customer satisfaction, NPS, feature usage, downloads as understanding product value. Flow metrics and measures like cycle time, technical debt, time spent multitasking can capture the team’s time to market and ability to innovate.