3 Flashcards
What is sprint planning meeting?
The initial step of the sprint.
The team defines what they will build during the sprint and how they will achieve this.
There is no standard way for conducting a sprint planning meeting.
Output of sprint planning meeting
Sprint goal
A list of team members
Sprint backlog
What is timeboxed sprint planning?
The length of sprint planning meeting is determined by the length of the sprint
It is acceptable for the meeting to take less time but not more.
For example, a two week sprint should not require a team to spend more than 4 hours of sprint planning
How to calculate total sprint planning meeting length
The number of weeks in your sprint * 2
What does product owner do in sprint planning meeting
They explain the highest value items in the product backlog
The team responds to the product owner on what they feel they can realistically commit to
The team in sprint planning
Define the work
Assigns the work
Estimates work
Figures how to do the work
Commits to a realistic amount of work for the sprint
Preparing sprint planning
There should be one product backlog one product owner
All important items should have priority ratings to them, different importance ratings
The product owner should understand each story.
Sprint backlog
Contains the user stories they have committed to develop only in this sprint
Team decides how many stories to include in the sprint
How to determine a sprint backlog?
The team has decide which stories to include in a sprint.
There are many ways:
By calculating estimate velocity of the team. (How many story points the team believes they can complete during the sprint)
Add user stories the sprint backlog
Estimating velocity(yesterday’s weather)
First calculate available man-days
Then, calculate focus factor based on previous sprints. Then calculate estimated velocity
Estimated velocity < available man days
This sprints estimated velocity:
(Available man-days) x (focus factor) = (estimated velocity)
Focus factor is an estimate of how focused a team is.
Last sprints focus factor :
(Focus factor ) = (actual velocity ) / (available man- days)
Example of yesterday weather
The last sprint we completed 18 story points working 3 weeks for a total of 45 man days. We have 50 available man days in this sprint. What is our estimated velocity for the next sprint?
1st calculate last sprint focus factor :
18/45 = 40%
2nd calculate the sprint estimated velocity :
40% * 50 man days = 20 story points
What to do when no previous sprint ?focus fago
Use default focus factor
For new teams it’s usually 70%
Adding stories to the sprint backlog
Estimated velocity is 20 story points:
This means the team should add stories to the sprint backlog until it adds up to approximately 20.
You always select the most important user stories first
What is estimating stories?
Estimating is a team activity- every team member is usually involved in estimating every story.
Estimating helps in breaking down user stories into tasks
Planning poker : technique to avoid allowing a team member to affect everybody’s else’s estimate.
Breaking down stories into tasks
Stories are deliverables that the product owner cares about.
Tasks are non- deliverable stuff. Or stuff that the product owner doesn’t care about.
Like:
Developers work items
Usually the time estimate goes up, and thereby gives a more realistic sprint plan.
