Scrum Artifacts

Product itself- The Scrum model expects the team to bring the product or system to a potentially shippable state at the end of each Scrum sprint.

Product Backlog- This is the complete list of the functionality that remains to be added to the product. The product owner prioritizes the backlog so the team always works on the most valuable features first. It is created by populating it with user stories, which are short descriptions of functionality described from the perspective of a user or customer.

Sprint Backlog- The sprint backlog is the list of tasks the team needs to perform in order to deliver the functionality it committed to deliver during the sprint. It is created by team members on the first day of a sprint and during the planning meeting. It is just like team’s to-do list for the sprint, whereas a product backlog is a list of features to be built.

Sprint Burndown Chart- Burndown charts show the amount of work remaining either in a sprint or a release, and are an effective tool in Scrum software development to determine whether a sprint or release is on schedule to have all planned work finished by the desired date. A burn down chart is a visual representation of the amount of work that still needs to be completed. A burn down chart has a Y axis that shows work and an X axis that shows time. Ideally, the chart illustrates a downward trend, as the amount of work still left to do over time burns down to zero.

Product increment- This refers to what has been accomplished during a Sprint — all the product backlog items — as well as what’s been created during all previous Sprints. The product increment reflects how much progress has been made.