---
title: How do Scrum Teams capture and document Product Backlog items?
description: "Many Scrum Teams use user stories to capture and document [Product Backlog](https://www.thescrummaster.co.uk/glossary/a-scrum-artifact-that-consists-of-an-ordered-list-of-the-work-to-be-done-in-order-to-create-maintain-and-sustain-a-product-managed-by-the-product-owner/) items. User stories are a common practice in Scrum but not mandatory. They provide a structured way to describe features or functions from the perspective of the end-user,…"
url: "https://www.thescrummaster.co.uk/docs/how-do-scrum-teams-capture-and-document-product-backlog-items/"
updated: "2024-12-19"
category: Artifacts / Product Backlog
---

# How do Scrum Teams capture and document Product Backlog items?

Many Scrum Teams use user stories to capture and document [Product Backlog](https://www.thescrummaster.co.uk/glossary/a-scrum-artifact-that-consists-of-an-ordered-list-of-the-work-to-be-done-in-order-to-create-maintain-and-sustain-a-product-managed-by-the-product-owner/) items. User stories are a common practice in Scrum but not mandatory. They provide a structured way to describe features or functions from the perspective of the end-user, which helps in ensuring that the team understands the [Value](https://www.thescrummaster.co.uk/glossary/value/) and purpose of the work.

Using user stories helps in breaking down complex tasks into smaller, manageable pieces. It also promotes a user-centric approach to development, ensuring that the final product meets the needs of its users. However, teams can choose other methods that best suit their needs and context.