DocumentaciónHelp

Start a sprint

Start a planned sprint, record each person's capacity and put the sprint on the desk's board.

On this page

Starting a sprint sets the team's commitment: from that moment, the sprint's points are recorded as Committed and any item that comes in or goes out is recorded as a scope change. The sprint becomes Active and appears on the board.

Before you start

  • You must be the desk's Lead.

  • The sprint must be Planned, with its items already chosen. See Create and plan a sprint.

  • There can't be another active sprint in the desk.

  • The sprint's end date can't have passed.

Steps

  1. Go to Sprints.

  2. On the sprint's card, press Start. You can also open the sprint and press Start sprint.

  3. In the Start window, check the summary at the top: the commitment in points and, if available, the team's average velocity.

  4. If you want, enter each person's capacity for this sprint, with their vacations or absences already deducted:

    • points: how many points they can take;

    • days: how many days they work in the sprint.

    Everyone in the desk appears except those with the Viewer role. The fields are optional.

  5. Press Start sprint.

If it can't be started

Notice

What to do

There's already an active sprint: "name". Close it before starting another one.

Close a sprint and hold the retrospective first. In the list, the Start button is disabled while there is an active one

The sprint has already ended according to its dates: adjust them before starting it.

Press Edit and change the dates

What happens next

  • You see the notice that the sprint started. If the commitment exceeds the team's average velocity or the capacity you entered, the notice says so. It's a warning: the sprint starts anyway.

  • The sprint moves to In progress in the sprint list.

  • The Work on the board shows the sprint with its name, its goal, the days left and the progress in points.

  • At the end of each day, the platform takes a snapshot of the sprint to draw the burndown and the burnup. See Follow a sprint.

  • From now on, sprint items that haven't reached QA when 2 business days or less are left are marked as at risk.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

↑↓ to navigate · Enter to open · Esc to close