MENU
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?
21 comments · newest first
HI
Hildred
11 months ago
They should focus on user needs, not just tech stuff.
IL
Iluminada
11 months ago
I disagree, they shouldn't be fixed after approval.
RE
Remona
11 months ago
Totally agree, iterative is the way to go!
ME
Melita
11 months ago
Wait, are user stories really that flexible?
KA
Katie
11 months ago
User stories definitely help with iterative development!
JE
Jean
12 months ago
I recall that user stories help teams understand what users want, which aligns with option A about iterative development.
DA
Daniel
12 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.
TA
Tawny
1 year 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?
AN
Annamae
1 year ago
I remember that user stories are meant to be flexible and encourage iterative development, so I think option A makes sense.
JE
Jettie
1 year 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.
RO
Roxane
1 year 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.
LA
Laurena
1 year 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.
CO
Corinne
1 year ago
This seems like a pretty straightforward question about user stories. I'm pretty confident I can handle this one.
LA
Latonia
1 year ago
B is incorrect. User stories focus on the user's perspective, not technical components. The BA needs to keep that in mind.
LI
Lizbeth
1 year ago
Yes, it's important to consider the technical aspects when writing user stories.
BE
Ben
1 year ago
User stories encourage iterative development, which is crucial for this cross-functional project. The BA should keep that in mind during the workshop.
LA
Lajuana
1 year ago
B) User stories specify which technical components are impacted.
BR
Bronwyn
1 year ago
A) User stories encourage iterative development.
GE
Genevive
1 year ago
B) User stories specify which technical components are impacted.
KI
Kiley
1 year ago
That's true, user stories help in breaking down the project into manageable chunks.
LI
Lizbeth
1 year ago
A) User stories encourage iterative development.