# Managing user stories in a versioned backlog

*Business Analyst Study Guide · User Stories · Last updated October 15, 2026 · https://www.certifyforce.com/study-guide/business-analyst/user-stories/managing-user-stories-in-a-versioned-backlog*

How a version-controlled story repository becomes the system of record for scope: per-story revision history, recording mid-sprint and post-delivery changes, stakeholder access, deferral decisions, links to requirements and releases, and moving an existing document in as the baseline.

- Certification: Salesforce Business Analyst
- Exam section: User Stories
- Study guide: https://www.certifyforce.com/study-guide/business-analyst

**Official exam objective:**

> Document user stories in a version controlled repository to manage scope.

## What the exam expects

- Establish one version-controlled story repository as the system of record instead of spreadsheets, slides, minutes or chat.
- Use per-story revision history (author, timestamp, comment) to answer who agreed a change and why.
- Record mid-sprint changes, refinement decisions and deferrals against the story, and raise post-delivery changes as new linked items.
- Give stakeholders direct view and comment access, and avoid lost work from concurrent edits.
- Link stories to their parent requirement and release, and migrate an existing document in as the starting baseline.

Key terms:
- **Product backlog:** the ordered list of work, defined at Salesforce as the single source of truth for changes, updates and requirements.
- **Revision history:** the saved record of each change, with its author, time and date.
- **System of record:** the one place whose current version everyone builds, tests and approves against.
- **Deferred:** a story kept in the backlog with the decision to leave it out of the current release.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Product backlog | Single source of truth; constantly refined | [Scrum Workflow](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-the-elements-of-the-scrum-workflow) |
| Backlog owner | Product owner owns and prioritizes it | [Scrum Workflow](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-the-elements-of-the-scrum-workflow) |
| In the backlog ≠ done | Items are pulled into a sprint only if high priority and feasible | [Scrum Workflow](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-the-elements-of-the-scrum-workflow) |
| Exam objective | Document user stories in a version-controlled repository to manage scope | [Refresh Your User Story Skills](https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/refresh-your-user-story-skills) |
| A saved change shows | Author, time and date, and what changed | [Work with Your History in Git](https://trailhead.salesforce.com/content/learn/modules/git-and-git-hub-basics/work-with-your-history-in-git) |
| Reverting a change | Adds a new entry (git revert) rather than erasing the original | [Work with Your History in Git](https://trailhead.salesforce.com/content/learn/modules/git-and-git-hub-basics/work-with-your-history-in-git) |
| No merge process | Teammates can easily overwrite each other's changes, with no way to go back and recapture them | [Why Version Control Matters](https://trailhead.salesforce.com/content/learn/modules/git-and-git-hub-basics/learn-why-version-control-is-important-for-team-based-development) |
| Stories are refined | As many times as needed | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |

## Check yourself

- Why is a slide deck or chat channel not a system of record for stories?
- When a delivered story's behaviour must change, what does the BA create?
- What does each saved revision record?
- Why do concurrent edits get lost without version control?

## Sources

- [Learn the Elements of the Scrum Workflow](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-the-elements-of-the-scrum-workflow)
- [Refresh Your User Story Skills](https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/refresh-your-user-story-skills)
- [Work with Your History in Git](https://trailhead.salesforce.com/content/learn/modules/git-and-git-hub-basics/work-with-your-history-in-git)
- [Learn Why Version Control Is Important for Team-Based Development](https://trailhead.salesforce.com/content/learn/modules/git-and-git-hub-basics/learn-why-version-control-is-important-for-team-based-development)
- [Learn About Salesforce Application Lifecycle Management](https://trailhead.salesforce.com/content/learn/modules/salesforce-application-lifecycle-management-quick-look/learn-about-salesforce-application-lifecycle-management)
- [Learn About Scrum](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-about-scrum)
- [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story)
- [Gather Requirements](https://trailhead.salesforce.com/content/learn/modules/best-practices-for-project-management/gather-requirements)
- [See Business Process Mapping in Practice](https://trailhead.salesforce.com/content/learn/modules/business-process-mapping/see-business-process-mapping-in-practice)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 14 linked practice questions, and unlimited timed mock exams are included with the Business Analyst pack (USD $19): https://www.certifyforce.com/practice-exams