You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
Scrum defines three artefacts that represent work or value. Each artefact contains a commitment that provides focus and a measurable target:
| Artefact | Commitment | Purpose |
|---|---|---|
| Product Backlog | Product Goal | An ordered list of everything needed to improve the product |
| Sprint Backlog | Sprint Goal | The set of Product Backlog items selected for the Sprint plus the plan for delivering them |
| Increment | Definition of Done | A concrete stepping stone toward the Product Goal; the sum of all completed items |
These artefacts are designed to maximise transparency — they ensure that everyone has the same understanding of the work being done and the value being created.
The Product Backlog is a single, ordered list of everything that is known to be needed in the product. It is the single source of work for the Scrum Team.
| Characteristic | Description |
|---|---|
| Single source | There is only one Product Backlog, even if multiple teams work on the product |
| Ordered | Items are ordered by value, risk, dependencies, and need — the Product Owner decides the order |
| Emergent | The backlog is never complete; it continuously evolves as the product and market change |
| Refined | Items are progressively detailed — items near the top are small and well-understood; items lower down are larger and less defined |
Refinement (sometimes called "grooming") is the act of breaking down and further defining Product Backlog items. This is an ongoing activity, not a single event. Refinement typically includes:
Tip: The Scrum Guide recommends that refinement should consume no more than 10% of the Developers' capacity.
The Product Goal is the long-term objective for the Scrum Team. It describes a future state of the product. The team pursues one Product Goal at a time.
| Aspect | Description |
|---|---|
| Scope | High-level vision; broader than a single Sprint |
| Communication | Clearly communicated so the team understands the direction |
| Progress | Measured by the state of the Product Backlog and Increments delivered |
| Completion | A Product Goal is either achieved or abandoned before a new one is set |
The Sprint Backlog is composed of three elements:
| Characteristic | Description |
|---|---|
| Owned by Developers | Only the Developers can change the Sprint Backlog during the Sprint |
| Real-time plan | Updated throughout the Sprint as the Developers learn more |
| Highly visible | Typically displayed on a task board (physical or digital) |
| Scope flexibility | The Sprint Goal is fixed, but the specific items and tasks can be negotiated with the Product Owner |
The Sprint Goal is a single objective for the Sprint. It provides:
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.