A Sprint is a time-box of one month or less after which a “Done”, useable, and potentially releasable product/service Increment is created (this is the official definition in the Scrum Guide).

Sprints are visible as cards in the Storymap Tree, below Releases in the Timeline (When) Folder part.

Sprint Planning

In most cases, Sprints are created in the Product Backlog. A Release may contain one or more Sprints with a start and end date. In the Sprint Planning, the Product Owner and the team will add Stories spanning the time period in effort days.

The team can define Tasks for each Story to further detail implementation chunks. Tasks are created in the Task tab of the Story modal window or in the Sprint Backlog.

Note: You can only add Stories, Issues and Ideas to the Sprint. Not Epics.

Sprint Implementation

During the Sprint period, the team will mark the Tasks as done, while they finish each Task. Agemba will automatically set a Story to done, when all the Story’s Tasks are done.

The team uses the Sprint Backlog to change the state of Stories/Tasks and to follow the progress.