Today I want to tell you a little bit about our Sprint planning meeting. Today we started our next two week Sprint for the current project we are working on. In scrum you start each spring off with a Sprint planning meeting. What this does is allows the team to decide on how many user stories they will be able to complete during the next sprint. The Product Owner is responsible for prioritizing the most important user stories or functions that the customer will get the most benefit from. The team starts at the top of the list and estimates how many story points each story is worth. In our case, some of this was done during the last sprint, we took about two hours a week to groom the backlog. With this we were able to have some of the planning done before we started our Sprint planning meeting. We decided how many user stories we could complete this upcoming spring, in this case we settled on 30 story points. On our first sprint we thought we could complete 55 story points and actually only completed 23. From there we backed down to 25 story points and were able to complete 27 story points. We have progressively increased our velocity since then and are now working at about 30.
During the second part of our spring planning meeting the team breaks down the user stories into task. There is not a whole lot that I have to do during this time since I am the scrum Master. I usually go about my business taking care of issues that will slow down the team. Once the team has broken the user stories down into task they began to start development by taking a task to work on.
During the second part of our spring planning meeting the team breaks down the user stories into task. There is not a whole lot that I have to do during this time since I am the scrum Master. I usually go about my business taking care of issues that will slow down the team. Once the team has broken the user stories down into task they began to start development by taking a task to work on.
