sprint-reviewer-data
Agent: Data Analyst
L2 data analyst (Nx) responsible for data modelling, instrumentation implementation, metrics dashboards, funnel analysis, and signal synthesis.
Department ethos: ideal-data-growth.md
Skill Description
The sprint reviewer audits all data deliverables completed in the current sprint — instrumentation implementations, dashboard builds, data model changes, and analysis reports — to confirm each meets the acceptance criteria defined in the ticket and the standards defined in the instrumentation spec.
When to Use
- When the sprint approaches completion and data work items need sign-off before the sprint review meeting.
- When multiple data tasks complete in parallel and need consolidated quality review.
- When a prior sprint had data quality issues escape review, and the team wants to prevent recurrence.
Workflow
- List deliverables: Pull all data-related tickets marked "done" or "in review" in the current sprint. Categorize by type (instrumentation, dashboard, analysis, data model).
- Review instrumentation: For each instrumentation ticket, confirm the verification report exists, events pass spec validation, and production deployment is scheduled or complete.
- Review dashboards: For each dashboard ticket, verify metric accuracy against raw queries, confirm layout matches the design spec, and check that documentation exists.
- Review analyses: For each analysis ticket, validate methodology, check data sources, and confirm the output addresses the question posed in the ticket.
- Compile review summary: Produce a sprint data review summary listing each deliverable, its status (approved / needs rework), and specific feedback for any rework items.
Anti-Patterns
- Rubber-stamping done tickets: Marking deliverables as reviewed without checking the output produces a false sense of quality. Why: unreviewed instrumentation ships bugs to production; unreviewed dashboards display wrong numbers.
- Reviewing in isolation: Checking each deliverable without considering cross-deliverable dependencies misses integration issues. Why: a dashboard built on a data model that changed in the same sprint may reference deprecated columns.
Output
Success:
- A sprint data review summary with pass/rework status per deliverable and specific feedback for any items requiring rework, delivered before the sprint review meeting.
Failure:
- Data deliverables ship without review and quality issues are discovered post-sprint. Report the escaped issue, its impact, and the review process gap that allowed it.
Related Skills
1---2name: sprint-reviewer-data3description: This skill reviews data deliverables in sprint to confirm instrumentation and dashboards meet requirements. Use when asked to QA analytics deliverables, review sprint data work, or sign off on instrumentation and dashboard completeness. Also consider at sprint end when data work items are marked done. Suggest when data tasks close without explicit review.4---56# sprint-reviewer-data78## Agent: Data Analyst910L2 data analyst (Nx) responsible for data modelling, instrumentation implementation, metrics dashboards, funnel analysis, and signal synthesis.1112Department ethos: [ideal-data-growth.md](../../../../departments/data-growth/ideal-data-growth.md)1314## Skill Description1516The sprint reviewer audits all data deliverables completed in the current sprint — instrumentation implementations, dashboard builds, data model changes, and analysis reports — to confirm each meets the acceptance criteria defined in the ticket and the standards defined in the instrumentation spec.1718## When to Use1920- When the sprint approaches completion and data work items need sign-off before the sprint review meeting.21- When multiple data tasks complete in parallel and need consolidated quality review.22- When a prior sprint had data quality issues escape review, and the team wants to prevent recurrence.2324## Workflow25261. **List deliverables**: Pull all data-related tickets marked "done" or "in review" in the current sprint. Categorize by type (instrumentation, dashboard, analysis, data model).272. **Review instrumentation**: For each instrumentation ticket, confirm the verification report exists, events pass spec validation, and production deployment is scheduled or complete.283. **Review dashboards**: For each dashboard ticket, verify metric accuracy against raw queries, confirm layout matches the design spec, and check that documentation exists.294. **Review analyses**: For each analysis ticket, validate methodology, check data sources, and confirm the output addresses the question posed in the ticket.305. **Compile review summary**: Produce a sprint data review summary listing each deliverable, its status (approved / needs rework), and specific feedback for any rework items.3132## Anti-Patterns3334- **Rubber-stamping done tickets**: Marking deliverables as reviewed without checking the output produces a false sense of quality. *Why*: unreviewed instrumentation ships bugs to production; unreviewed dashboards display wrong numbers.35- **Reviewing in isolation**: Checking each deliverable without considering cross-deliverable dependencies misses integration issues. *Why*: a dashboard built on a data model that changed in the same sprint may reference deprecated columns.3637## Output3839**Success:**40- A sprint data review summary with pass/rework status per deliverable and specific feedback for any items requiring rework, delivered before the sprint review meeting.4142**Failure:**43- Data deliverables ship without review and quality issues are discovered post-sprint. Report the escaped issue, its impact, and the review process gap that allowed it.4445## Related Skills4647- [`instrumentation-verifier-data`](../instrumentation-verifier-data/SKILL.md) -- instrumentation verification is a key input to the sprint review.48- [`metrics-dashboard-builder`](../metrics-dashboard-builder/SKILL.md) -- dashboards are a primary deliverable reviewed in sprint.49- [`sprint-reviewer`](../../../product/product-manager/sprint-reviewer/SKILL.md) -- the PM sprint reviewer covers product deliverables; this skill focuses on data deliverables.