Sprints

Sprint series are time-bound periods of focus and work for the team. During a sprint, the team aims to complete a set of issues. You can configure sprint series under Settings > Workspace > Sprints.

Configuring a sprint series

To configure a sprint series, you'll need to make some decisions about how you want to have your team work. Required settings will have a default value but are editable.

Once a sprint series is live (a full sprint within the series has started and/or finished), you will no longer be able to edit the settings for that sprint series. To make changes, you'll need to create a new sprint series.

Timeline

For each sprint series, you'll need to define a timeline:

• Sprint start day: The day of the week on which a sprint will start. The most common day for a sprint to start is Monday.

• Sprint end day: The day of the week on which a sprint will end. The most common day for a sprint to end is Friday.

• Sprint duration: The number of weeks that a sprint will span. The most common duration for a sprint is 2 weeks.

• Sprint launch: This is when any ticket assignment updates are made and team members are notified of their work for the upcoming sprint. The sprint launch can happen at the same time as the sprint start or the day before.

• Sprint close: This is when the sprint is closed and locked. The sprint close can happen at the same time as the sprint end or can happen the day after.

The most common setup has the sprint launch take place 1 day before the sprint start, and the sprint close takes place 1 day after the sprint end. This way, team members are alerted about their work before the sprint begins, and have time after the sprint ends to ensure that all of their issue statuses are updated.

Capacity

You can configure how Hurdle calculates team capacity for each sprint within a series, by setting a sample size and measuring method: Average or Median. An upcoming sprint's capacity will be determined by applying the appropriate measure to the velocities of the sprints in the sample set.

Configuration:

• Rolling: Specify the number of previously completed sprints to sample.

• All sprints: Use all of the previously completed sprints in the series as the sample.

• Last sprint: Use only the previous sprint to determine capacity.

Carryover

You're also able to determine how incomplete, or in-progress, issues at sprint close are treated during planning for the next sprint in the series. You can automatically carry-over all issues that are not started or in-progress.

Multiple sprint series

There are no limits to the number of sprint series that can be created within a single workspace. Multiple sprint series can be active at the same time.