DefinitionA sprint backlog is the subset of product backlog that a team targets to deliver during a sprint in order to accomplish the sprint goal and make progress toward a desired outcome. The sprint backlog consists of product backlog items that the team agreed with their product owner to include during
sprint planning. The team owns the sprint backlog and can determine whether new items are added or existing items are removed. This allows the team to focus on a clear scope for the length of the sprint. Some teams may allow the inclusion of a new product backlog item if it replaces a product backlog item of equal or greater size that already exists on the sprint backlog. If a team identifies tasks needed
to deliver the select product backlog item, those tasks also become part of the sprint backlog. The team can add or remove tasks to the sprint backlog throughout the course of the sprint. The sprint backlog also includes any action items the team identified from the previous retrospective meeting. The sprint backlog is generally tracked on an information radiator to provide a visual signal of the progress of the team as well as indicate the scope of the current sprint. If the team does not
identify tasks, the product backlog items are tracked through different stages of the workflow in a format sometimes referred to as a delivery board. If the team breaks their product backlog items into tasks, they will often use a task board to track those tasks. The majority of product backlog items included on a sprint backlog are
user stories that are appropriately described according to the team’s definition of ready. Other product backlog items could represent bugs that need to be addressed, research that needs to be done (typically in the form of spikes), or changes needed to the products architecture or infrastructure. The sprint backlog only lasts for the duration of a sprint. Each new sprint starts with a new sprint backlog,
although the team may choose to add items from the previous sprint’s sprint backlog to the new sprint backlog it those items contribute to completing the new sprint’s sprint goal.
Also Known AsIteration backlog
Expected BenefitsA sprint backlog provides a team with a clear focus for the short term while a dynamic product backlog provides a mechanism for the team to collect and remember ideas for future consideration. Keeping a stable list of product backlog
items in a sprint backlog protects the team from changing priorities and interrupts, at least for a short (usually 2 week) period. Keeping the sprint backlog visible and showing the progress of items provides the team a way of communicating status without the extra work of creating burndown or burnup charts. A visual representation of the sprint backlog also provides a helpful visual aids for team
discussions around current work and what to do next. The ability to add tasks throughout the course of a sprint allows a team to learn and adjust their plan for delivering their select product backlog items.
Common PitfallsTeams can become overly fixated, usually due to outside pressure to complete every item on the sprint backlog at all costs based on the concept that an item placed on the sprint backlog is a commitment to get that item done. The standard of success for
a sprint should be whether the team accomplishes the sprint goal. The sprint backlog may need to change through the course of the sprint based on what the team learns as they start working through the sprint backlog.
When ApplicableThe sprint backlog is applicable when a team is using Scrum and working in timeboxed sprints. If a team is working in a flow approach (such as Kanban) a sprint backlog is
not necessary.
Further ReadingSprint Backlog Scrum Guide
The three pillars of empirical process control are: A) Respect For People, Kaizen, Eliminating Waste
B) Planning, Demonstration, Retrospective
C) Inspection, Transparency, Adaptation
D) Planning, Inspection, Adaptation
E) Transparency, Eliminating Waste, Kaizen Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience
and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.**The three pillars of empirical process control are: A) Respect For People, Kaizen, Eliminating Waste
B) Planning, Demonstration, Retrospective
C) Inspection, Transparency, Adaptation
D) Planning, Inspection, Adaptation
E) Transparency, Eliminating Waste, Kaizen C
This is how it
works: When you first add the items in the Product Backlog, you don't have to break them down into very small and clear items, because it's a form of upfront planning. Some of them may be very large. When you order the items, if they are at the top of the list, you have to make them clear, and make sure they can fit into one Sprint; therefore, you will break them down into smaller items. Some of those child items may remain at the top, and some may go down. Nevertheless, because of this way of
refining, the items at the top of the Product Backlog are on average smaller than those at the bottom. On the other hand, items in the Sprint Backlog come from the top of the Product Backlog, therefore, we can say that the items in the Sprint Backlog are, on average, smaller than items on the Product Backlog. D
Recently, Scrum.org considered ordering based on value, priority, risks, and dependencies. However, if you don't have such a choice, the next best
answer (the old-fashioned one) is "based on value".
Note: priority is different from order; it's something like "high, medium, low", or "must-have, should-have, could-have". B
This is how it works: When you first add the items in the Product Backlog, you don't have to break them down into very small and clear items, because it's a form of upfront planning. Some of them may be very large. When you order the items, if they are at the top of the list, you
have to make them clear, and make sure they can fit into one Sprint; therefore, you will break them down into smaller items. Some of those child items may remain at the top, and some may go down. Nevertheless, because of this way of refining, the items at the top of the Product Backlog are on average smaller than those at the bottom. On the other hand, items in the Sprint Backlog come from the top of the Product Backlog, therefore, we can say that the items in the Sprint Backlog are, on average,
smaller than items on the Product Backlog. A
Recently, Scrum.org considered ordering based on value, priority, risks, and dependencies. However, if you don't have such a choice, the next best answer (the old-fashioned one) is "based on value".
Note: priority is different from order; it's something like "high, medium, low", or "must-have, should-have, could-have". A, B, D
Scrum is a simple framework rather than a
comprehensive methodology, and it contains only the necessary minimums that you need in every project. So, instead of a normal tailoring, you will follow everything that is described in Scrum, and suit it to your project by the practices and techniques that you add; e.g. Planning Poker, Pair-Programming, and Test-Driven Development. When it comes to terminology, Scrum.org believes that it's better if you don't change them, for the reasons that you see in the answers. B
This
is how it works: When you first add the items in the Product Backlog, you don't have to break them down into very small and clear items, because it's a form of upfront planning. Some of them may be very large. When you order the items, if they are at the top of the list, you have to make them clear, and make sure they can fit into one Sprint; therefore, you will break them down into smaller items. Some of those child items may remain at the top, and some may go down. Nevertheless, because of
this way of refining, the items at the top of the Product Backlog are on average smaller than those at the bottom. On the other hand, items in the Sprint Backlog come from the top of the Product Backlog, therefore, we can say that the items in the Sprint Backlog are, on average, smaller than items on the Product Backlog. D
Recently, Scrum.org considered ordering based on value, priority, risks, and dependencies. However, if you don't have such a choice,
the next best answer (the old-fashioned one) is "based on value".
Note: priority is different from order; it's something like "high, medium, low", or "must-have, should-have, could-have". B, C, D
Scrum is a simple framework rather than a comprehensive methodology, and it contains only the necessary minimums that you need in every project. So, instead of a normal tailoring, you will follow everything that is described in Scrum, and suit it to your
project by the practices and techniques that you add; e.g. Planning Poker, Pair-Programming, and Test-Driven Development. When it comes to terminology, Scrum.org believes that it's better if you don't change them, for the reasons that you see in the answers. A
Recently, Scrum.org considered ordering based on value, priority, risks, and dependencies. However, if you don't have such a choice, the next best answer (the old-fashioned one) is "based on
value".
Note: priority is different from order; it's something like "high, medium, low", or "must-have, should-have, could-have". A, C, E
Scrum is a simple framework rather than a comprehensive methodology, and it contains only the necessary minimums that you need in every project. So, instead of a normal tailoring, you will follow everything that is described in Scrum, and suit it to your project by the practices and techniques that you add; e.g.
Planning Poker, Pair-Programming, and Test-Driven Development. When it comes to terminology, Scrum.org believes that it's better if you don't change them, for the reasons that you see in the answers. B
This is how it works: When you first add the items in the Product Backlog, you don't have to break them down into very small and clear items, because it's a form of upfront planning. Some of them may be very large. When you order the items, if they are at
the top of the list, you have to make them clear, and make sure they can fit into one Sprint; therefore, you will break them down into smaller items. Some of those child items may remain at the top, and some may go down. Nevertheless, because of this way of refining, the items at the top of the Product Backlog are on average smaller than those at the bottom. On the other hand, items in the Sprint Backlog come from the top of the Product Backlog, therefore, we can say that the items in the Sprint
Backlog are, on average, smaller than items on the Product Backlog.
What is the main purpose of sprint backlog?
The main purpose of the Sprint Backlog is to provide the Scrum Team (and other stakeholders) with full transparency of the work being done during the Sprint.
What does sprint backlog contain?
What Does a Sprint Backlog Contain? Officially, the Sprint Backlog contains a plan for the Sprint. Usually, it will contain the Product Backlog Items (PBIs) that the team forecast to complete, along with a list of prioritized tasks broken down for each PBI to execute by a team.
Is sprint backlog updated daily?
During the Scrum sprint, team members are expected to update the sprint backlog as new information is available, but minimally once per day. Many teams will do this during the daily scrum.
What is a sprint backlog in Scrum?
The Sprint Backlog is an ordered list of Product Backlog Items or Increments, preferably User or Job Stories, that will achieve the Sprint Goal and that the Team believes it can complete during the coming Sprint.
| 
