Posted on 28, Sep 2010
In this step product owner and development team will plan sprint.
Development team meats with product owner on sprint planning meeting. Product owner shows the team his plan for first sprint. Product owner chose stories by top importance (priority).
Switch to the Planning View by click on corresponding menu item. This view provides access to all product planning activities. Users can based on theirs role in a project to:
View displays two boards. Board display stories of sprint and release selected from corresponding combo boxes which are near to board.
We prepared Release A and Sprint 1 in previous steps. We have backlog stories written in our backlog. Now we will plan our first Sprint.
Let’s display stories unassigned to any sprint:
Sort backlog stories by Importance. Now you can drag stories from upper board to bottom showing the Sprint 1.
Drag stories until the sprint’s occupation indicator will not indicate sprint fullness. This indicator calculates sprint occupation by sum of stories’ sizes. This sum must be less or equals then Sprint capacity value entered in the Sprint detail window.
Sprint detail window
As you can see capacity of Sprint 1 is set to 5 story points. This is a value upon team agreed. It is maybe to low, but team is just starting first sprint and team members don’t know how fast are they able to work.
We can assign only one story to this sprint. It is a story “Protocol selection (priority 60, size 5)”. Drag this story from upper board and drop it to bottom board.
You have completed planning for your first sprint now.
It is good to do sprint planning before each sprint. This is a way how to develop your product in an iterative manner.
Every team member must specify tasks on which he will be working. He must estimate duration of every task. Total time of the work will be checked to this duration.
Task can be planned in ScrumDesk different ways.