Blog‎ > ‎1. Scrum‎ > ‎

4.Scrum Artifacts

The Scrum Artifacts

Product Backlog

The requirements in Scrum are called Backlog. Backlog is everything that is yet to be done and not necessarily the activities that the team has fallen behind.

The product backlog is an ordered list of requirements that is maintained for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever needs to be done in order to successfully deliver a viable product. The product backlog items (PBIs) are ordered by the Product Owner based on considerations like risk, business value, dependencies, date needed, etc.

The product backlog contains the Product Owner’s assessment of business value and the Development Team’s assessment of development effort.

The product backlog and the business value of each backlog item is the responsibility of the Product Owner.

The size (i.e. estimated complexity or effort) of each backlog item is, however, determined by the Development Team, who contributes by sizing items, either in story points or in estimated hours.

Sprint Backlog

The list of the tasks to be executed by the Scrum Team in upcoming Sprint is called the “Sprint Backlog”.

It is common practice that the Sprint Backlog is represented on a task board which provides a constantly visible depiction of the status of the user stories in the backlog. Also included in the Sprint Backlog are any risks associated with the various tasks. Any mitigating activities to address the identified risks would also be included as tasks in the Iteration Backlog.

Once the Sprint Backlog is finalized and committed to by the Team, new User Stories should not be added. However, tasks that might have been missed or overlooked from the committed User Stories may need to be added. If new requirements arise during a Sprint, they will be added to the overall Prioritized Product Backlog and included in a future Iteration.

The Sprint backlog is the list of work the Development Team must address during the next iteration. The list is derived by selecting product backlog items from the top of the product backlog until the Development Team feels it has enough work to fill the iteration. This is done by the Development Team asking “Can we also do this?” and adding product backlog items to the iteration backlog. The Development Team should keep in mind its past performance assessing its capacity for the new sprint, and use this as a guide line of how much “effort” they can complete.


The Increment is the sum of all Product Backlog Items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done” which means that it st be in a useable condition and meet the Scrum Team’s definition of Done. It must be in a useable condition regardless of whether the Product Owner decides to actually release it.

Sample Scrum Agile Video by Amit Kulkarni

Sample Training Video by Sateesh Kamat


Amit Kulkarni conducting Planning Poker Estimation Exercise


EPMC - Project Foundational Concepts by Sateesh Kamat