# Scope vs requirements vs user stories

*Business Analyst Study Guide · Requirements · Last updated October 15, 2026 · https://www.certifyforce.com/study-guide/business-analyst/requirements/scope-vs-requirements-vs-user-stories*

How the scope statement, requirements and user stories differ in purpose, point of view and timing, and how a business need flows down through them without losing business rules.

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

**Official exam objective:**

> Understand the differences between scope, requirements and user stories.

## What the exam expects

- Classify a stakeholder statement as a business objective, a scope boundary, a requirement, a non-functional constraint, a user story or an implementation request.
- Explain why a scope statement names what is out of scope, and how that lets the team recognise a later request as a change.
- Distinguish a functional requirements specification from a system requirements specification, and a use case from a user story.
- Turn an approved requirement into one or more user stories, and decompose a requirement too large for one sprint.
- Explain when each artifact is produced and why stories alone lose business rules.

Key terms:
- **Scope statement specification:** the clear definition of what the project must achieve and the work needed to deliver it.
- **Requirement:** something a stakeholder needs, stated so it is quantifiable and verifiable.
- **User story:** a simple description of a feature told from the user's point of view (who, what, why).
- **Functional requirements specification (FRS):** requirements defined from an end user or business perspective.
- **System requirements specification (SRS):** how the complete system should function, including hardware, software and behaviour.
- **Epic:** a requirement too large for one sprint, split into stories (an exam convention; no Salesforce page defines it).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Scope statement specification | Most fundamental deliverable: what must be achieved and the work to deliver it | [Documentation Types](https://trailhead.salesforce.com/content/learn/modules/business-analyst_skills-strategies/learn-documentation-types-importance-documentation) |
| Scope states exclusions | Describes precisely what is and is not included | [Gather Requirements](https://trailhead.salesforce.com/content/learn/modules/best-practices-for-project-management/gather-requirements) |
| Scope creep | Unauthorized changes included without approval | [Gather Requirements](https://trailhead.salesforce.com/content/learn/modules/best-practices-for-project-management/gather-requirements) |
| FRS | Requirements from an end user or business perspective; expected outcomes | [Documentation Types](https://trailhead.salesforce.com/content/learn/modules/business-analyst_skills-strategies/learn-documentation-types-importance-documentation) |
| SRS | Complete system: hardware, software, functional and behavioural requirements | [Documentation Types](https://trailhead.salesforce.com/content/learn/modules/business-analyst_skills-strategies/learn-documentation-types-importance-documentation) |
| User story format | As a < who >, I want < what > so that < why > | [Learn About User Stories](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories) |
| A story is a synopsis | It does not outline the entire requirement | [Learn About User Stories](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories) |
| A valid requirement | Quantifiable and verifiable; owned by the stakeholder | [BA Detective](https://admin.salesforce.com/blog/2020/become-a-business-analysis-detective) |
| Backlog contents | Includes nonfunctional requirements; owned and prioritized by the product owner | [Scrum Workflow](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-the-elements-of-the-scrum-workflow) |

## Check yourself

- Why does a scope statement list what the project will not deliver?
- Which document describes requirements from an end user or business perspective?
- Why can user stories alone lose business rules?
- When should a backlog item carry the most detail?

## Sources

- [Explore Documentation Types](https://trailhead.salesforce.com/content/learn/modules/business-analyst_skills-strategies/learn-documentation-types-importance-documentation)
- [Review Requirements](https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/review-requirements)
- [Learn About User Stories](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories)
- [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)
- [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)
- [Implement Scrum](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/implement-scrum)
- [Become A Business Analysis Detective](https://admin.salesforce.com/blog/2020/become-a-business-analysis-detective)
- [Explore Techniques for Information Discovery](https://trailhead.salesforce.com/content/learn/modules/business-analyst_skills-strategies/explore-techniques--information-discovery)

## About the full unit

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