Remove sprint-backlogs
article thumbnail

How self-management is supported by a transparent Sprint Backlog (51)

Scrum.org

In the past series of blog posts we covered the three pillars of Empiricism, and we covered the Scrum Values. Let’s take a look at the Sprint Backlog. The Sprint Backlog includes the Sprint Goal. This is the objective for the current Sprint. And so the Sprint Backlog supports deciding on what.

SCRUM 168
article thumbnail

Product Backlog and Sprint Backlog: A Quick Guide

ProjectManager.com

Two such potentially confusing terms are product backlog and sprint backlog, both of which are essential for planning and prioritizing tasks in a project. What is a Product Backlog? The product backlog is compiled of all the things that must be done to complete the whole project. What is a Sprint Backlog?

SCRUM 360
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Product Backlog vs. Sprint Backlog: What are the Differences?

Inloox

In this blog post, we want to clear up any misunderstandings around Scrum. One of the most common sources for confusion, which probably still leads to a lot of misunderstandings in agile teams on a daily basis, is the distinction between Product backlog and sprint backlog. What is a product backlog?

SCRUM 176
article thumbnail

How the Sprint Backlog Supports Adaptation (29)

Scrum.org

This also applies for the Sprint Backlog. The Sprint Backlog is typically adapted during Sprint Planning and during the Daily Scrum. etc. Each time new insights are gained about the progress towards the Sprint Goal, the Developers do make the necessary adaptations.

SCRUM 151
article thumbnail

How living the Scrum Values improves your Sprint Backlog (40)

Scrum.org

For the Sprint Backlog this comm itment is the Sprint Goal. This implies that the Scrum Team Commits to put their efforts in the Sprint Backlog so that all Developers have the same understanding when looking at the Sprint Backlog, and that this transparency allows them to measure progress towards the Sprint Goal.

SCRUM 165
article thumbnail

How are Done and your Sprint Backlog related? ?? (73)

Scrum.org

So how does the Sprint Backlog support the concept of getting to a Done Increment at least by the end of every Sprint? Remember that the purpose of the Sprint Backlog is to bring transparency on the work the Developers still plan to accomplish in order to achieve the Sprint Goal in the next Increment.

SCRUM 199
article thumbnail

The importance of Transparency and the Sprint Backlog (07)

Scrum.org

Let’s take the Sprint Backlog. Why are we even doing this Sprint? Understanding the goal for a Sprint allows the team to take ownership. What Product Backlog Items are selected for this Sprint? Then here you go, bring more transparency though your Sprint Backlog. Through your Sprint Backlog.

SCRUM 170