ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/bmad-core/checklists/sprint-review-checklist.md

9.2 KiB
Raw Blame History

Sprint Review Checklist

This checklist guides teams through conducting effective sprint reviews that capture achievements, learnings, and set up the next sprint for success.

[[LLM: INITIALIZATION INSTRUCTIONS - SPRINT REVIEW

Sprint Reviews are critical ceremonies for:

  • Demonstrating completed work to stakeholders
  • Capturing lessons learned
  • Adjusting project direction based on feedback
  • Planning upcoming work
  • Updating project documentation

This checklist should be used:

  • At the end of each sprint/iteration
  • Before major milestone reviews
  • When significant changes occur
  • For handoffs between teams

The goal is to create a comprehensive record of progress and decisions.]]

1. PRE-REVIEW PREPARATION

LLM: Good preparation ensures productive reviews. Complete these items 1-2 days before the review.

1.1 Sprint Metrics Collection

  • Sprint goals documented and assessed
  • User stories completed vs planned tallied
  • Story points delivered calculated
  • Velocity compared to previous sprints
  • Burndown/burnup charts prepared
  • Blockers and impediments listed

1.2 Demo Preparation

  • Completed features identified for demo
  • Demo environment prepared and tested
  • Demo scripts/scenarios written
  • Demo order determined (highest value first)
  • Presenters assigned for each feature
  • Backup plans for demo failures prepared

1.3 Documentation Review

  • Dev Journal entries for sprint compiled
  • ADRs created during sprint listed
  • Memory Bank updates identified
  • Architecture changes documented
  • Technical debt items logged

2. STAKEHOLDER COORDINATION

LLM: Effective reviews require the right people with the right information.

2.1 Attendee Management

  • Required stakeholders identified and invited
  • Product Owner availability confirmed
  • Technical team members scheduled
  • Optional attendees invited
  • Meeting logistics communicated
  • Pre-read materials distributed

2.2 Agenda Creation

  • Review objectives defined
  • Time allocated per demo/topic
  • Q&A time built in
  • Feedback collection method determined
  • Next steps discussion included
  • Time for retrospective insights

3. SPRINT ACCOMPLISHMENTS

LLM: Focus on value delivered and outcomes achieved, not just features built.

3.1 Completed Work

  • All completed user stories listed
  • Business value of each story articulated
  • Technical achievements highlighted
  • Infrastructure improvements noted
  • Bug fixes and issues resolved documented
  • Performance improvements quantified

3.2 Partial/Incomplete Work

  • In-progress stories status documented
  • Reasons for incompletion analyzed
  • Carry-over plan determined
  • Re-estimation completed if needed
  • Dependencies identified
  • Risk mitigation planned

3.3 Unplanned Work

  • Emergency fixes documented
  • Scope changes captured
  • Technical discoveries noted
  • Time impact assessed
  • Process improvements identified
  • Prevention strategies discussed

4. TECHNICAL DECISIONS & LEARNINGS

LLM: Capture the "why" behind decisions for future reference.

4.1 Architectural Decisions

  • Key technical decisions documented
  • ADRs created or referenced
  • Trade-offs explained
  • Alternative approaches noted
  • Impact on future work assessed
  • Technical debt created/resolved

4.2 Process Learnings

  • What worked well identified
  • What didn't work documented
  • Process improvements suggested
  • Tool effectiveness evaluated
  • Communication gaps noted
  • Team dynamics assessed

4.3 Technical Learnings

  • New technologies evaluated
  • Performance insights gained
  • Security findings documented
  • Integration challenges noted
  • Best practices identified
  • Anti-patterns discovered

5. STAKEHOLDER FEEDBACK

LLM: Stakeholder input shapes future direction. Capture it systematically.

5.1 Feature Feedback

  • User reactions to demos captured
  • Feature requests documented
  • Priority changes noted
  • Usability concerns raised
  • Performance feedback received
  • Gap analysis completed

5.2 Strategic Feedback

  • Alignment with business goals verified
  • Market changes discussed
  • Competitive insights shared
  • Resource concerns raised
  • Timeline adjustments proposed
  • Success metrics validated

6. NEXT SPRINT PLANNING

LLM: Use review insights to plan effectively for the next sprint.

6.1 Backlog Refinement

  • Backlog prioritization updated
  • New stories created from feedback
  • Technical debt items prioritized
  • Dependencies identified
  • Estimation needs noted
  • Spike stories defined

6.2 Sprint Goal Setting

  • Next sprint theme determined
  • Specific goals articulated
  • Success criteria defined
  • Risks identified
  • Capacity confirmed
  • Commitment level agreed

6.3 Process Adjustments

  • Retrospective actions incorporated
  • Process improvements planned
  • Tool changes identified
  • Communication plans updated
  • Meeting cadence adjusted
  • Team agreements updated

7. DOCUMENTATION UPDATES

LLM: Keep project documentation current with sprint outcomes.

7.1 Memory Bank Updates

  • progress.md updated with completions
  • activeContext.md refreshed for next sprint
  • systemPatterns.md updated with new patterns
  • techContext.md updated if stack changed
  • productContext.md adjusted based on feedback
  • All updates committed and pushed

7.2 Project Documentation

  • README updated if needed
  • CHANGELOG updated with sprint changes
  • Architecture docs updated
  • API documentation current
  • Deployment guides updated
  • User documentation refreshed

7.3 Knowledge Sharing

  • Dev Journal entries completed
  • Key decisions documented in ADRs
  • Lessons learned captured
  • Best practices documented
  • Team wiki updated
  • Knowledge gaps identified

8. METRICS & REPORTING

LLM: Data-driven insights improve future performance.

8.1 Sprint Metrics

  • Velocity calculated and tracked
  • Cycle time measured
  • Defect rates analyzed
  • Test coverage reported
  • Performance metrics captured
  • Technical debt quantified

8.2 Quality Metrics

  • Code review effectiveness assessed
  • Test automation coverage measured
  • Security scan results reviewed
  • Performance benchmarks compared
  • User satisfaction gathered
  • Stability metrics tracked

8.3 Trend Analysis

  • Velocity trends analyzed
  • Quality trends identified
  • Estimation accuracy reviewed
  • Bottlenecks identified
  • Improvement areas prioritized
  • Predictions for next sprint

9. ACTION ITEMS

LLM: Reviews without follow-through waste time. Ensure actions are specific and assigned.

9.1 Immediate Actions

  • Critical fixes identified and assigned
  • Blocker resolution planned
  • Documentation updates assigned
  • Communication tasks defined
  • Tool/access issues addressed
  • Quick wins identified

9.2 Short-term Actions (Next Sprint)

  • Process improvements scheduled
  • Technical debt items planned
  • Training needs addressed
  • Tool implementations planned
  • Architecture updates scheduled
  • Team changes coordinated

9.3 Long-term Actions

  • Strategic changes documented
  • Major refactoring planned
  • Platform migrations scheduled
  • Team scaling addressed
  • Skill development planned
  • Innovation initiatives defined

SPRINT REVIEW SUMMARY

[[LLM: Generate a comprehensive but concise summary for stakeholders and team records.

Include:

  1. Sprint Overview

    • Sprint number/name
    • Duration
    • Team composition
    • Overall outcome (successful/challenged/failed)

  2. Achievements

    • Stories completed vs planned
    • Value delivered
    • Technical accomplishments
    • Quality improvements

  3. Challenges

    • Major blockers faced
    • Incomplete work
    • Technical difficulties
    • Process issues

  4. Key Decisions

    • Technical choices made
    • Priority changes
    • Process adjustments
    • Resource changes

  5. Stakeholder Feedback

    • Satisfaction level
    • Major concerns
    • Feature requests
    • Priority shifts

  6. Next Sprint Focus

    • Primary goals
    • Key risks
    • Dependencies
    • Success metrics

  7. Action Items

    • Owner, action, due date
    • Priority level
    • Dependencies

Keep it scannable and action-oriented.]]

Review Summary Template

Sprint: [Number/Name]
Date: [Review Date]
Duration: [Sprint Length]
Attendees: [List Key Attendees]

Overall Assessment: [Green/Yellow/Red]

Completed:

  • X of Y stories (Z story points)
  • Key features: [List]
  • Technical achievements: [List]

Incomplete:

  • X stories carried over
  • Reasons: [Brief explanation]

Key Feedback:

Next Sprint Focus:

  1. [Primary goal]
  2. [Secondary goal]
  3. [Technical focus]

Critical Actions:

Action Owner Due Date
[Action] [Name] [Date]

Review Completed By: [Name]
Documentation Updated: [Yes/No]