There are primarily 3 scrum artefacts. The purpose behind maintaining these artefacts is to ensure transparency across teams and stakeholders.
The reason why artefacts are important are:
Artefacts should be transparent
Optimizes the value and minimizes the risk
Incomplete artefacts create blind spot.
Product Backlog
List of everything that is needed in order to build a product. It contains all items including user stories, features, test criteria, bugs, tests etc.
A product backlog item has 4 attributes
Description
Value
Order
Estimate
This list is never finite, its ever evolving. As the team proceeds with the first sprint, the product backlog keeps getting refined due to feedbacks from existing items and new requirements coming in.
Product Owner uses Product Backlog to measure the progress. It can be done by keeping a check on release burndown chart or the cumulative flow diagram.
Sprint Backlog
Subset of Product Backlog. Development Team is the Owner of Sprint Backlog. This is finalised during the sprint planning meeting. Depending on the velocity of the team, the sprint backlog is finalised.
This artefact is used by the development team to track their progress.
Increment
Sum of all the sprint backlogs that are already completed. if multiple teams are working on the product, then it is the combined effort of all teams.
Increments should always be in releasable state, but it depends on the product owner if he wants to release it or not.
It's always advised to release increments at least once in every 2 months.
コメント