Difference between sprint backlog and sprint goal?How can I improve measurement of Sprint Goals that are based on soft skills or communication processes?What should Scrum Master do if Scrum Team hasn't reached an event goal after time-box expires?What does it mean that a Sprint Goal can be any other coherence?What is a good total size for a Product Backlog?Applying agile in a mostly operations/support environmentIn scrum should incomplete stories be re-estimated or does the original estimate get burned down when it's finally completed?Ineffective Backlog Grooming and Sprint PlanningHow can we fix Sprint Planning meetings that are unproductive?Scrum: is it ok to make developer responsible for one of sprint goals?Should we add more items to sprint backlog if there is items that are not completed
New order #4: World
What do you call a Matrix-like slowdown and camera movement effect?
Can I interfere when another PC is about to be attacked?
Is it possible to make sharp wind that can cut stuff from afar?
What is the offset in a seaplane's hull?
How is it possible to have an ability score that is less than 3?
What is the command to reset a PC without deleting any files
I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine
A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?
Is there really no realistic way for a skeleton monster to move around without magic?
"which" command doesn't work / path of Safari?
How is this relation reflexive?
What is the logic behind how bash tests for true/false?
How to add power-LED to my small amplifier?
Possibly bubble sort algorithm
Copenhagen passport control - US citizen
Patience, young "Padovan"
A Journey Through Space and Time
Pronouncing Dictionary.com's W.O.D "vade mecum" in English
Draw simple lines in Inkscape
I see my dog run
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
How old can references or sources in a thesis be?
How long does it take to type this?
Difference between sprint backlog and sprint goal?
How can I improve measurement of Sprint Goals that are based on soft skills or communication processes?What should Scrum Master do if Scrum Team hasn't reached an event goal after time-box expires?What does it mean that a Sprint Goal can be any other coherence?What is a good total size for a Product Backlog?Applying agile in a mostly operations/support environmentIn scrum should incomplete stories be re-estimated or does the original estimate get burned down when it's finally completed?Ineffective Backlog Grooming and Sprint PlanningHow can we fix Sprint Planning meetings that are unproductive?Scrum: is it ok to make developer responsible for one of sprint goals?Should we add more items to sprint backlog if there is items that are not completed
One of the questions while PSM I™ Preparation Quiz which I was unable to digest was,
What provides guidance to the Development Team on why it is building
the Increment?
- The Sprint Backlog
- The Product Owner
- The Sprint Goal
- The Scrum Master
For this I selected the "The sprint backlog" as appropriate answer but it turned out wrong. Correct answer is "The Sprint Goal" with the explanation as
"The Sprint Goal is an objective set for the Sprint that can be met through
the implementation of Product Backlog.
It provides guidance to the Development Team on why it
is building the Increment."
My question over here is what is the difference between Sprint Backlog and Sprint Goal?
I have tried googling around to understand this but I was unable to get to any conclusion. Please suggest!
scrum
add a comment |
One of the questions while PSM I™ Preparation Quiz which I was unable to digest was,
What provides guidance to the Development Team on why it is building
the Increment?
- The Sprint Backlog
- The Product Owner
- The Sprint Goal
- The Scrum Master
For this I selected the "The sprint backlog" as appropriate answer but it turned out wrong. Correct answer is "The Sprint Goal" with the explanation as
"The Sprint Goal is an objective set for the Sprint that can be met through
the implementation of Product Backlog.
It provides guidance to the Development Team on why it
is building the Increment."
My question over here is what is the difference between Sprint Backlog and Sprint Goal?
I have tried googling around to understand this but I was unable to get to any conclusion. Please suggest!
scrum
add a comment |
One of the questions while PSM I™ Preparation Quiz which I was unable to digest was,
What provides guidance to the Development Team on why it is building
the Increment?
- The Sprint Backlog
- The Product Owner
- The Sprint Goal
- The Scrum Master
For this I selected the "The sprint backlog" as appropriate answer but it turned out wrong. Correct answer is "The Sprint Goal" with the explanation as
"The Sprint Goal is an objective set for the Sprint that can be met through
the implementation of Product Backlog.
It provides guidance to the Development Team on why it
is building the Increment."
My question over here is what is the difference between Sprint Backlog and Sprint Goal?
I have tried googling around to understand this but I was unable to get to any conclusion. Please suggest!
scrum
One of the questions while PSM I™ Preparation Quiz which I was unable to digest was,
What provides guidance to the Development Team on why it is building
the Increment?
- The Sprint Backlog
- The Product Owner
- The Sprint Goal
- The Scrum Master
For this I selected the "The sprint backlog" as appropriate answer but it turned out wrong. Correct answer is "The Sprint Goal" with the explanation as
"The Sprint Goal is an objective set for the Sprint that can be met through
the implementation of Product Backlog.
It provides guidance to the Development Team on why it
is building the Increment."
My question over here is what is the difference between Sprint Backlog and Sprint Goal?
I have tried googling around to understand this but I was unable to get to any conclusion. Please suggest!
scrum
scrum
asked Apr 4 at 9:55
ShubhShubh
1314
1314
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Great question! It sounds like you may already know this, but for anyone else, the Scrum Guide says this about Topic 1 in Sprint planning:
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The
Sprint Goal is an objective that will be met within the Sprint through
the implementation of the Product Backlog, and it provides guidance to
the Development Team on why it is building the Increment.
A sprint goal might be something like:
A user will be able to see a list of recent transactions on their
account and search that list.
Then the team brings the backlog items in that fulfill that goal. Many teams pull in a number of backlog items that may or may not have some coherent theme and then set the goal of finishing the work. The difference between these two approaches is subtle, but it comes down to outcome vs output. The first one focuses on creating an outcome for end users. The second one focuses on output (work being done rather than value being delivered).
Something else interesting about this sort of sprint goal is that it is in some times possible to deliver the sprint goal without delivering all of the backlog items. This is a little unintuitive, but when things don't go as planned in a sprint, a great team can rally around the sprint goal to find a new way to reach it.
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%2f26128%2fdifference-between-sprint-backlog-and-sprint-goal%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Great question! It sounds like you may already know this, but for anyone else, the Scrum Guide says this about Topic 1 in Sprint planning:
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The
Sprint Goal is an objective that will be met within the Sprint through
the implementation of the Product Backlog, and it provides guidance to
the Development Team on why it is building the Increment.
A sprint goal might be something like:
A user will be able to see a list of recent transactions on their
account and search that list.
Then the team brings the backlog items in that fulfill that goal. Many teams pull in a number of backlog items that may or may not have some coherent theme and then set the goal of finishing the work. The difference between these two approaches is subtle, but it comes down to outcome vs output. The first one focuses on creating an outcome for end users. The second one focuses on output (work being done rather than value being delivered).
Something else interesting about this sort of sprint goal is that it is in some times possible to deliver the sprint goal without delivering all of the backlog items. This is a little unintuitive, but when things don't go as planned in a sprint, a great team can rally around the sprint goal to find a new way to reach it.
add a comment |
Great question! It sounds like you may already know this, but for anyone else, the Scrum Guide says this about Topic 1 in Sprint planning:
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The
Sprint Goal is an objective that will be met within the Sprint through
the implementation of the Product Backlog, and it provides guidance to
the Development Team on why it is building the Increment.
A sprint goal might be something like:
A user will be able to see a list of recent transactions on their
account and search that list.
Then the team brings the backlog items in that fulfill that goal. Many teams pull in a number of backlog items that may or may not have some coherent theme and then set the goal of finishing the work. The difference between these two approaches is subtle, but it comes down to outcome vs output. The first one focuses on creating an outcome for end users. The second one focuses on output (work being done rather than value being delivered).
Something else interesting about this sort of sprint goal is that it is in some times possible to deliver the sprint goal without delivering all of the backlog items. This is a little unintuitive, but when things don't go as planned in a sprint, a great team can rally around the sprint goal to find a new way to reach it.
add a comment |
Great question! It sounds like you may already know this, but for anyone else, the Scrum Guide says this about Topic 1 in Sprint planning:
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The
Sprint Goal is an objective that will be met within the Sprint through
the implementation of the Product Backlog, and it provides guidance to
the Development Team on why it is building the Increment.
A sprint goal might be something like:
A user will be able to see a list of recent transactions on their
account and search that list.
Then the team brings the backlog items in that fulfill that goal. Many teams pull in a number of backlog items that may or may not have some coherent theme and then set the goal of finishing the work. The difference between these two approaches is subtle, but it comes down to outcome vs output. The first one focuses on creating an outcome for end users. The second one focuses on output (work being done rather than value being delivered).
Something else interesting about this sort of sprint goal is that it is in some times possible to deliver the sprint goal without delivering all of the backlog items. This is a little unintuitive, but when things don't go as planned in a sprint, a great team can rally around the sprint goal to find a new way to reach it.
Great question! It sounds like you may already know this, but for anyone else, the Scrum Guide says this about Topic 1 in Sprint planning:
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The
Sprint Goal is an objective that will be met within the Sprint through
the implementation of the Product Backlog, and it provides guidance to
the Development Team on why it is building the Increment.
A sprint goal might be something like:
A user will be able to see a list of recent transactions on their
account and search that list.
Then the team brings the backlog items in that fulfill that goal. Many teams pull in a number of backlog items that may or may not have some coherent theme and then set the goal of finishing the work. The difference between these two approaches is subtle, but it comes down to outcome vs output. The first one focuses on creating an outcome for end users. The second one focuses on output (work being done rather than value being delivered).
Something else interesting about this sort of sprint goal is that it is in some times possible to deliver the sprint goal without delivering all of the backlog items. This is a little unintuitive, but when things don't go as planned in a sprint, a great team can rally around the sprint goal to find a new way to reach it.
answered Apr 4 at 10:39
DanielDaniel
9,53821327
9,53821327
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%2f26128%2fdifference-between-sprint-backlog-and-sprint-goal%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