Scrum Framework - Three Artifacts

In my previous article, we discussed three roles in Agile Scrum. In this article, we will discuss three artifacts in Scrum Frameworks.

There are three artifacts in Agile Scrum Framework.

Product Backlog
Sprint Backlog
Working Product

(Figure: Scrum Process from : https://commons.wikimedia.org/wiki/File:Scrum_process.svg)

Product Backlog is an ordered list of tasks or features that need to be done within the project. It may have short descriptions of all functionality desired in the product. Product Backlog is owned by the Product Owner.

It is an ordered list of features for the product.
Each product item has an Order, Value, Description, and Estimation.
Generally, tasks which have more business values are the top priority.
Product Owner owns the product backlog.
Product Owner makes sure that the product backlog is clear and transparent to the team.
Anyone from the team can add an idea in the product backlog but it's product owner who decides which one stays there.
There is one Product Backlog for one product, multiple teams who are working on the same product use the same product backlog.

Product backlog has the following different types,

Features
Bugs
Technical work
Knowledge acquisition

Sprint Backlog is an ordered list of tasks that are selected by the Scrum team from the product backlog to be achieved or completed in the sprint. The sprint backlog is owned by Development Team.

Set of product backlog items selected for the sprint.
Sprint Backlog makes visible all of the work items that development team identifies as a priority to meet the sprint goal.
Owned by development team and updated by only development team during the sprint.
Sprint goal is fixed but new tasks which need to complete the sprint goal can be added to the sprint backlog during the sprint.
It is critical that team will only commit to items that they can complete in particular sprint.
Sprint Burndown and Sprint Burnup Chart will be managed during the sprint.

Working Product is something that we have created using product backlog and scrum process which provides benefits to a market.

It's a sum of all the tasks from product backlog that are completed during the sprint and all previously completed sprints.
All tasks must meet acceptance criteria and meet the definition of 'Done'.
Product Owner decides which tasks have been done and are ready for release.

Scrum depends or relies on transparency and the above 3 artifacts help manage transparency among the Product Owner, Scrum Master, and Development Team.

It is the Scrum Master's duty to work with the Product Owner and Development Team to understand if the artifacts are completely transparent. I hope you liked this article, please leave your comments and suggestions in the comment box.

Reference

https://www.scrumalliance.org/
http://staragile.com