Tingg

h1. Sprint Close – Overview

{{toc}}

h2. 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

h2. Scope

This process applies to:

* All Scrum / Sprint-based teams

* All items assigned to a Sprint version

* Stories, Tasks, Bugs (unless otherwise specified)

h2. 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

h2. Sprint Close High-Level Flow

# Validate completed work

# Validate spillover

# Clear sprint version

# Lock sprint history

# Generate metrics

h2. 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