Scrum Artifacts contain critical information that the Scrum Team and STAKEHOLDERS need to know in order to understand the product being developed, the activities that have been completed, and the activities that are planned for the project. The Scrum Process Framework defines the following artifacts:

• Product Backlog: The Product Backlog is a list of all the features, functionalities, requirements, additions, and fixes that will be included in FUTURE releases of the product. Description, order, estimate, and value are all properties of Product Backlog items.  The Product Owner is in charge of the Product Backlog's content, as well as its availability and ordering.
• Sprint Backlog: The Sprint Backlog consists of the Product Backlog items chosen for the Sprint, as well as a strategy for delivering the product increment and achieving the Sprint Goal. It is the Team's projection of what feature will be available in the next Increment, as well as the work required to turn that functionality into a working product Increment.
• Increment: The Increment is the total of all Product Backlog items accomplished THROUGHOUT a Sprint plus all preceding Sprint increments. The new Increment must be a working product at the end of a Sprint, which means it must be in usable form. Regardless of whether the Product Owner decides to release it, it must be in functioning condition.
• Sprint Burn-Down Chart: The total work remaining in the Sprint Backlog can be totalled at any point throughout the Sprint. The team keeps track of the overall work remaining for each Daily Scrum to estimate the chances of MEETING the Sprint Goal. The Team can control its progress by keeping track of the remaining work during the Sprint. The Sprint Burn-Down Chart is a METHOD of tracking how much work the Scrum Team has done in a given sprint. This has been shown to be an effective method for tracking Sprint progress toward the Sprint Goal.