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

Salesforce Certified Business Analyst (BA-201) Exam - Topic 4 Question 66 Discussion

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

The Salesforce project team at Cloud Kicks is about to start a project that crosses sales and service teams. The business analyst (BA) has been tasked with writing user stories with the teams in a workshop.

What should the BA keep in mind during the process?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Hildred
2 months ago
They should focus on user needs, not just tech stuff.
upvoted 0 times
...
Iluminada
3 months ago
I disagree, they shouldn't be fixed after approval.
upvoted 0 times
...
Remona
3 months ago
Totally agree, iterative is the way to go!
upvoted 0 times
...
Melita
3 months ago
Wait, are user stories really that flexible?
upvoted 0 times
...
Katie
3 months ago
User stories definitely help with iterative development!
upvoted 0 times
...
Jean
3 months ago
I recall that user stories help teams understand what users want, which aligns with option A about iterative development.
upvoted 0 times
...
Daniel
4 months ago
I think I saw a practice question about user stories being fixed after approval, but that seems off. They should evolve as the project progresses, I believe.
upvoted 0 times
...
Tawny
4 months ago
I'm not entirely sure, but I feel like user stories shouldn't get too technical. They focus more on user needs rather than specific components, right?
upvoted 0 times
...
Annamae
4 months ago
I remember that user stories are meant to be flexible and encourage iterative development, so I think option A makes sense.
upvoted 0 times
...
Jettie
4 months ago
I'm a bit confused by the wording of the question. What exactly does the BA need to keep in mind during the user story writing process? I'll have to read through the options carefully to figure out the best answer.
upvoted 0 times
...
Roxane
4 months ago
Okay, the key thing to remember with user stories is that they encourage iterative development, not that they specify technical components or are fixed upon approval. I think A is the way to go on this one.
upvoted 0 times
...
Laurena
5 months ago
Hmm, I'm a little unsure about the differences between the answer choices here. I'll need to think through the key characteristics of user stories to determine the best approach.
upvoted 0 times
...
Corinne
5 months ago
This seems like a pretty straightforward question about user stories. I'm pretty confident I can handle this one.
upvoted 0 times
...
Latonia
5 months ago
B is incorrect. User stories focus on the user's perspective, not technical components. The BA needs to keep that in mind.
upvoted 0 times
...
Lizbeth
5 months ago
Yes, it's important to consider the technical aspects when writing user stories.
upvoted 0 times
...
Ben
6 months ago
User stories encourage iterative development, which is crucial for this cross-functional project. The BA should keep that in mind during the workshop.
upvoted 0 times
Lajuana
5 months ago
B) User stories specify which technical components are impacted.
upvoted 0 times
...
Bronwyn
5 months ago
A) User stories encourage iterative development.
upvoted 0 times
...
...
Genevive
6 months ago
B) User stories specify which technical components are impacted.
upvoted 0 times
...
Kiley
7 months ago
That's true, user stories help in breaking down the project into manageable chunks.
upvoted 0 times
...
Lizbeth
7 months ago
A) User stories encourage iterative development.
upvoted 0 times
...

Save Cancel