Exercise "Product 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.
Product Backlog Item (= PBI)¶
A Product Backlog Item (PBI) is an entry in the Product Backlog and can take various forms, such as tasks, activities, User Stories, epics, or themes.
Scrum artifacts¶
Scrum Artifacts are documents or tools that make the progress and value of work transparent in the Scrum process. These include the Product Backlog, Sprint Backlog, and Increment, each with a specific focus or goal.
Backlog Refinement Meeting¶
The Backlog Refinement Meeting is a regular gathering where the Product Backlog is reviewed and assessed. It involves evaluating the relevance of individual User Stories and their alignment with stakeholder interests.
Product Goal¶
The Product Goal is the desired outcome of a Scrum project and serves as a guiding principle for development work. It is realised through the Sprints of the Scrum team.
User Stories¶
A User Story is an entry in the Product Backlog that reflects the requirements and wishes of the customer or end user. It should meet the INVEST criteria and should not contain technical details for implementation.
Epics¶
Epics are particularly large User Stories that are too complex for typical assessment and implementation. They usually need to be further subdivided into manageable tasks that can be implemented within a development interval.
Themes¶
Themes are different User Stories combined into a topic area.
Tasks¶
Tasks are derived from the User Stories. Usually processed by one person. Unlike User Stories, Epics, and Themes, tasks are not a direct part of the Product Backlog.
Kano model¶
The Kano model shows how specific product features or services influence customer satisfaction. It categorises these features into five types, each of which can have different effects on customer satisfaction. These categories are basic, performance, excitement, indifferent, and dissatisfaction.
Test yourself¶
Try to answer the following questions on your own. Take your time and think carefully before checking the solutions.
Where are the customer's requirements listed?
In the Product Backlog.
When is the Product Backlog created?
The Product Backlog is created at the beginning of a project and is maintained throughout the project.
What is a Scrum Artefact?
The Scrum artifacts are the three process documents: the Product Backlog, which is described in detail in this chapter, as well as the Sprint Backlog and the Increment. The Scrum artifacts help the Scrum Team gain an overview of the work or value. Each Scrum Artefact includes a commitment that the Scrum Team upholds.
What does the abbreviation 'GUI' stand for?
GUI is the abbreviation for Graphical User Interface.
What does the acronym 'DEEP' stand for?
- (appropriately) Detailed
- Estimated
- Emergent
- Prioritised
Why does the Product Backlog have to be prioritised? Which ranking makes sense?
Since not all entries of the Product Backlog are formulated in the same detail, are not equally important, and are not of the same size, it is important to prioritise the entries of the Product Backlog so that they can be processed in the determined order. The entries are ranked according to their importance and the higher a PBI is ranked in the Product Backlog, the more detailed its description. The top entries are the PBIs that the Product Owner wants to have implemented first. The criterion for prioritisation is usually the business value that the implementation of the respective User Story delivers. But other criteria may also play a role, such as development costs, the value estimate, or risks.
Who has the final say in deciding on the prioritisation of the Product Backlog?
The Product Owner.
What does the abbreviation PBI stand for? What does it mean?
PBI stands for Product Backlog Item, which means an entry in the Product Backlog. These can be User Stories, tasks, Epics, or Themes.
Explain the Kano model including its three characteristics.
The Kano model graphically represents the relationship between customer satisfaction ("low" to "high") and the realised quality ("not fulfilled" to "realised"). The three central characteristics are:
- Basic attributes
- are a matter of course and are taken for granted by the customer.
- do not make customers more satisfied if they are provided.
- make customers disproportionately dissatisfied if they are not provided.
- Performance attributes:
- are actively demanded by the customer.
- can, for example, be found out by observing the market.
- satisfy customers when they are provided.
- make customers dissatisfied if they are not provided.
- Attractive attributes:
- are not a matter of course and customers do not demand these features.
- do not make customers more dissatisfied if they are not provided.
- make customers disproportionately satisfied if they are provided.
What is the difference between User Stories, Epics, and Themes?
User Stories are wishes and requirements for a final product that are written down in "prose" by the Product Owner or stakeholders. They do not refer to how the features will be technically implemented - this comes later in the Sprint Backlog. Epics are very extensive User Stories that are still too large for a User Story at the time of their evaluation as an Epic. Themes are different User Stories that are grouped into a common topic area.
What is the commitment to the Product Backlog? Please explain.
The Product Goal is the commitment associated with the Product Backlog. The Product Goal creates transparency and the Scrum Team commits to the Product Goal. It serves as a compass during development and describes a concrete goal that is pursued with the Scrum project and achieved through the Sprints.
What questions should be asked when creating the Product Goal?
- How is the business model structured?
- Which audience or target group is being addressed?
- What is the need or benefit of the client or consumer?
- What are the unique selling points of the application or product compared to competitors?
- In which way is profit to be generated?
- Why is the project being carried out?
- What is the project about? What exactly is being offered?
Why does the Product Backlog need to be updated regularly?
Assessing, reviewing, and updating the Product Backlog regularly will ensure that the entries are still up-to-date and whether they correctly reflect the interests of the customer.
Which meeting is held to update the Product Backlog? What is the process and who is responsible for this meeting?
The Backlog Refinement Meeting. There is no fixed agenda for this meeting, but a possible agenda could be as follows:
- Sorting and prioritising the Product Backlog Items
- Deleting entries that are no longer important
- Adding new entries to the Product Backlog
- Formulating and adding details to Product Backlog Items
- Summarising Product Backlog Items
- Estimating entries in the Product Backlog (effort estimation)
- If necessary, schedule releases
The Product Owner is responsible for the Backlog Refinement Meeting in his role as manager of the Product Backlog. They are supported by the Developers.