Your question is Measure Team Delivery for MB.OS. 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 are the Engineering Manager for a Mercedes-Benz Group team building a customer-facing MB.OS feature used in the Mercedes-Benz app and in-vehicle digital experience. In the last two quarters, stakeholders say the team is "busy" and shipping often, but product partners are unsure whether delivery quality and business impact are actually improving.
Your team of 9 engineers, 1 QA engineer, and 1 engineering analyst supports one major quarterly release and weekly production deployments. Last quarter, the team completed 48 story tickets, shipped 14 production releases, and closed 91% of planned sprint scope. However, post-release defects rose from 11 to 19, average lead time increased from 6.2 days to 8.4 days, and the share of roadmap items delivered on the committed quarter slipped from 82% to 68%. Meanwhile, MB.OS feature adoption improved from 420k to 470k monthly active users.
The Director of Engineering asks: "What metrics would you use to know whether this team is delivering well, and how would you separate output from actual delivery health?"