A sprint is a time-boxed period during which a team works to complete a set of tasks to achieve a specific goal. This approach breaks down larger projects into smaller, more manageable pieces of work.

Why Use Sprints?
Encourages focus by limiting work in progress
Enhances transparency with a clear view of what is being worked on
Delivers value incrementally and helps teams adapt to changing requirements
Key Components of a Sprint
A sprint includes the following elements:
Name: The identifier for the sprint
Start Date: The date when the sprint begins
End Date: The expected date when the sprint will conclude
Completed Date: The actual date when the sprint is closed
Goal: The objective or focus of the sprint
Issues: The work items in the sprint, such as stories, tasks, and bugs
Metrics Tracked at the End of a Sprint
At the conclusion of a sprint, you can track several metrics to assess performance:
Duration: The time elapsed between the start and completion dates
Completion Rate: The percentage of work completed, based on story points or tasks
Unplanned Work: The amount of work added after the sprint begins
Initial Scope: The total work defined at the start of the sprint
Total Scope: The total work included in the sprint by the end
Carry Over: The work not completed during the previous sprint and included in the current sprint
Customizing Sprints in Kindor
Kindor allows for customization of sprints to better align with your team's workflow:
1. Planning Window
The planning window is the time period after a sprint begins during which adjustments can be made without affecting metrics like scope and unplanned work.
Default Setting: 2 days.
Example: If your sprint starts on Monday and the planning window is 2 days, you can add or remove tasks until Tuesday without impacting metrics such as Completion Rate or Unplanned Work.
2. Cancellation Statuses
A list of statuses that represent canceled work, and Tasks with a status in this list won’t count as work completed, but it will be part of the Scope of the Sprint.
Default Setting: Dismiss, Won't Do, Cancelled, Canceled, Declined, Cancelado, Discarded, Descartado
Example: A task with 5 Story Points is included in a sprint. Midway through the sprint, the team realizes the task does not need attention and moves it to a status called “Dismiss,” which is listed as a cancellation status. Although the task remains part of the sprint scope since it was planned initially, it will not count as completed work for the team members.
How Kindor Calculates Sprint Metrics
Duration: The difference between the Completed Date and Start Date
Initial Scope: Total issues added before the planning window ends
Total Scope: Total issues included in the sprint
Unplanned Work: Issues added after the planning window ends, over the Total Scope
Completion Rate: The ratio of Completed Issues over Total Scope. For this calculation:
Issues must be linked to the sprint
Parent issues with subtasks are excluded, and the subtasks are counted instead
Example: If a sprint contains a user story worth 5 story points and 3 subtasks worth 1 story point each, the subtasks will be counted in place of the parent story for metrics
Disclaimer: If a task is marked as completed before the start of the sprint, it will not be considered part of the sprint's scope. This is to ensure that metrics accurately reflect the work completed during the sprint. Including pre-completed tasks would inflate metrics like the Completion Rate and Total Scope, giving a misleading picture of the team's performance. By excluding these tasks, we maintain the integrity of the sprint's data, allowing for a clear evaluation of the team’s efforts and achievements within the defined sprint timeline.
Understanding Metrics in Context
Metrics are essential for evaluating sprint performance and identifying areas for improvement. By customizing settings like the planning window and cancellation statuses, teams can tailor metrics to reflect their unique workflows accurately.
Kindor’s sprint dashboard provides insights that empower teams to maintain focus, improve transparency among other areas, and continuously enhance their delivery process.
Comments