The Scrum Artifacts provide the necessary information and insights of the Scrum Team activities to all the stakeholders of how the software is being developed and what are the steps being planned and executed during the sprint. The three Scrum Artifacts defined in the Scrum process framework are: Product Backlog, Sprint Backlog, and Product Increment.
The Product Backlog is the set of work items that have to be delivered as a part of the end product. These backlog items are categorised by features, prioritised, and arranged in an ordered list. The product backlog acts as a single source of requirements and they keep changing as the requirements from the customers are added or amended. These backlogs are high-visible artifacts of the project are available to all the stakeholders of the project. The Product Backlog is owned by the Product Owner.
The Sprint Backlog is a subset of work items from the main Product Backlog artifact. The Sprint backlog gives an insight into what the team has to accomplish by the end of the sprint. The Scrum team identifies the prioritised work items for the given sprint and adds them to the sprint backlog during the Sprint planning meeting, sets the Sprint goal and delivery roadmap. The sprint backlog items are usually added as user stories with the well-defined acceptance criteria which will meet the “definition of done” rule to mark the work item “done”. Once the items are added, they will not be changed during the sprint. The team can create sub-tasks and work items from the delivery perspective. The Sprint backlogs are owned by developers.
The Product Increment is the list of work items from the Product Backlog that are “done” during the Sprint and available for shipment to the client. This marks the completion of the current sprint by conforming to the “definition of done” checklist, and the next sprint can be kicked off.