You’re the analytics partner for Uber Eats Merchant Growth. The team is building a new feature called “Smart Promotions” that helps restaurants automatically create discounts during slow hours. The feature is expected to drive +0.6% marketplace gross bookings in the next quarter and is tied to a public commitment in the quarterly business review (QBR). The org runs 2-week sprints with a 6-person engineering squad, 1 PM, 1 designer, and shared QA.
Over the last 4 sprints, leadership has noticed that the team is missing milestones: the beta launch slipped by 3 weeks, and cross-functional partners (Sales, Support, Legal) are escalating because merchant comms and training depend on the delivery date. The EM claims the team is “working hard” and points to high commit counts and long hours. The PM believes scope creep is the issue. Finance is worried because the delay pushes expected revenue impact out of quarter.
You have access to Jira, incident logs, and production deploy metadata. You’re asked to use velocity and related delivery metrics to correct the team’s trajectory—not just report what happened, but identify the most actionable drivers and propose a plan that can be executed within the next 2 sprints.
Stakeholders are asking:
| Source | What it contains | Grain |
|---|---|---|
jira_issues | issue_id, team_id, sprint_id, story_points, issue_type (story/bug/chore), created_at, started_at, done_at, status, labels | per issue |
jira_sprints | sprint_id, start_date, end_date, planned_capacity_points, committed_points | per sprint |
deployments | service_name, deploy_at, commit_sha, change_size_loc, rollback_flag | per deploy |
incidents | incident_id, severity, opened_at, closed_at, owning_team, root_cause | per incident |
oncall_pages | page_id, team_id, page_at, ack_at, resolved_at, severity | per page |
product_events | feature_flag, exposure_at, merchant_id, funnel events for Smart Promotions | per event |
Constraints: