Your question is Measure Engineering Velocity. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You lead an engineering team that ships product changes every sprint, but the org keeps arguing about whether the team is actually getting faster. Some people point to story points completed, others point to cycle time, and a few want to use release count as the main scorecard. The team also supports a B2B SaaS product with frequent customer escalations, so quality and speed both matter.
How do you measure and improve your team's engineering velocity?