Scrumโs artifacts include Product Backlog๐, Sprint Backlog๐ and the increment๐ฆ.
These artifacts represent the work or value to provide transparency and opportunities for inspection and adaptation.
These artifacts help in generating a common understanding of the work being done, and the work that is planned.
๐ ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐๐๐ค๐ฅ๐จ๐ ๐ข๐ฌ ๐ญ๐ก๐ ๐ฌ๐ข๐ง๐ ๐ฅ๐ ๐ฌ๐จ๐ฎ๐ซ๐๐ ๐๐จ๐ซ ๐๐ฅ๐ฅ ๐ญ๐ก๐ ๐ซ๐๐ช๐ฎ๐ข๐ซ๐๐ฆ๐๐ง๐ญ๐ฌ ๐๐จ๐ซ ๐ ๐ฉ๐๐ซ๐ญ๐ข๐๐ฎ๐ฅ๐๐ซ ๐ฉ๐ซ๐จ๐๐ฎ๐๐ญ.ย
It lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases.
Product Owner๐งโ๐ผ owns the product backlog and is responsible for its content, availability and ordering.
Product Owner can make changes in the product backlog,
or may ask anyone from the development team or the scrum master to make the changes in it on his behalf,ย
but the ultimate accountability lies with the product owner.
๐ ๐๐ฉ๐ซ๐ข๐ง๐ญ ๐๐๐๐ค๐ฅ๐จ๐ ๐๐จ๐ง๐ฌ๐ข๐ฌ๐ญ๐ฌ ๐จ๐ ๐ญ๐ก๐ ๐๐จ๐ฅ๐ฅ๐จ๐ฐ๐ข๐ง๐ ๐ญ๐ฐ๐จ ๐ข๐ญ๐๐ฆ๐ฌ:
๐ The set of Product Backlog items selected for the Sprint
๐ A plan for delivering the product Increment and realizing the Sprint Goal.
A Sprint backlog is generally created in the Sprint planning meeting.
It may not necessarily be complete at the end of the Sprint planning.
The development team๐งโ๐ป๐จโ๐ป๐ฉโ๐ป modifies the sprint backlog during the sprint as more details become available.
๐ฆ ๐๐ก๐ ๐๐ง๐๐ซ๐๐ฆ๐๐ง๐ญ ๐ข๐ฌ:
๐ The sum of all the Product Backlog items completed during a Sprint, and,
๐ The value of the increments of all previous Sprints.