MENU
At the start of a new Agile development project, the Universal Containers' product owner asked the business analyst (BA) to clearly define the intended results of the work based on stakeholder needs. The development and implementation teams will use the intended results to plan product decisions. The definition should avoid assumptions and focus on stakeholder value.
Which element should the BA choose to define the intended results?
Suggested Answer: B
Get Premium Salesforce Certified Business Analyst (BA-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The performance analyzer is a tool that helps business analysts and admins identify and troubleshoot performance issues on record pages. It shows the load time of each component on a record page and provides recommendations to improve performance. The first step to resolve the issue is to use the performance analyzer to view the assessment and identify the slowest components.
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/optimize-performance
https://help.salesforce.com/s/articleView?id=sf.performance_analyzer.htm&type=5
36 comments · newest first
SH
Sharee
11 months ago
Agreed, user stories focus on value and avoid assumptions!
DA
Darrin
11 months ago
Wait, are we sure user stories are the best choice here?
VA
Van
12 months ago
Requirements are too rigid for Agile, user stories all the way!
LE
Lettie
12 months ago
I think epics are better for defining high-level goals.
KA
Kayleigh
1 year ago
Definitely user stories, they capture stakeholder needs well.
GE
Georgiana
1 year ago
I'm a bit confused; I thought requirements were the way to go, but now I'm leaning towards user stories after reviewing some examples.
LA
Lashaun
1 year ago
Epics could work too, but they seem more high-level. I feel like user stories are more specific to what stakeholders want.
EV
Eveline
1 year ago
I remember practicing a question like this, and I think requirements might be too broad for defining intended results.
YO
Yolande
1 year ago
I think the BA should go with user stories since they focus on stakeholder needs and value. But I'm not entirely sure if that's the best choice.
UL
Ula
1 year ago
User stories seem like the best fit to me. They allow the BA to define the intended results from the stakeholder's perspective, without getting bogged down in technical details.
TO
Tonette
1 year ago
Requirements might be the right answer here, as they provide a more comprehensive definition of the intended results. But I'll need to double-check how that compares to user stories and epics.
VA
Valentin
1 year ago
Okay, I think I've got this. The BA should choose user stories to define the intended results, as they capture the stakeholder's needs in a concise, value-focused way.
ID
Idella
1 year ago
Hmm, I'm a bit unsure here. The question mentions avoiding assumptions and focusing on stakeholder value, so I'll need to carefully consider which option best aligns with that guidance.
LI
Lili
1 year ago
This seems like a straightforward question about Agile project management. I'll focus on identifying the key elements that define the intended results based on stakeholder needs.
DE
Denae
1 year ago
Hmm, this looks like a classic weighted-ranking matrix question. I'll need to carefully review the criteria and scores to determine the best solution.
DA
Daniel
1 year ago
Ah, the age-old battle of user stories vs. epics. It's like choosing between a cup of coffee or an entire coffee plantation. Either way, you're going to get a caffeine buzz, am I right?
BE
Belen
1 year ago
A: User stories are more detailed and focused on specific user needs
AL
Alyssa
1 year ago
B: Epics
ST
Stefanie
1 year ago
A: User stories
DE
Deandrea
2 years ago
User stories all the way! They're like the MVP of requirements - just the essential bits to get the job done. And they're way more fun to write than those dry old requirements.
TH
Theron
1 year ago
Absolutely, user stories help us stay agile and adapt to changing stakeholder needs more easily.
HE
Herminia
1 year ago
User stories are great for breaking down the work into manageable chunks and keeping the focus on stakeholder value.
LA
Lashon
1 year ago
I agree, user stories are more user-friendly and easier to understand compared to traditional requirements.
AH
Ahmad
2 years ago
User stories are definitely the way to go. They help us focus on what really matters to the stakeholders.
SH
Shad
2 years ago
I think epics would be the best option, as they provide a high-level overview of the project goals.
TR
Trinidad
2 years ago
Requirements? Really? That's way too detailed and specific for this scenario. The BA needs to keep it high-level and focus on stakeholder value, so user stories are the way to go.
AM
Amie
2 years ago
User 2: Agreed, user stories are more high-level and focus on stakeholder value.
LE
Leana
2 years ago
User 1: User stories
FI
Fidelia
2 years ago
I think epics would be the best choice here. Epics provide a high-level overview of the project's objectives, which aligns with the need to define the intended results based on stakeholder needs.
LE
Leonie
2 years ago
I disagree, I believe requirements would be a better choice for defining the intended results.
KA
Kaitlyn
2 years ago
I think the BA should choose user stories to define the intended results.
AL
Alecia
2 years ago
The BA should choose user stories to define the intended results. User stories focus on stakeholder value and avoid assumptions, which is exactly what the question requires.
RO
Roslyn
2 years ago
User stories focus on stakeholder value and avoid assumptions.
MA
Mauricio
2 years ago
C) Epics
TE
Tennie
2 years ago
B) User stories
TA
Tayna
2 years ago
A) Requirements