Your question is Measure Engineering Delivery Effectiveness. 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).
At Hexaware Technologies, the engineering organization for the Hexaware RapidX delivery platform has grown from 6 to 11 squads in the last two quarters. The VP of Engineering says delivery feels slower even though total story points completed increased from 4,800 to 5,600 quarter over quarter.
In the most recent quarter, on-time release rate fell from 91% to 76%, production defects per release rose from 0.8 to 1.6, average lead time from code commit to production increased from 2.4 days to 4.1 days, and sprint spillover increased from 12% to 23%. Team utilization remains high at 87%, but stakeholder satisfaction from internal delivery surveys dropped from 8.4 to 7.1 out of 10. The CTO asks you to define how Hexaware should track whether engineering teams are delivering effectively, not just shipping more work.
jira_issues: issue_id, squad_id, issue_type, story_points, sprint_id, committed_flag, completed_flag, created_at, done_atgit_prs: pr_id, repo, squad_id, opened_at, approved_at, merged_at, lines_changed, reviewer_countdeployments: deployment_id, squad_id, environment, deployed_at, release_type, rollback_flagincident_log: incident_id, squad_id, severity, created_at, linked_release_id, root_causerelease_calendar: release_id, squad_id, planned_release_date, actual_release_date, release_scopestakeholder_survey: squad_id, quarter, satisfaction_score, business_unit