Scrum Artifacts — Product Backlog and Sprint Backlog
More blog posts about Scrum:
→ Scrum Theory — What is this?
→ Who’s on a Scrum team?
→ What are Scrum events?
Scrum artifacts show the value or the work to create transparency and verification possibilities. These artifacts are specifically designed to maximize the essential information so that everyone involved can have the same understanding of an artifact.
There are two parts: the Product Backlog and the Sprint Backlog.
Product backlog
Here all requirements for the product are listed. It is kept dynamic and is always being developed further. Furthermore, it is never complete. The origin of the work of the development team can be found here.
The product owner is responsible for adding, editing and maintaining the backlog.
The product backlog lists all improvements, bug fixes and features that need to be changed in the product. It contains a description, an order and the estimate, which is also the responsibility of the development team. The Product Owner’s task is to describe the entries as clearly as possible so that the development team does not have any problems with the estimation. Due to changes in business requirements, market or technology, there are also changes in the backlog, which never stops changing.
A refinement of the product backlog is a process where details are added to each entry. An estimate is also made and the order is determined. When the entries that the development team will deal with in the next sprint are finished in detail, it can be considered “ready”.
Sprint Backlog
The sprint backlog consists of the product backlog tasks selected for the sprint. A sprint target is also added. It is a forecast of the development team, which functionalities will be in the next step and what has to be done to get it “done”.
It is usually displayed in the form of a task board.
Social Media
https://twitter.com/Vollcom_Digital
Vollcom Digital GmbH
Thierschstraße 34, 80538 München
info@vollcom-digital.de
