Tap ScrumFunction ‘Sprint Planning’ (6) to run Sprint Planning. Whether you do this step on your own or in a meeting, here is where you define a sprint’s workload. Specific tasks that will be worked this sprint are identified and a story point value is assigned for each.
When you started the project, you defined KEY sprint variables in the profile: Target Velocity, sprint length, when a task is ‘done’, and average cost per team member. You can change these settings at any time (edit the project from the home page). An overview of the process looks like this…
Get ready to assign story points, with or without a team meeting.
Identify tasks to vote on (establish story point values)
Manage an active sprint planning session vote using the ScrumMaster™ application.
Accept each task vote, and when ready, close the Sprint Planning session.
ScrumMaster dynamically tallies team member votes to establish the ‘Agreed upon Story Point Value’ for each task in the sprint, whether you manually enter an individual’s vote or they use Agile Story Sizing Cards™. It also automatically tracks meeting time and cost, based on number of meeting participants whose work contributes to backlog burndown and meeting time (minimum 1 Story Point Value).
 |
 |
 |
NextWave ScrumMaster™ 