CreatingNewSprints

Scrumboard allows teams to Manage new sprints in a very intuitive and easy manner. Unlike many other tools, Scrumboard does not need the team to first create a sprint and then proceed with the other activities of creating and assigning user stories.

The easiest way to create a new sprint in ScrumBoard is to add the name as a tag to the UserStories in the relevant column when uploading UserStories in the DataImport tool.

This create sprints automatically as tags to indicate the temporal event identifying the days of the calendar. The actual dates of the sprint, the release it belongs to and other information can be managed when needed any time before the sprint starts.

To create a new Sprint using the Sprint Administration functions, you can add a sprint, assign it to a release and set the start and end dates of the sprint. NOTE: If the sprint that you are creating over laps with a sprint that is already created earlier, then the tool will inform you of the same and you can take relevant action.

NOTE: If the previous sprint had ended and there is no release or sprint active on the day that you login, the tool will prompt you to create a new release and a new sprint with the relevant details.

SprintPlanning

SprintPlanning activity is where the team identifies the SprintGoal and defines HOW the SprintGoal can be achieved.

ScrumBoard supports both these activities by allowing the team to PlanUserStories.

ScrumBoard provides multiple ways of creating tasks for the user stories, so that team and team members have flexibility on the tool that makes most sense to quickly add tasks and task information to the SprintGoal.

PlanningUserStories

UserStory : As a Team, we can define the SprintGoal in terms of the UserStories that can be completed during the Sprint, So that the expectation can be set to the ProductOwner as to what to expect at the end of the Sprint.

ScrumBoard provides an easy and effective way for the ProductOwner and the team to search for UserStories from the Release/Product BackLog and allows them to assign that story to the Sprint.

By reviewing the Velocity of the team over the past few sprints, the Team can identify the stories that need to be picked up during the sprint based on the ProductOwner prioritization of the features.

The ProductOwner can filter the UserStories from the ProductBackLog based on the the Release that the stories were assigned to. The UserStories already assigned to a sprint can also be searched and moved to the current sprint in case of changed priorities.

The UserStories belonging to a particular Theme can be filtered and easily added to the Sprint, being able to filter the Stories by Themes allows the ProductOwner to be able to intuitively search and filter the stories and add them to the SprintGoal to ensure that prioritization is clear.

The ProductOwner can choose to bring in a few Bugs into the definition of the SprintGoal based on the severity of the bugs and move some pre planned UserStories out of the sprint during the SprintPlanning.