Sprint Close – Overview¶

• Table of contents
• Sprint Close – Overview
  • Purpose
  • Scope
  • Key Principles
  • Sprint Close High-Level Flow
  • Definitions

Purpose¶

This guideline defines the standard Sprint Close process using Redmine.
It ensures:

• No loss of sprint history
• Accurate velocity & throughput
• Clear spillover accountability
• Audit-ready sprint records

Scope¶

This process applies to:

• All Scrum / Sprint-based teams
• All items assigned to a Sprint version
• Stories, Tasks, Bugs (unless otherwise specified)

Key Principles¶

• Sprint history must never be lost
• Every completed item must be explicitly tagged
• Every unfinished item must have a spillover reason
• Sprint version must only be cleared after validation

Sprint Close High-Level Flow¶

1. Validate completed work
2. Validate spillover
3. Clear sprint version
4. Lock sprint history
5. Generate metrics

Definitions¶

• Sprint Version – Redmine Fixed Version representing the sprint
• Completed In Sprint – Custom field used as historical truth
• Spillover Reason – Mandatory reason for unfinished work