Managing Scrum Artifacts
So far, we’ve looked at how the Scrum Team regularly attends Scrum Events, detailed in Chapter 4, as part of a constant inspection and adaptation cycle. Scrum Events involve creating, reviewing, and modifying certain artifacts, namely the Product Backlog, the Sprint Backlog, and the Product Increment.
In this chapter, we are going to examine these artifacts in greater detail. We will learn how to add value to the development process by undertaking certain commitments through artifact creation. We will learn how to capture requirements in the Product Backlog as user stories, using the three Cs and INVEST, and as features, using Impact Mapping. Additionally, we will find out how to refine the Product Backlog, create a Sprint Backlog, and create a Definition of Done.
We will cover these topics in the chapter:
- Understanding the value of the Scrum Artifacts
- Creating and managing the Product Backlog
- Creating and managing the Sprint Backlog...