Swiftorial Logo
Home
Swift Lessons
Matchups
CodeSnaps
Tutorials
Career
Resources

Scrum Artifacts Tutorial

Introduction to Scrum Artifacts

Scrum is an agile framework for managing complex projects. Within Scrum, artifacts are key deliverables that provide transparency and opportunities for inspection and adaptation. The primary Scrum artifacts are the Product Backlog, the Sprint Backlog, and the Increment. Each of these artifacts serves a specific purpose and contributes to the overall success of the Scrum process.

1. Product Backlog

The Product Backlog is a prioritized list of all the work that needs to be done on the product. It is a dynamic document that evolves as new requirements emerge. The Product Owner is responsible for managing the Product Backlog, ensuring it is transparent, visible, and understood by all stakeholders.

The items in the Product Backlog are often referred to as "backlog items" or "user stories." Each item should include a description, value, and estimation of effort required for completion.

Example:

As a user, I want to reset my password so that I can regain access to my account.

Estimation: 3 story points

2. Sprint Backlog

The Sprint Backlog is the set of items selected from the Product Backlog that the Scrum Team commits to completing during the current Sprint. It includes the user stories and the tasks necessary to deliver the Increment. The Sprint Backlog is updated throughout the Sprint as work is completed and new tasks are identified.

The Sprint Backlog is created during the Sprint Planning meeting, where the Scrum Team collaborates to determine what can be achieved in the upcoming Sprint based on their capacity and the priority of the backlog items.

Example:

Sprint Goal: Implement password reset functionality.

Selected Backlog Items:

  • As a user, I want to request a password reset email.
  • As a user, I want to set a new password.

3. Increment

The Increment is the sum of all the completed Product Backlog items at the end of a Sprint. It must be in a usable condition and meet the Definition of Done as agreed by the Scrum Team. The Increment provides a measure of progress and serves as a basis for future planning.

Each Increment should add value to the product and must be potentially releasable. This means the team should work towards delivering a functional and integrated product at the end of each Sprint.

Example:

The Increment after Sprint 1 includes:

  • User can request a password reset email.
  • User can set a new password.

The Increment is now ready for review and can be released if it meets the acceptance criteria.

Conclusion

Scrum artifacts are essential for maintaining the transparency, inspection, and adaptation that are the cornerstones of the Scrum framework. By understanding and effectively managing the Product Backlog, Sprint Backlog, and Increment, Scrum Teams can ensure they are delivering value to their stakeholders in a timely manner.