Home › Business Analyst › User Stories

Business Analyst practice questions: User Stories

User Stories is 18% of the Salesforce Certified Business Analyst exam. It covers story format, acceptance criteria and INVEST. Try these 9 free questions, then open each answer to see why every option is right or wrong.

While reviewing user stories for a new Salesforce CPQ rollout at an outdoor gear company, a BA sees this story: 'As a sales rep, I want a button to generate a quote so that I can send pricing to customers.' The developers report that it is too big to finish within one sprint. Which INVEST criterion does the story fail?

Negotiable - once written, the story's scope can no longer change.
Independent - the story relies on other system components to work.
Valuable - the story does not make the business value for the user clear.
Small - the story contains more work than can be completed in a single sprint iteration.

Show answer

Answer: D

A. Negotiable - once written, the story's scope can no longer change.Incorrect. Negotiable means the details and scope can be discussed and adjusted before development. Being too large does not make a story non-negotiable; large stories can still be split.

B. Independent - the story relies on other system components to work.Incorrect. Independence is about whether another story blocks this one. The problem here is size, not dependency.

C. Valuable - the story does not make the business value for the user clear.Incorrect. The story states its value ('so that I can send pricing to customers'). The team's concern is size, not value.

D. Small - the story contains more work than can be completed in a single sprint iteration. ✓Correct. The 'S' in INVEST means a story must be small enough to finish in one sprint. A story flagged as too large fails Small and should be broken into sprint-sized stories.

Why: INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, Testable. A story that cannot fit in a sprint breaks the Small criterion, so the BA splits it into smaller stories that each fit the sprint and still deliver incremental value.

For a Salesforce CPQ rollout at a packaging manufacturer, the BA wrote: 'As an account executive, I want to be notified when a quote I submitted has been approved so that I can promptly follow up with the customer.' In backlog grooming, the product owner asks whether the story is negotiable. In this situation, what does the Negotiable criterion of INVEST mean?

Negotiable means the product owner may decide not to build the story if it drops in backlog priority.
Negotiable means HOW the story is delivered (notification channel such as email, in-app, or push notification) is flexible and open to discussion and agreement between the BA, product owner, and development team - the business need is fixed while implementation details stay open.
Negotiable means the account executive persona can be swapped for any other Salesforce user persona without changing the story's value.
Negotiable means the acceptance criteria can be changed at any point during the sprint without consulting anyone.

Show answer

Answer: B

A. Negotiable means the product owner may decide not to build the story if it drops in backlog priority.Incorrect. Any backlog item can lose priority; that is not what Negotiable means. The term refers to flexibility in the story's details, not its priority.

B. Negotiable means HOW the story is delivered (notification channel such as email, in-app, or push notification) is flexible and open to discussion and agreement between the BA, product owner, and development team - the business need is fixed while implementation details stay open. ✓Correct. The business need is fixed, but the delivery mechanism (email, in-app banner, push notification, Chatter post) is open to discussion based on feasibility and user experience, which also keeps stories from dictating technical solutions.

C. Negotiable means the account executive persona can be swapped for any other Salesforce user persona without changing the story's value.Incorrect. The persona defines who benefits; changing it changes the story itself. Negotiable concerns implementation details, not the core who/what/why.

D. Negotiable means the acceptance criteria can be changed at any point during the sprint without consulting anyone.Incorrect. Changing acceptance criteria mid-sprint requires consulting the product owner and stakeholders; it is not a unilateral change. Negotiable refers to implementation flexibility before the sprint.

Why: The 'N' in INVEST means a story is not a locked specification. The need (the AE learns when a quote is approved) is firm, but how it is delivered (email, in-app alert, Chatter) is agreed among the BA, product owner, and team based on feasibility and design.

A Service Cloud team at an outdoor gear company reviews this story: 'As a case manager, I want to reassign a case to another agent so that the customer receives timely assistance from the right expert.' The developers say it is ready to estimate, but the BA disagrees. What gap is the BA most likely seeing?

The story doesn't say whether Salesforce Cases or Salesforce Tasks should track the reassignment.
The story lacks acceptance criteria, so there are no testable conditions defining when the reassignment feature is successfully implemented.
'Case manager' is not a standard Salesforce role and should be replaced with 'System Administrator.'
The story is too brief and needs a full paragraph of background before the team can estimate it.

Show answer

Answer: B

A. The story doesn't say whether Salesforce Cases or Salesforce Tasks should track the reassignment.Incorrect. Which object tracks the reassignment is an implementation choice, not a readiness criterion. Stories should stay implementation-agnostic.

B. The story lacks acceptance criteria, so there are no testable conditions defining when the reassignment feature is successfully implemented. ✓Correct. The role, action, and value are present, but nothing defines what 'reassign a case' means in testable terms: who can reassign to whom, under what conditions, and what confirmation is sent. These must be acceptance criteria before estimating and building.

C. 'Case manager' is not a standard Salesforce role and should be replaced with 'System Administrator.'Incorrect. Case manager is a valid business role. Personas describe business roles, not Salesforce system roles.

D. The story is too brief and needs a full paragraph of background before the team can estimate it.Incorrect. Length is not a readiness test; short, clear stories with good acceptance criteria are preferred.

Why: Even a well-structured story statement is not ready without acceptance criteria. Criteria define when reassignment is allowed, how the system should behave, and what outcome proves it works; without them developers build their own interpretation and UAT has nothing concrete to test.

A BA at a packaging manufacturer finds this in the sprint backlog: 'As a customer service manager, I want the system to automatically escalate cases that have been open for more than 2 hours to a senior agent AND send an email notification to the manager AND create a follow-up task AND update the case priority to High.' The developers estimate three sprints. What should the BA do?

Accept the three-sprint estimate, since the story describes a complete business process and shouldn't be split.
Ask the developers to raise their sprint velocity to fit the large story.
Split the story into smaller, independently deliverable stories - for example separate ones for escalation routing, the manager email notification, follow-up task creation, and the priority update.
Turn the story into an epic and push all four behaviors to a later project phase.

Show answer

Answer: C

A. Accept the three-sprint estimate, since the story describes a complete business process and shouldn't be split.Incorrect. Needing three sprints violates Small. Even a complete process must be broken into sprint-sized stories to keep iterative delivery.

B. Ask the developers to raise their sprint velocity to fit the large story.Incorrect. Demanding more velocity does not fix a badly sized story; decomposition does.

C. Split the story into smaller, independently deliverable stories - for example separate ones for escalation routing, the manager email notification, follow-up task creation, and the priority update. ✓Correct. The four distinct behaviors can each be developed, tested, and released separately, making every piece sprint-sized and delivering value incrementally.

D. Turn the story into an epic and push all four behaviors to a later project phase.Incorrect. Epics suit very large features, but these concrete behaviors can be sized for sprints by splitting them. Deferring everything is unnecessary.

Why: A story that cannot fit in one sprint fails INVEST's Small criterion, so the BA decomposes it. Each resulting story should be valuable by itself; escalation, email notification, task creation, and priority update can each be built, tested, and delivered independently.

At a sprint review at a sneaker brand, the team demos a finished feature on the sales opportunity dashboard. Sales reps who never took part in the original requirements sessions watch the demo and raise five new requirements they consider critical. The product owner asks the BA how to handle them. What should the BA recommend?

Add all five requirements to the current sprint as extra stories, since the review exposed a gap in the original discovery.
Acknowledge the new requirements, record them as user stories in the product backlog, and prioritize them with the product owner for a future sprint.
Reject all five because they were not found in the original discovery sessions and are out of scope.
Have the sales reps write up the requirements themselves and send them to the project manager to add to the project plan.

Show answer

Answer: B

A. Add all five requirements to the current sprint as extra stories, since the review exposed a gap in the original discovery.Incorrect. Adding scope to a running sprint breaks commitments and destabilizes delivery. The right response is backlog management.

B. Acknowledge the new requirements, record them as user stories in the product backlog, and prioritize them with the product owner for a future sprint. ✓Correct. The BA records the requirements as user stories in the backlog, and the product owner ranks them against existing items for a future sprint, keeping sprint integrity while losing nothing.

C. Reject all five because they were not found in the original discovery sessions and are out of scope.Incorrect. Rejecting real business needs for surfacing late is wrong; Agile welcomes evolving requirements. The BA's job is to document them, not to gatekeep.

D. Have the sales reps write up the requirements themselves and send them to the project manager to add to the project plan.Incorrect. Having users self-document and bypass the BA skips the BA's requirements management role. The BA should elicit and write the stories with the reps.

Why: Finding new requirements at a sprint review is normal in Agile; seeing working software prompts learning. The BA captures them as backlog user stories and prioritizes them with the product owner for later sprints, protecting the current sprint while keeping the new insights tracked.

In a Service Cloud sprint review at a packaging manufacturer, the team shows a finished story. A stakeholder says: 'This works correctly, but I also need cases that stay open more than 4 hours to escalate automatically.' Checking the original story and acceptance criteria, the BA confirms escalation was never documented. What should the BA do NEXT?

Add escalation to the existing story's acceptance criteria and have the developer build it right away.
Acknowledge the feedback, write a new user story for the escalation requirement, and put it in the product backlog for prioritization in a future sprint.
Dismiss the feedback because the original story was finished and its acceptance criteria were met.
Add the escalation rule to the current story's definition of done and mark the story incomplete.

Show answer

Answer: B

A. Add escalation to the existing story's acceptance criteria and have the developer build it right away.Incorrect. Reopening a finished story and demanding immediate work skips sprint planning, adds unplanned work, and destabilizes the backlog. This is new scope, not a fix.

B. Acknowledge the feedback, write a new user story for the escalation requirement, and put it in the product backlog for prioritization in a future sprint. ✓Correct. New functionality spotted in a review or UAT becomes a new backlog story, so it is tracked and prioritized without disrupting the current sprint.

C. Dismiss the feedback because the original story was finished and its acceptance criteria were met.Incorrect. Dismissing valid feedback erodes trust and leaves a real need unmet. The BA manages scope through the proper process instead.

D. Add the escalation rule to the current story's definition of done and mark the story incomplete.Incorrect. The definition of done is a team quality standard (code reviewed, tested, deployed to sandbox), not a place for new functional requirements. A new story is the right vehicle.

Why: Net-new requirements raised at a sprint review are a scope change: acknowledge them, write a new user story, and add it to the backlog for prioritization. This protects the sprint and keeps the need tracked. Note the distinction: acceptance criteria are story-specific, while the definition of done is a team-wide quality gate.

A BA at a packaging manufacturer reviews the acceptance criteria on a Salesforce Sales Cloud opportunity story, which say: 'The system should allow sales reps to create opportunities.' A tester reports being unable to tell whether this passes or fails. What change should the BA make?

Remove the criterion because creating opportunities is a standard Salesforce feature that needs no documentation.
Rewrite it in Given/When/Then format with specific preconditions, user actions, and observable expected outcomes the tester can judge unambiguously as pass or fail.
Add a note to the criterion saying it 'should be tested thoroughly by the development team before UAT.'
Turn the criterion into a user story: 'As a sales rep, I want to create opportunities so that I can track my sales pipeline.'

Show answer

Answer: B

A. Remove the criterion because creating opportunities is a standard Salesforce feature that needs no documentation.Incorrect. Standard features still need acceptance criteria when they are part of the story; otherwise the tester cannot confirm they work in this business context.

B. Rewrite it in Given/When/Then format with specific preconditions, user actions, and observable expected outcomes the tester can judge unambiguously as pass or fail. ✓Correct. For example: 'Given a sales rep with Opportunity Create permission, When they click New Opportunity, fill in required fields, and save, Then a new opportunity record is created with the entered data and the rep as owner.' This gives a clear pass/fail.

C. Add a note to the criterion saying it 'should be tested thoroughly by the development team before UAT.'Incorrect. Developer testing belongs to the definition of done and does not fix a vague criterion.

D. Turn the criterion into a user story: 'As a sales rep, I want to create opportunities so that I can track my sales pipeline.'Incorrect. A story states the need and acceptance criteria state its testable conditions; both are needed and one cannot become the other.

Why: Acceptance criteria must let a tester decide pass or fail without interpretation. The current wording names no condition, action, or observable result. Given/When/Then supplies a precondition (Given), a triggering action (When), and an expected system state (Then), making UAT objective and consistent.

A footwear retailer is wrapping up a Sales Cloud rollout, and the BA must judge whether the original business goals were met. The goals were 'Cut sales rep data entry time by 30%' and 'Give regional managers better pipeline visibility.' How should the BA evaluate them?

Ask the project sponsor whether, in their opinion, the goals were reached.
Measure the same metrics captured as a baseline during discovery (data entry time and pipeline visibility ratings before go-live) after implementation, using the same method, and compare the two.
Check the approved requirements list and confirm every user story was delivered as 'done.'
Survey the developers on whether they think the delivered features will reduce data entry and improve visibility.

Show answer

Answer: B

A. Ask the project sponsor whether, in their opinion, the goals were reached.Incorrect. A sponsor's opinion is subjective. Quantified goals need measurable evidence.

B. Measure the same metrics captured as a baseline during discovery (data entry time and pipeline visibility ratings before go-live) after implementation, using the same method, and compare the two. ✓Correct. Comparing post-implementation measurements with the discovery baseline directly shows whether the 30% reduction happened. This is exactly why capturing baseline metrics in discovery is a key BA task.

C. Check the approved requirements list and confirm every user story was delivered as 'done.'Incorrect. All stories being 'done' shows the features were built as specified, not that they delivered the business outcome. A project can ship every story and still miss its goals.

D. Survey the developers on whether they think the delivered features will reduce data entry and improve visibility.Incorrect. Developer expectations are not a measurement. Outcomes must be checked against real performance data.

Why: Goal achievement is proven by comparing post-go-live results with the baseline taken during discovery, such as average daily data entry minutes per rep or manager visibility survey scores. Measuring the same metrics the same way afterward shows whether quantified objectives were actually met, not just whether features shipped.

A camping supplies company adds a rule: 'Any quote totaling more than $50,000 needs approval from both the regional sales director AND the VP of Finance.' The BA is writing Given/When/Then acceptance criteria for the story. Which criterion BEST expresses this rule?

Given any quote in the system, when it is submitted, then both the regional director and the VP of Finance are notified.
Given a quote with a total value of $50,000 or more, when a sales rep submits it for approval, then the quote goes through a two-step approval that needs sign-off from both the regional sales director and the VP of Finance before it can be sent to the customer.
Given a quote submitted with a discount, when the total goes past company limits, then an approval workflow starts.
Given that the VP of Finance and the regional director are both available, when a large quote is submitted, then they get an email asking them to approve it.

Show answer

Answer: B

A. Given any quote in the system, when it is submitted, then both the regional director and the VP of Finance are notified.Incorrect. It drops the $50,000 condition, so every quote would trigger dual notification, which is wider than the requirement.

B. Given a quote with a total value of $50,000 or more, when a sales rep submits it for approval, then the quote goes through a two-step approval that needs sign-off from both the regional sales director and the VP of Finance before it can be sent to the customer. ✓Correct. It covers the precondition (total of $50,000 or more), the trigger (rep submits for approval) and the expected behavior (sequential approval by the regional director and the VP of Finance). It is specific, testable and implementation-neutral.

C. Given a quote submitted with a discount, when the total goes past company limits, then an approval workflow starts.Incorrect. The rule concerns quote total, not discounts, and 'company limits' is undefined and cannot be tested.

D. Given that the VP of Finance and the regional director are both available, when a large quote is submitted, then they get an email asking them to approve it.Incorrect. Approver availability is not a valid precondition, and 'large quote' is not a defined threshold, so the criterion cannot be tested.

Why: Good Given/When/Then criteria name the exact threshold, are triggered by a user action (the When) and describe an observable outcome (the Then) without dictating the technical build. The right option captures the threshold, the trigger and the dual-approval result precisely.

Find out if you're ready to pass

Take the free Business Analyst diagnostic: 20 questions, no account needed. Then unlock all 180 questions, full practice exams and the study guide.

Start the free diagnostic See plans

Business Analyst practice questions: User Stories

A BA at a packaging manufacturer reviews the acceptance criteria on a Salesforce Sales Cloud opportunity story, which say: 'The system should allow sales reps to create opportunities.' A tester reports being unable to tell whether this passes or fails. What change should the BA make?

A footwear retailer is wrapping up a Sales Cloud rollout, and the BA must judge whether the original business goals were met. The goals were 'Cut sales rep data entry time by 30%' and 'Give regional managers better pipeline visibility.' How should the BA evaluate them?

A camping supplies company adds a rule: 'Any quote totaling more than $50,000 needs approval from both the regional sales director AND the VP of Finance.' The BA is writing Given/When/Then acceptance criteria for the story. Which criterion BEST expresses this rule?

Find out if you're ready to pass

Other sections of this exam