User Stories18% of the exam
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.
Document user stories in a version controlled repository to manage scope.
~7 min read · 14 practice questions ·
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
Product backlog
- Detail
- Single source of truth; constantly refined
Backlog owner
- Detail
- Product owner owns and prioritizes it
In the backlog ≠ done
- Detail
- Items are pulled into a sprint only if high priority and feasible
Exam objective
- Detail
- Document user stories in a version-controlled repository to manage scope
A saved change shows
- Detail
- Author, time and date, and what changed
Reverting a change
- Detail
- Adds a new entry (git revert) rather than erasing the original
No merge process
- Detail
- Teammates can easily overwrite each other's changes, with no way to go back and recapture them
Stories are refined
- Detail
- As many times as needed
Sources for this section (5)
- Scrum Workflowtrailhead.salesforce.com (opens in a new tab)
- Refresh Your User Story Skillstrailhead.salesforce.com (opens in a new tab)
- Work with Your History in Gittrailhead.salesforce.com (opens in a new tab)
- Why Version Control Matterstrailhead.salesforce.com (opens in a new tab)
- Construct a User Storytrailhead.salesforce.com (opens in a new tab)
- 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?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Business Analyst pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Business Analyst guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams