Sprint is 2 week and 40-stories
Clash Royale CLAN TAG#URR8PPP
Question for QA- What you are doing if your current sprint is 2 week and you have 20 stories, suddenly PO added more 20 stories how you handle this situation..?
agile sprint quality-management agile-coach sprint-review
asked Feb 26 at 8:04
user28692user28692
463
add a comment |
Question for QA- What you are doing if your current sprint is 2 week and you have 20 stories, suddenly PO added more 20 stories how you handle this situation..?
agile sprint quality-management agile-coach sprint-review
asked Feb 26 at 8:04
user28692user28692
463
6
If the Product Owner is assigning stories to the Development Team or directly adding stories the Sprint Backlog, then whatever you're doing is not Scrum.
– Todd A. Jacobs♦
Feb 26 at 14:51
add a comment |
Question for QA- What you are doing if your current sprint is 2 week and you have 20 stories, suddenly PO added more 20 stories how you handle this situation..?
agile sprint quality-management agile-coach sprint-review
asked Feb 26 at 8:04
user28692user28692
463
Question for QA- What you are doing if your current sprint is 2 week and you have 20 stories, suddenly PO added more 20 stories how you handle this situation..?
agile sprint quality-management agile-coach sprint-review
agile sprint quality-management agile-coach sprint-review
asked Feb 26 at 8:04
user28692user28692
463
asked Feb 26 at 8:04
user28692user28692
463
asked Feb 26 at 8:04
user28692user28692
463
asked Feb 26 at 8:04
user28692user28692
463
asked Feb 26 at 8:04
user28692user28692
463
463
6
If the Product Owner is assigning stories to the Development Team or directly adding stories the Sprint Backlog, then whatever you're doing is not Scrum.
– Todd A. Jacobs♦
Feb 26 at 14:51
add a comment |
6
If the Product Owner is assigning stories to the Development Team or directly adding stories the Sprint Backlog, then whatever you're doing is not Scrum.
– Todd A. Jacobs♦
Feb 26 at 14:51
6
6
If the Product Owner is assigning stories to the Development Team or directly adding stories the Sprint Backlog, then whatever you're doing is not Scrum.
– Todd A. Jacobs♦
Feb 26 at 14:51
If the Product Owner is assigning stories to the Development Team or directly adding stories the Sprint Backlog, then whatever you're doing is not Scrum.
– Todd A. Jacobs♦
Feb 26 at 14:51
add a comment |
2 Answers
2
active
oldest
votes
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation between the Product Owner and Development Team while considering past performance and forecast capacity, is owned exclusively by the Development Team.
If work comes in and it is a higher priority, there needs to be a discussion between the Product Owner and the Development Team on how to adjust the Sprint to balance the higher priority work with the remaining time and capacity of the Development Team. If the Sprint Goal is obsolete and the work that the team has been working on is no longer relevant or valuable, cancelling the Sprint is an option. If there are multiple Scrum Teams involved, dependencies must also be considered. The Scrum Master can facilitate any discussions or decisions made, including escalation beyond the Scrum Team if necessary.
Going back to the Scrum Values, the Development Team needs to have the courage and openness to push back against the Product Owner and protect their time. Going back all the way to the principles behind the Manifesto for Agile Software Development, development needs to be sustainable and done with a pace that can be held indefinitely, with continuous attention to technical excellence. Overloading Sprints or forcing the team is not collaborative and introduces a lot of risk and pain to an effort.
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
add a comment |
is the 20 old stories represent a release? if yes there is a real problem at the business vision, where that the 20+ stories will completely lead to another product and how these extra stories were added it should be a collaborative process (PO with team), you have to re-estimate the stories, re-planning the release and the iteration, some people make the iteration time dynamic so you can extend it from 2 up to 4 weeks according to the PO business values
in Scrum it is so important that all team members sit with PO in "Stories workshop" with "brainstorm" term to gathering all stories as possible this lead to good estimation for release, in your situation you must collaboratively re-planning the release(story workshop then estimate then prioritize and re-set the sprint time, finally assign the user stories in iteration according to the team velocity)
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
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
);
);
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%2f25891%2fsprint-is-2-week-and-40-stories%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation between the Product Owner and Development Team while considering past performance and forecast capacity, is owned exclusively by the Development Team.
If work comes in and it is a higher priority, there needs to be a discussion between the Product Owner and the Development Team on how to adjust the Sprint to balance the higher priority work with the remaining time and capacity of the Development Team. If the Sprint Goal is obsolete and the work that the team has been working on is no longer relevant or valuable, cancelling the Sprint is an option. If there are multiple Scrum Teams involved, dependencies must also be considered. The Scrum Master can facilitate any discussions or decisions made, including escalation beyond the Scrum Team if necessary.
Going back to the Scrum Values, the Development Team needs to have the courage and openness to push back against the Product Owner and protect their time. Going back all the way to the principles behind the Manifesto for Agile Software Development, development needs to be sustainable and done with a pace that can be held indefinitely, with continuous attention to technical excellence. Overloading Sprints or forcing the team is not collaborative and introduces a lot of risk and pain to an effort.
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
add a comment |
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation between the Product Owner and Development Team while considering past performance and forecast capacity, is owned exclusively by the Development Team.
If work comes in and it is a higher priority, there needs to be a discussion between the Product Owner and the Development Team on how to adjust the Sprint to balance the higher priority work with the remaining time and capacity of the Development Team. If the Sprint Goal is obsolete and the work that the team has been working on is no longer relevant or valuable, cancelling the Sprint is an option. If there are multiple Scrum Teams involved, dependencies must also be considered. The Scrum Master can facilitate any discussions or decisions made, including escalation beyond the Scrum Team if necessary.
Going back to the Scrum Values, the Development Team needs to have the courage and openness to push back against the Product Owner and protect their time. Going back all the way to the principles behind the Manifesto for Agile Software Development, development needs to be sustainable and done with a pace that can be held indefinitely, with continuous attention to technical excellence. Overloading Sprints or forcing the team is not collaborative and introduces a lot of risk and pain to an effort.
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
add a comment |
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation between the Product Owner and Development Team while considering past performance and forecast capacity, is owned exclusively by the Development Team.
If work comes in and it is a higher priority, there needs to be a discussion between the Product Owner and the Development Team on how to adjust the Sprint to balance the higher priority work with the remaining time and capacity of the Development Team. If the Sprint Goal is obsolete and the work that the team has been working on is no longer relevant or valuable, cancelling the Sprint is an option. If there are multiple Scrum Teams involved, dependencies must also be considered. The Scrum Master can facilitate any discussions or decisions made, including escalation beyond the Scrum Team if necessary.
Going back to the Scrum Values, the Development Team needs to have the courage and openness to push back against the Product Owner and protect their time. Going back all the way to the principles behind the Manifesto for Agile Software Development, development needs to be sustainable and done with a pace that can be held indefinitely, with continuous attention to technical excellence. Overloading Sprints or forcing the team is not collaborative and introduces a lot of risk and pain to an effort.
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation between the Product Owner and Development Team while considering past performance and forecast capacity, is owned exclusively by the Development Team.
If work comes in and it is a higher priority, there needs to be a discussion between the Product Owner and the Development Team on how to adjust the Sprint to balance the higher priority work with the remaining time and capacity of the Development Team. If the Sprint Goal is obsolete and the work that the team has been working on is no longer relevant or valuable, cancelling the Sprint is an option. If there are multiple Scrum Teams involved, dependencies must also be considered. The Scrum Master can facilitate any discussions or decisions made, including escalation beyond the Scrum Team if necessary.
Going back to the Scrum Values, the Development Team needs to have the courage and openness to push back against the Product Owner and protect their time. Going back all the way to the principles behind the Manifesto for Agile Software Development, development needs to be sustainable and done with a pace that can be held indefinitely, with continuous attention to technical excellence. Overloading Sprints or forcing the team is not collaborative and introduces a lot of risk and pain to an effort.
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
answered Feb 26 at 11:02
Thomas OwensThomas Owens
5,0761428
5,0761428
add a comment |
add a comment |
is the 20 old stories represent a release? if yes there is a real problem at the business vision, where that the 20+ stories will completely lead to another product and how these extra stories were added it should be a collaborative process (PO with team), you have to re-estimate the stories, re-planning the release and the iteration, some people make the iteration time dynamic so you can extend it from 2 up to 4 weeks according to the PO business values
in Scrum it is so important that all team members sit with PO in "Stories workshop" with "brainstorm" term to gathering all stories as possible this lead to good estimation for release, in your situation you must collaboratively re-planning the release(story workshop then estimate then prioritize and re-set the sprint time, finally assign the user stories in iteration according to the team velocity)
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
add a comment |
is the 20 old stories represent a release? if yes there is a real problem at the business vision, where that the 20+ stories will completely lead to another product and how these extra stories were added it should be a collaborative process (PO with team), you have to re-estimate the stories, re-planning the release and the iteration, some people make the iteration time dynamic so you can extend it from 2 up to 4 weeks according to the PO business values
in Scrum it is so important that all team members sit with PO in "Stories workshop" with "brainstorm" term to gathering all stories as possible this lead to good estimation for release, in your situation you must collaboratively re-planning the release(story workshop then estimate then prioritize and re-set the sprint time, finally assign the user stories in iteration according to the team velocity)
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
add a comment |
is the 20 old stories represent a release? if yes there is a real problem at the business vision, where that the 20+ stories will completely lead to another product and how these extra stories were added it should be a collaborative process (PO with team), you have to re-estimate the stories, re-planning the release and the iteration, some people make the iteration time dynamic so you can extend it from 2 up to 4 weeks according to the PO business values
in Scrum it is so important that all team members sit with PO in "Stories workshop" with "brainstorm" term to gathering all stories as possible this lead to good estimation for release, in your situation you must collaboratively re-planning the release(story workshop then estimate then prioritize and re-set the sprint time, finally assign the user stories in iteration according to the team velocity)
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
is the 20 old stories represent a release? if yes there is a real problem at the business vision, where that the 20+ stories will completely lead to another product and how these extra stories were added it should be a collaborative process (PO with team), you have to re-estimate the stories, re-planning the release and the iteration, some people make the iteration time dynamic so you can extend it from 2 up to 4 weeks according to the PO business values
in Scrum it is so important that all team members sit with PO in "Stories workshop" with "brainstorm" term to gathering all stories as possible this lead to good estimation for release, in your situation you must collaboratively re-planning the release(story workshop then estimate then prioritize and re-set the sprint time, finally assign the user stories in iteration according to the team velocity)
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
answered Feb 26 at 14:36
Mjd KassemMjd Kassem
638
638
add a comment |
add a comment |
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%2f25891%2fsprint-is-2-week-and-40-stories%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
6
If the Product Owner is assigning stories to the Development Team or directly adding stories the Sprint Backlog, then whatever you're doing is not Scrum.
– Todd A. Jacobs♦
Feb 26 at 14:51