Requirements18% of the exam
Requirements baselines, traceability and change control
Why requirements live in one version-controlled repository, how a baseline and its change history expose scope creep, how change requests are logged and decided, and how unique IDs trace each requirement to the stories and tests that prove it.
Document requirements in a version controlled repository to manage scope.
~7 min read · 14 practice questions ·
What the exam expects
- Recommend one version-controlled repository over emailed spreadsheets, exports and personal notes, and say which risks it removes.
- Compare current requirements with the approved baseline to separate clarifications from scope creep.
- Take a new or changed requirement through change control: log it, assess impact, get a decision, update the item.
- Set access so a few people edit and stakeholders read and comment, with every revision showing who, when and which approval.
- Trace each requirement by unique ID to the stories and test cases that prove it, keep deferred items with their rationale, and merge duplicates.
Key terms:
- Version control: any system that keeps track of multiple versions of something.
- Baseline: the approved set of requirements that later requests and edits are compared against.
- Scope creep: unauthorized changes included without approval.
- Change request log: a log of every change request, with date, requester and other key information.
- Requirements traceability matrix (RTM): exam convention for the table linking each requirement ID to its stories and test cases.
- Glossary: key terms and definitions that boost understanding across teams.
Key facts
Single source of truth
- Detail
- The backlog describes all changes, updates and requirements
Exam objective
- Detail
- Document requirements in a version-controlled repository to manage scope
Without version control
- Detail
- Teammates can overwrite each other's changes, with no way to go back and recapture them
Each saved change records
- Detail
- Author, time and date, and the changes made
Change request log
- Detail
- Date of request, requester and other key information
Significant requirements added mid-execution
- Detail
- Schedule or cost must change, or the item is deferred
Access rights
- Detail
- Determine who can view and who can edit a diagram
Test cases
- Detail
- Validate the functional requirements
Sources for this section (7)
- Scrum Workflowtrailhead.salesforce.com (opens in a new tab)
- Review Requirementstrailhead.salesforce.com (opens in a new tab)
- Why Version Control Matterstrailhead.salesforce.com (opens in a new tab)
- Work with Your History in Gittrailhead.salesforce.com (opens in a new tab)
- Explore Documentation Typestrailhead.salesforce.com (opens in a new tab)
- Gather Requirementstrailhead.salesforce.com (opens in a new tab)
- Understand Universal Process Notationtrailhead.salesforce.com (opens in a new tab)
- Why does a baseline matter for scope?
- When should a change agreed in a refinement session be written into the repository?
- What does a change request log capture?
- Why keep a glossary in the repository?
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