Selecting user stories during sprint planning Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How can I manage team distractions like chit-chat?In Scrum, what should we do with partly-completed work started at the end of a Sprint?How does the team deliver consistent velocity when user stories are de-scoped mid-way through a sprint?Why does our Sprint Planning not align with our original Release Plan?Do user stories mean rework? How much is ok?How to address delivery of production fixes in scrum?How to deal with tasks detalization in sprint planning?Should a technical person take part of the user stories prioritization process?What should we do if there are not enough PBIs to fill a final Sprint in Scrum?Agile user story's task estimationVelocity calculation based on number of user stories completed in a sprintNeed help for sprint planning when tasks are not done in previous sprint
What came first? Venom as the movie or as the song?
Will I be more secure with my own router behind my ISP's router?
Weaponising the Grasp-at-a-Distance spell
Providing direct feedback to a product salesperson
Compiling and throwing simple dynamic exceptions at runtime for JVM
"Destructive force" carried by a B-52?
How to produce a PS1 prompt in bash or ksh93 similar to tcsh
Are Flameskulls resistant to magical piercing damage?
How to charge percentage of transaction cost?
Can I take recommendation from someone I met at a conference?
Has a Nobel Peace laureate ever been accused of war crimes?
How to keep bees out of canned beverages?
Why isn't everyone flabbergasted about Bran's "gift"?
How to leave only the following strings?
What is the difference between 准时 and 按时?
Proving inequality for positive definite matrix
lm and glm function in R
Lights are flickering on and off after accidentally bumping into light switch
Can the van der Waals coefficients be negative in the van der Waals equation for real gases?
How to ask rejected full-time candidates to apply to teach individual courses?
Can this water damage be explained by lack of gutters and grading issues?
Suing a Police Officer Instead of the Police Department
What is the ongoing value of the Kanban board to the developers as opposed to management
Why is one lightbulb in a string illuminated?
Selecting user stories during sprint planning
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How can I manage team distractions like chit-chat?In Scrum, what should we do with partly-completed work started at the end of a Sprint?How does the team deliver consistent velocity when user stories are de-scoped mid-way through a sprint?Why does our Sprint Planning not align with our original Release Plan?Do user stories mean rework? How much is ok?How to address delivery of production fixes in scrum?How to deal with tasks detalization in sprint planning?Should a technical person take part of the user stories prioritization process?What should we do if there are not enough PBIs to fill a final Sprint in Scrum?Agile user story's task estimationVelocity calculation based on number of user stories completed in a sprintNeed help for sprint planning when tasks are not done in previous sprint
When selecting user stories from the prioritized product backlog during sprint planning, is it more important to make sure that we end up with our predicted velocity in story points or that we choose the most important user stories?
Consider the following example:
The team feels comfortable committing to 9 story points this iteration.
These are the stories at the top of our product backlog (from most important to least important)
- User Story A - 4 story points
- User Story B - 2 story points
- User Story C - 1 story point
- User Story D - 3 story points
Is it better to choose A, B and C (7 story points, based on priority) or should we choose A, B and D (9 story points, based on predicted velocity)?
scrum sprint-planning
edited Apr 18 at 12:40
Glorfindel
143119
asked Apr 18 at 7:55
LukasLukas
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
When selecting user stories from the prioritized product backlog during sprint planning, is it more important to make sure that we end up with our predicted velocity in story points or that we choose the most important user stories?
Consider the following example:
The team feels comfortable committing to 9 story points this iteration.
These are the stories at the top of our product backlog (from most important to least important)
- User Story A - 4 story points
- User Story B - 2 story points
- User Story C - 1 story point
- User Story D - 3 story points
Is it better to choose A, B and C (7 story points, based on priority) or should we choose A, B and D (9 story points, based on predicted velocity)?
scrum sprint-planning
edited Apr 18 at 12:40
Glorfindel
143119
asked Apr 18 at 7:55
LukasLukas
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Please correct the typo in the title :-o spring -> sprint
– Falco
Apr 18 at 12:16
add a comment |
When selecting user stories from the prioritized product backlog during sprint planning, is it more important to make sure that we end up with our predicted velocity in story points or that we choose the most important user stories?
Consider the following example:
The team feels comfortable committing to 9 story points this iteration.
These are the stories at the top of our product backlog (from most important to least important)
- User Story A - 4 story points
- User Story B - 2 story points
- User Story C - 1 story point
- User Story D - 3 story points
Is it better to choose A, B and C (7 story points, based on priority) or should we choose A, B and D (9 story points, based on predicted velocity)?
scrum sprint-planning
edited Apr 18 at 12:40
Glorfindel
143119
asked Apr 18 at 7:55
LukasLukas
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
When selecting user stories from the prioritized product backlog during sprint planning, is it more important to make sure that we end up with our predicted velocity in story points or that we choose the most important user stories?
Consider the following example:
The team feels comfortable committing to 9 story points this iteration.
These are the stories at the top of our product backlog (from most important to least important)
- User Story A - 4 story points
- User Story B - 2 story points
- User Story C - 1 story point
- User Story D - 3 story points
Is it better to choose A, B and C (7 story points, based on priority) or should we choose A, B and D (9 story points, based on predicted velocity)?
scrum sprint-planning
scrum sprint-planning
edited Apr 18 at 12:40
Glorfindel
143119
asked Apr 18 at 7:55
LukasLukas
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 18 at 12:40
Glorfindel
143119
asked Apr 18 at 7:55
LukasLukas
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 18 at 12:40
Glorfindel
143119
edited Apr 18 at 12:40
Glorfindel
143119
edited Apr 18 at 12:40
Glorfindel
143119
143119
asked Apr 18 at 7:55
LukasLukas
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 18 at 7:55
LukasLukas
535
asked Apr 18 at 7:55
LukasLukas
535
535
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Lukas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Please correct the typo in the title :-o spring -> sprint
– Falco
Apr 18 at 12:16
add a comment |
Please correct the typo in the title :-o spring -> sprint
– Falco
Apr 18 at 12:16
Please correct the typo in the title :-o spring -> sprint
– Falco
Apr 18 at 12:16
Please correct the typo in the title :-o spring -> sprint
– Falco
Apr 18 at 12:16
add a comment |
3 Answers
3
active
oldest
votes
This is a really good question, but there is no definitive answer.
Have the conversation with your Product Owner. Explain to them the situation and offer them a choice.
The Product Owner may say that the difference in importance between Story C and Story D is not significant, so they are happy for you to swap them around for this sprint.
Alternatively, they may say that getting Story C done in this sprint is really important to them.
It may also be worth analysing Story D to see if it can be broken down in to smaller stories.
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
add a comment |
I really liked Todd's explanantion on how to deal with such situations:
Focus on Sprint Goal, instead of specific Stories.
When prioritising these stories, some will fit better to a concept of a single goal than others. So, instead of focusing on priority or velocity, focus on Sprint Goal. Ok, it's kinda the same as focus on priority.
Besides, avoid the 100% utilization fallacy. It's more important to deliver value (through the Sprint Goal or prioritisation) than trying to use every Story Point available for the sake of Velocity.
Your goal is not to go faster. Is to deliver more value.
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
add a comment |
First of all, it is a good practice to have the SP estimated following the Fibonnacci sequence, where 4 it is not possible.
To answer your question: The Scrum guide specifies that is the Product Owner who will choose the Product Backlog items that should be done during the sprint:
The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.
So in that case it is the Product Owner who has to decide that, where probably in your example could decide to do in this Sprint the User Stories 1, 2, 3 and leave 4 as a challenge US where you do not have engagement.
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "208"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Lukas is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f26235%2fselecting-user-stories-during-sprint-planning%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a really good question, but there is no definitive answer.
Have the conversation with your Product Owner. Explain to them the situation and offer them a choice.
The Product Owner may say that the difference in importance between Story C and Story D is not significant, so they are happy for you to swap them around for this sprint.
Alternatively, they may say that getting Story C done in this sprint is really important to them.
It may also be worth analysing Story D to see if it can be broken down in to smaller stories.
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
add a comment |
This is a really good question, but there is no definitive answer.
Have the conversation with your Product Owner. Explain to them the situation and offer them a choice.
The Product Owner may say that the difference in importance between Story C and Story D is not significant, so they are happy for you to swap them around for this sprint.
Alternatively, they may say that getting Story C done in this sprint is really important to them.
It may also be worth analysing Story D to see if it can be broken down in to smaller stories.
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
add a comment |
This is a really good question, but there is no definitive answer.
Have the conversation with your Product Owner. Explain to them the situation and offer them a choice.
The Product Owner may say that the difference in importance between Story C and Story D is not significant, so they are happy for you to swap them around for this sprint.
Alternatively, they may say that getting Story C done in this sprint is really important to them.
It may also be worth analysing Story D to see if it can be broken down in to smaller stories.
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
This is a really good question, but there is no definitive answer.
Have the conversation with your Product Owner. Explain to them the situation and offer them a choice.
The Product Owner may say that the difference in importance between Story C and Story D is not significant, so they are happy for you to swap them around for this sprint.
Alternatively, they may say that getting Story C done in this sprint is really important to them.
It may also be worth analysing Story D to see if it can be broken down in to smaller stories.
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
answered Apr 18 at 9:05
Barnaby GoldenBarnaby Golden
9,6301825
9,6301825
add a comment |
add a comment |
I really liked Todd's explanantion on how to deal with such situations:
Focus on Sprint Goal, instead of specific Stories.
When prioritising these stories, some will fit better to a concept of a single goal than others. So, instead of focusing on priority or velocity, focus on Sprint Goal. Ok, it's kinda the same as focus on priority.
Besides, avoid the 100% utilization fallacy. It's more important to deliver value (through the Sprint Goal or prioritisation) than trying to use every Story Point available for the sake of Velocity.
Your goal is not to go faster. Is to deliver more value.
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
add a comment |
I really liked Todd's explanantion on how to deal with such situations:
Focus on Sprint Goal, instead of specific Stories.
When prioritising these stories, some will fit better to a concept of a single goal than others. So, instead of focusing on priority or velocity, focus on Sprint Goal. Ok, it's kinda the same as focus on priority.
Besides, avoid the 100% utilization fallacy. It's more important to deliver value (through the Sprint Goal or prioritisation) than trying to use every Story Point available for the sake of Velocity.
Your goal is not to go faster. Is to deliver more value.
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
add a comment |
I really liked Todd's explanantion on how to deal with such situations:
Focus on Sprint Goal, instead of specific Stories.
When prioritising these stories, some will fit better to a concept of a single goal than others. So, instead of focusing on priority or velocity, focus on Sprint Goal. Ok, it's kinda the same as focus on priority.
Besides, avoid the 100% utilization fallacy. It's more important to deliver value (through the Sprint Goal or prioritisation) than trying to use every Story Point available for the sake of Velocity.
Your goal is not to go faster. Is to deliver more value.
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
I really liked Todd's explanantion on how to deal with such situations:
Focus on Sprint Goal, instead of specific Stories.
When prioritising these stories, some will fit better to a concept of a single goal than others. So, instead of focusing on priority or velocity, focus on Sprint Goal. Ok, it's kinda the same as focus on priority.
Besides, avoid the 100% utilization fallacy. It's more important to deliver value (through the Sprint Goal or prioritisation) than trying to use every Story Point available for the sake of Velocity.
Your goal is not to go faster. Is to deliver more value.
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
answered Apr 18 at 9:19
Tiago Cardoso♦Tiago Cardoso
5,80941854
5,80941854
add a comment |
add a comment |
First of all, it is a good practice to have the SP estimated following the Fibonnacci sequence, where 4 it is not possible.
To answer your question: The Scrum guide specifies that is the Product Owner who will choose the Product Backlog items that should be done during the sprint:
The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.
So in that case it is the Product Owner who has to decide that, where probably in your example could decide to do in this Sprint the User Stories 1, 2, 3 and leave 4 as a challenge US where you do not have engagement.
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
add a comment |
First of all, it is a good practice to have the SP estimated following the Fibonnacci sequence, where 4 it is not possible.
To answer your question: The Scrum guide specifies that is the Product Owner who will choose the Product Backlog items that should be done during the sprint:
The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.
So in that case it is the Product Owner who has to decide that, where probably in your example could decide to do in this Sprint the User Stories 1, 2, 3 and leave 4 as a challenge US where you do not have engagement.
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
add a comment |
First of all, it is a good practice to have the SP estimated following the Fibonnacci sequence, where 4 it is not possible.
To answer your question: The Scrum guide specifies that is the Product Owner who will choose the Product Backlog items that should be done during the sprint:
The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.
So in that case it is the Product Owner who has to decide that, where probably in your example could decide to do in this Sprint the User Stories 1, 2, 3 and leave 4 as a challenge US where you do not have engagement.
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
First of all, it is a good practice to have the SP estimated following the Fibonnacci sequence, where 4 it is not possible.
To answer your question: The Scrum guide specifies that is the Product Owner who will choose the Product Backlog items that should be done during the sprint:
The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.
So in that case it is the Product Owner who has to decide that, where probably in your example could decide to do in this Sprint the User Stories 1, 2, 3 and leave 4 as a challenge US where you do not have engagement.
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
answered Apr 18 at 14:50
Alex BlascoAlex Blasco
14711
14711
add a comment |
add a comment |
Lukas is a new contributor. Be nice, and check out our Code of Conduct.
Lukas is a new contributor. Be nice, and check out our Code of Conduct.
Lukas is a new contributor. Be nice, and check out our Code of Conduct.
Lukas is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Project Management Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f26235%2fselecting-user-stories-during-sprint-planning%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please correct the typo in the title :-o spring -> sprint
– Falco
Apr 18 at 12:16