
Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. The artifacts are:
- Product Backlog
- Sprint Backlog
- Increment
Product Backlog
The Product Backlog is a transparent and ordered list of known and valuable work. It is the single source of work for the Scrum Team. By the time a Product Backlog items (PBI) reaches the top of the Product Backlog, it must have been refined to a ready state meaning enough is known, and it is small enough to be taken into a Sprint.
The Product Owner is accountable for the Product Backlog although others may assist them to manage it. Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.
Sprint Backlog
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
It represents a forecast by the Developers about what valuable work will be in the next Increment and it makes this work visible. It has enough detail that progress can be inspected at the Daily Scrum. The Developers may modify the Sprint Backlog throughout the Sprint as more is learned about the best way to complete the work.
Increment
An Increment is a body of inspectable, useable and Done work that supports empiricism. It is the sum of all the Product Backlog items Done during a Sprint and the Increments of all previous Sprints.
For work to form part of Increment it must meet The Definition of Done. The Increment is a tangible step towards a Product Goal and is inspected in the Sprint Review.
At the end of a Sprint, any work that did not meet the Definition of Done is returned to the Product Backlog.
Continue reading the series to learn more. Total reading time is less than 15 minutes.




