Skip to content

Exercise "Sprint Backlog"

Summary

Here you will find the definitions of the most important terms from this chapter.

Sprint Backlog

The Sprint Backlog is a list of tasks to be completed in the upcoming Sprint. It serves as the basis for the Sprint Goal, defining the central objectives of the Sprint.

Sprint Goal

In the agile Scrum framework, a Sprint Goal is defined for each Sprint during Sprint Planning, and the content of the Sprint Backlog is determined on the basis of the Sprint Goal. The Sprint Goal is formulated by the Product Owner and serves as a target for the Developers. The Sprint Goal is the Developers' commitment to the Sprint Backlog. It should be SMART and answer the question: Why are we doing this Sprint? The Sprint Goal should not be changed during the Sprint.

Daily Scrum

The Daily Scrum, also known as the Daily Stand-up Meeting, is a 15-minute daily meeting. Its goal is to review progress towards the Sprint Goal. The Daily Scrum improves communication, identifies impediments, and promotes quick decision-making.

Impediments

Impediments are barriers or disruptive factors that affect the team's performance or individual team members, questioning the achievement of the Sprint Goal.

Sprint Planning Meeting

The Sprint Planning Meeting marks the beginning of a new Sprint and is used to plan upcoming tasks. A plan is created that is supported by all team members. The duration of the meeting is proportional to the length of the Sprint.

Test yourself

Try to answer the following questions on your own. Take your time and think carefully before checking the solutions.

What question should you ask yourself when creating the Sprint Goal?

Why is this Sprint being carried out?

What happens if the Sprint Goal is not / can not be achieved?

If during the Sprint the results do not meet the Sprint Goal, the Developers can renegotiate the focus of the Sprint with the Product Owner.

Who is allowed to change the Sprint Goal during a sprint?

The Sprint Goal may not be changed by anyone during the Sprint. However, the focus of the Sprint may be changed in consultation with the Product Owner. In addition, the Product Owner can stop the Sprint if the previously set Sprint Goal has become obsolete.

What acronym should you keep in mind when creating the Sprint Goal? What does it stand for?

The Sprint Goal should be formulated "SMART". SMART stands for specific, measurable, achievable, reasonable and time-bound.

What is the Sprint Backlog?

The Sprint Backlog

  • is the list of Product Backlog Items to be processed in the current Sprint,
  • consists of entries that are taken from the Product Backlog,
  • is the description of the technical measures (tasks) for implementation and realisation (e.g. design, architecture, programming, testing and refactoring),
  • is the responsibility of the Developers, as they make a prediction of the functionalities to be developed,
  • is placed in the office for all to see. Maintenance and updating are done in a timely manner in relation to the Daily Scrum Meeting,
  • serves to visualise the progress.
Who is responsible for creating the Sprint Backlog?

The Developers are responsible for the creation and maintenance of the Sprint Backlog.

Who is allowed to make adjustments to the Sprint Backlog during the Sprint?

The Developers can make changes to the Sprint Backlog if, for example, it is determined during the Sprint that a task is more complex than estimated in advance.

What is the best way to display the Sprint Backlog, or how is it structured?

The Sprint Backlog is divided into four columns. On the far left, all User Stories that were selected in the previous Sprint Planning Meeting are listed. At the top is the User Story with the highest priority. The lower the User Stories are listed in the Sprint Backlog, the lower their priority - similar to the Product Backlog. To the right in the To-Do column you can find the tasks that are necessary for the implementation of the respective User Story into an Increment. The tasks are arranged as determined by the Developers in the Sprint Planning Meeting. The next column shows what is currently being done. The abbreviation "WIP," which stands for Work in Progress, is often used for this. The rightmost column lists the work that has been completed. The column is therefore called "Done".

When should a software-based Sprint Backlog be used?

If the Developers are distributed across different locations, a software-based Sprint Backlog should be used.

What does scope creep mean and what does it have to do with the Sprint Backlog?

Scope creep means that during the project life cycle, the scope of a project creeps and increases in an uncontrolled way. In agile projects, changing and adapting requirements is normal. However, during a Sprint there is a goal - the Sprint Goal - and tasks that have to be implemented. This means that scope creep can also occur in agile projects, related to individual Sprints. However, if the Sprint backlog is well managed, the Developers know exactly what they have to do to implement the tasks and thus the User Story.