Contents
What role do user stories play in agile planning?
A user story is a part of an Agile software development approach to acquire the details of a requirement from an end-user’s point of view. The user story specifies what type of user you are, what you want and the reason behind it.
What roles should be present during sprint planning?
In Scrum, the sprint planning meeting is attended by the product owner, ScrumMaster and the entire Scrum team. Outside stakeholders may attend by invitation of the team, although this is rare in most companies.
What is the main purpose of sprint planning?
Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team.
How many story points do you get in a sprint?
Moving forward, the scrum team would know that, on average, they complete 30 story points per sprint and could use this as a guide when going through the backlog items in sprint planning.
When to assign story points to a story?
A story point number is the outcome of an estimation of a user story, so story points are assigned when the team estimates the stories. The latest point in time where estimation can/should be done is when a story is being considered for inclusion in the current or upcoming sprint. This is normally during the planning session.
When does a scrum team assign story points to the stories in?
Scrum Team who is practicing XP will do Planning Poker with Story Points every Sprint Planning. Many Scrum Team found this Planning Poker practice with Story Points is helpful. While the blog seems to imply that XP wants you to play Planning Poker each Sprint Planning, the XP rules don’t talk about Planning Poker at all.
When is the team estimating in a sprint?
At the beginning of every Sprint the team signs up work on what they think can be accomplished during the course of a Sprint. The team estimates the stories in Story points. As a first step in the Sprint planning, I estimate the capacity of the team – number of days each scrum member available during the course of the Sprint.