Project

General

Profile

Actions
History

Sprint YYYY-NN – Sprint Summary

Sprint: Sprint YYYY-NN
Dates: Start Date → End Date
Team: [Team Name]
Sprint Goal: [Single, clear sprint goal]

1. Sprint Goal

Describe the one primary objective this sprint existed to achieve.

Rules:
  • One goal only
  • Outcome-focused
  • No task lists

Example:
bq. Enable end-to-end tenant onboarding with audit-ready logging.

2. Sprint Scope (Committed Work)

High-level description of what was committed at sprint start.

Guidelines:
  • Summarize themes, not tasks
  • Do not copy issue lists
  • Do not update after sprint start
Example:
  • Tenant provisioning flow
  • Audit logging improvements
  • Deployment pipeline hardening

3. Sprint Outcomes (What Was Delivered)

Summarize what was actually delivered by the end of the sprint.

Rules:
  • Outcome-based
  • No status updates
  • No partial credit language
Example:
  • Tenant provisioning available for internal testing
  • Audit logs enabled for all onboarding steps

4. Sprint Metrics (Final)

These values must reflect final, closed sprint data.

Metric Value
Velocity (Story Points)
Stories Completed
Stories Committed
Spillover Count
Source of truth:
  • Sprint History, Metrics & Audit
  • Saved queries only

bq. Metrics must not be manually adjusted.

5. Spillover Summary (If Any)

Summarize unfinished work and why it spilled over.

Guidelines:
  • Reference patterns, not excuses
  • Do not re-estimate here
  • Detailed reasons live in issue fields
Example:
  • External dependency delays
  • Underestimated complexity in integration work

6. Quality & Stability Notes

Capture quality-related observations.

Examples:
  • Major defects discovered during sprint
  • Stability concerns
  • Technical debt introduced or avoided
Do NOT:
  • Log bugs here
  • Track fixes here

7. Stakeholder Feedback (Sprint Review)

Summarize key feedback received during Sprint Review.

Examples:
  • Positive validation of feature direction
  • Requests for follow-up improvements
  • Concerns raised

This section informs backlog refinement.

8. Retrospective Summary

Capture team learning, not discussion transcripts.

What Went Well
  • [Bullet points]

What Didn’t Go Well
  • [Bullet points]

Improvement Actions
  • Action → Linked Issue ID (if created)

Rules:
  • Actions must be concrete
  • Actions should result in backlog items if needed

9. Links & References

  • Sprint History Queries:
    • Sprint History – Completed items (Sprint YYYY-NN)
    • Sprint Metrics – Velocity (Sprint YYYY-NN)
    • Sprint Metrics – Spillover (Sprint YYYY-NN)
  • Related Releases (if applicable):
    • Release X.Y – Name

10. Sprint Closure Declaration

This sprint is officially closed.

Field Value
Sprint Closed On
Closed By
Notes Optional

bq. After closure, this page must not be edited except for corrections approved by the Scrum Master.

11. Governance Rules (Read Before Editing)

This sprint wiki page must NOT contain:
  • Task tracking
  • Status updates
  • Daily notes
  • Rewritten metrics
  • Post-hoc scope changes

Sprint execution lives in issues, not in wiki.

12. Final Statement

bq. This page exists to preserve sprint memory, not to manage sprint execution.

If this page cannot be understood six months later, it has failed its purpose.

Updated by Redmine Admin about 2 months ago · 1 revisions