Jira provides a powerful way to start and end sprints. Kendis has bi-directional sync with Jira and once sprint starts in Jira, it can trigger the "Sprint Tracking for Committed Load" in Kendis too.

The reason to start the sprint tracking in Kendis is to set the baseline contents for each sprint at Kendis and provide information for tracking of

  • Committed Load: Contents in the sprint at the start. If any story moves to another sprint during or at the end of the sprint, it would be possible to track. Most importantly, when the sprint closes in Jira, all the open stories move to the next sprint or backlog and thus leaving no easy trace to find out what was committed and what was delivered.

  • Spillovers: Incomplete stories that moved to another sprint are considered "Spillovers". There are filters available at Analytics to view spillovers.

How to Start Sprint Tracking

Sprint can be started for a single team from the team area or there is an option at the board to start sprint for all teams.

When you press this "Start Sprint" option on the board, it will

  • List down all the sprints

  • If the sprint is mapped to Jira sprint, then the Jira sprint name will be shown along with the status, e.g., in this case, Team DWH Sprint 3 of Kendis is mapped to "Team Mars_Iteration 3" sprint in Jira and its status in Jira is "future", which means it's not started yet in Jira

You can select an individual team sprint to start or select the top option to start all sprints.

What happens to Jira sprint status when you start in Kendis?

When you start the sprint in Kendis, it doesn't change status in Jira at all. Start sprint in Kendis will barely take a snapshot of the contents and will log it to show the differences in analytics at Kendis.

What is Reset Start Sprint Tracking

Once sprints are started, you will see the date when it started, and also there will be an option to reset the start of the sprint. In case the sprint is started accidentally or there have been major changes in the sprint and you would like to reset the baseline for your analytics and tracking purposes, this option can be used.

This action will have no impact to Jira sprint status

End Sprint Tracking

This option will mark the "End of Sprint" in Kendis, this will have no impact on Jira sprint status. All the stories that will be moved to other sprints will be treated as "Spill over" in the analytics.

Audit Log

Kendis logs the entry in "Audit Log", available under the Board Settings menu. The audit log entry will show

  • Sprint start time and user name

  • Sprint end time and user name

  • Sprint reset start action performed by the user and at what time.

Did this answer your question?