This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog :
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
Sprint in Scrum [or an iteration in a XP team] is a time period (can be anything from 2 to 8 weeks) in which the team does whatever it can to develop software as per the features/ requirements that the Team has committed to .
The basic mechanics of a sprint in Scrum is centered on it being time boxed to a fixed duration . A 2 week sprint will end in 2 weeks even if all the work the team committed to is not completed.
The team might need to take on more work [finish all requirements too soon] or need to bump off some requirements [if they find they committed to too much work].
The team asks as many questions as possible [acceptance test cases/ test data/ UI designs etc] as they can to the product owner for each requirement and give a final commitment before moving to Part II of the sprint planning session.
There might be more or less tasks, depending on complexity.
As the team has not started working on any task, all tasks are pending and work remaining for each of the tasks is as the team has estimated.
It is important to understand that the team should think of all the tasks it can for each requirement so that the requirement is really done , note it down and estimate it as best as it can and then quickly move to the sprint.
If the team needs to add a task midway, then the team should definitely do so for each of the requirement.