3. Scrum Artifacts

Scrum’s artifacts represent work or value in various ways that are useful in providing transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information needed to ensure Scrum Teams are successful in delivering a “Done” Increment.[23]

  • Product Backlog: 
    The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Backlog is never complete, it only lays out the known and best understood requirements. Product Backlog is dynamic, it consistently changes to identify what the product needs to be useful.

    The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in the future releases. As product is used and gains value, feedback is provided and the Backlog becomes larger. Requirements never stop changing. Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.

  • Monitoring Progress Toward a Goal:
    At any time, the total work remaining to reach the goal can be summed. Various projection practices have been used to forecast progress, but whats will happen is unknown. Only what has happened can be use for forward-looking decision-making. 

  • Sprint Backlog:
  • The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality. The Sprint Backlog defines the work the Development Team will perform to turn Product Backlog items into a “Done” Increment. The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal. [23]

  • Monitoring Sprint Progress:
    Development team tracks total work remaining at least for every Daily Scrum. Development team tracks these sums daily and projects likelihood of achieving the Sprint Goals. 

  • Increment:
    The Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. At the end of a Sprint, the new Increment must be “Done,” which means it must be in usable condition and meet the Scrum Team’s Definition of “Done.” It must be in usable condition regardless of whether the Product Owner decides to actually release it.