New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Business Analyst (BA-201) Exam - Topic 5 Question 46 Discussion

Actual exam question for Salesforce's Salesforce Certified Business Analyst (BA-201) exam
Question #: 46
Topic #: 5
[All Salesforce Certified Business Analyst (BA-201) Questions]

Northern Tail Outfitters has fixed a business analyst (BA to help revamp the order management process. During the backlog regiment session, the BA discovers the few user satires are no longer needed.

What should the BA do next?

Show Suggested Answer Hide Answer
Suggested Answer: C

This answer states that reviewing these user stories in the backlog at the next sprint retrospective is what the BA should do next after discovering that a few user stories are no longer needed for revamping the order management process at NTO. User stories are short descriptions of a feature or a functionality from a user's perspective. Backlog is a list of user stories that need to be prioritized and completed for a project or a product. Sprint retrospective is a meeting or a workshop where the project team reviews and reflects on their performance and progress in the previous sprint. Reviewing these user stories in the backlog at the next sprint retrospective means that the BA discusses and evaluates these user stories with the project team to determine if they are still relevant, valuable, or feasible for revamping the order management process. Reviewing these user stories in the backlog at the next sprint retrospective is what the BA should do next after discovering that a few user stories are no longer needed because it helps the BA to update and maintain the backlog, and to ensure that the user stories align with the project scope and goals. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements


by Mitsue at Aug 22, 2024, 10:55 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Business Analyst (BA-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Janine
3 months ago
Reviewing them later could be useful, just in case.
upvoted 0 times
...
Twana
3 months ago
Moving them to the bottom seems like a waste of time.
upvoted 0 times
...
Queen
3 months ago
Wait, are we sure they’re really not needed?
upvoted 0 times
...
Shenika
4 months ago
Totally agree, no point in keeping them!
upvoted 0 times
...
Julie
4 months ago
I think the BA should just cancel those user stories.
upvoted 0 times
...
Craig
4 months ago
I’m leaning towards option A, but I wonder if there’s a chance those user stories could be relevant later on.
upvoted 0 times
...
Svetlana
4 months ago
Reviewing them at the next sprint retrospective could be useful, but I feel like that might just delay the process.
upvoted 0 times
...
Yaeko
4 months ago
I remember a practice question where we had to prioritize user stories, and moving them to the bottom of the backlog seemed like a safe option.
upvoted 0 times
...
Nydia
5 months ago
I think the BA should probably cancel the user stories since they’re no longer needed, but I’m not entirely sure if that’s the best approach.
upvoted 0 times
...
Myra
5 months ago
I think the key here is that the BA has discovered these user stories are no longer needed. In that case, the best approach is to just cancel them and remove them from the backlog entirely, as option A suggests. No need to complicate things by moving them or reviewing them later.
upvoted 0 times
...
Zena
5 months ago
Option B doesn't make much sense to me. Why would we want to just move the unnecessary stories to the bottom of the backlog? Seems like a waste of time. I'm leaning towards A or C, but I'll need to re-read the question to make sure I fully understand it.
upvoted 0 times
...
Frederica
5 months ago
Hmm, I'm a bit unsure about this one. I'm torn between A and C. Canceling the stories might be the cleanest approach, but reviewing them at the next retrospective could also be valuable. I'll have to think this through carefully.
upvoted 0 times
...
Loreta
5 months ago
This seems like a straightforward question about managing the backlog. I'd go with option A - canceling the user stories that are no longer needed and removing them from the backlog.
upvoted 0 times
...
Sherita
5 months ago
This question seems straightforward, but I want to make sure I understand the logic correctly before selecting an answer.
upvoted 0 times
...
Dorathy
1 year ago
Ah, the age-old dilemma of the unnecessary user story. I say we just give them a little nudge to the bottom of the backlog and let them simmer. You never know when they might come back to haunt us.
upvoted 0 times
Lashawnda
1 year ago
No need to cancel them, just let them stay at the bottom for now.
upvoted 0 times
...
Anglea
1 year ago
I think we should review them in the next sprint retrospective.
upvoted 0 times
...
Shawn
1 year ago
Agreed, it's better to keep them there just in case.
upvoted 0 times
...
Lenna
1 year ago
Let's just move those unnecessary user stories to the bottom of the backlog.
upvoted 0 times
...
...
Rosalind
1 year ago
I agree with Felton, it's important to review them before making any decisions.
upvoted 0 times
...
Dyan
1 year ago
Cancel the user stories? What is this, the dark ages? The BA should definitely review them during the next retrospective. You never know when those 'no longer needed' stories might come in handy.
upvoted 0 times
Jettie
1 year ago
C) Review these user stories in the backlog at the next sprint retrospective.
upvoted 0 times
...
Jerry
1 year ago
A) Cancel these user stories and remove them from the backlog.
upvoted 0 times
...
...
Felton
1 year ago
I disagree, I believe the BA should review those user stories in the backlog at the next sprint retrospective.
upvoted 0 times
...
Lewis
2 years ago
I think the BA should cancel those user stories and remove them from the backlog.
upvoted 0 times
...
Brande
2 years ago
Review them at the next sprint retrospective? Nah, that's way too much effort. I say just toss 'em and move on. Who needs user stories anyway, am I right?
upvoted 0 times
Jackie
1 year ago
B) Move these user stories to the bottom of the backlog.
upvoted 0 times
...
Nina
1 year ago
Review them at the next sprint retrospective? Nah, that's way too much effort. I say just toss 'em and move on. Who needs user stories anyway, am I right?
upvoted 0 times
...
Chu
1 year ago
A) Cancel these user stories and remove them from the backlog.
upvoted 0 times
...
...
Rana
2 years ago
Cancel those user stories? Are you kidding me? That's like throwing away perfectly good code. Let's move them to the bottom of the backlog, just in case.
upvoted 0 times
Edelmira
1 year ago
We can always revisit them later if needed.
upvoted 0 times
...
Skye
1 year ago
Moving them to the bottom sounds like a good compromise.
upvoted 0 times
...
Eve
1 year ago
Agreed, we shouldn't just throw away work that has already been done.
upvoted 0 times
...
Cassi
1 year ago
Let's not cancel them, just move them to the bottom of the backlog.
upvoted 0 times
...
...

Save Cancel