Sprint Audit & Best Practices¶

• Table of contents
• Sprint Audit & Best Practices
  • Scope Change Tracking (Optional)
    • Q11 – Scope Added After Sprint Start
  • Naming Convention
  • Common Mistakes to Avoid
  • Outcome

Scope Change Tracking (Optional)¶

Redmine does not natively track mid-sprint additions.
Use creation date as approximation.

Q11 – Scope Added After Sprint Start¶

• Filters:
  • Fixed version = Sprint 2025-03
  • Created on > Sprint start date

• Saved as:
  Sprint Audit – Scope added mid-sprint (approx)

Naming Convention¶

Always duplicate queries and rename per sprint:

• Sprint Close – ... (Sprint YYYY-MM)
• Sprint History – ... (Sprint YYYY-MM)
• Sprint Metrics – ... (Sprint YYYY-MM)

Common Mistakes to Avoid¶

• Clearing sprint version too early
• Using Fixed Version as history
• Missing spillover reasons
• Editing sprint history after closure

Outcome¶

Following this process ensures:

• Clean sprint closure
• Reliable velocity data
• Strong retrospective insights
• Audit-ready delivery history