MENU
A business analyst is working on a project to update the user interface for a legacy procurement system. An end user raises concerns that the new solution will not support their core business processes.
How could the business analyst address the end user's concerns about the new interface?
Suggested Answer: B
Get Premium PMI-PBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
According to the PMI Professional in Business Analysis objectives and content, a prototype is a tool that can be used to elicit, analyze, and validate requirements. A prototype is a representation of a solution that allows stakeholders to interact with it and provide feedback. By developing a prototype, the business analyst can gather functional requirements from the end user and ensure that the new interface supports their core business processes. A prototype can also help to reduce ambiguity, resolve conflicts, and increase stakeholder satisfaction.References:
PMI Professional in Business Analysis objectives and content:PMI-PBA Certification
PMI Professional in Business Analysis reference list:PBA Reference List
PMI Professional in Business Analysis study guide:PMI.com
35 comments · newest first
TO
Tomas
11 months ago
Use case packages can really help in aligning the interface with user processes!
TA
Tammi
11 months ago
Documenting business data objects is important too, but not the main focus here.
CH
Charolette
12 months ago
Not sure a prototype is enough to address all concerns though.
CL
Clarinda
12 months ago
Definitely agree, prototypes help clarify requirements!
CA
Carmen
1 year ago
I think developing a prototype is key to understanding user needs.
BU
Bulah
1 year ago
Documenting business data objects sounds important, but I don’t see how that directly addresses the user’s concerns about the new interface.
AD
Adelaide
1 year ago
I feel like creating a use case package could be beneficial, but I wonder if it’s enough to alleviate the user's worries about their core processes being supported.
LY
Lynsey
1 year ago
I'm not entirely sure, but I think consulting the stakeholder register might not directly address the user's concerns about the interface itself.
TI
Timothy
1 year ago
I remember we discussed the importance of involving users early in the design process. Developing a prototype could really help clarify their needs, right?
AR
Ardella
1 year ago
I've got a strategy for this. I'll start by checking the stakeholder register to see if this user has any special authority that needs to be considered. Then I'll focus on gathering detailed requirements through a prototype or use case package.
QU
Quentin
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to make sure I fully grasp the user's concerns and how they're tied to the business processes. Documenting the data objects could help provide some context.
KA
Karl
1 year ago
Okay, let's see. I think the key is to really understand the user's requirements and how the new interface will affect their day-to-day work. Developing a prototype could be a good way to get their feedback.
LE
Leslee
1 year ago
This seems like a tricky one. I'll need to carefully consider the user's concerns and how the new interface might impact their core processes.
OC
Octavio
2 years ago
You know, I heard that the best way to address user concerns is to just lock them in a room until they agree with the new interface. Teamwork makes the dream work, right? (chuckles)
JE
Jerrod
2 years ago
D) Document the business data objects using an entity relationship diagram.
PA
Pansy
2 years ago
C) Develop a use case package to support the user interface.
KE
Keith
2 years ago
B) Develop a prototype to gather functional requirements.
WI
Willow
2 years ago
A) Consult the stakeholder register to evaluate if the user has authority to influence the project.
RO
Rosalia
2 years ago
Hold up, the entity relationship diagram is clearly the way to go. I mean, what could be more important than documenting the business data objects? That's the foundation for the whole system! (rolls eyes)
MU
Muriel
2 years ago
Forget the prototype, let's just go with the use case package. That will give us all the functional requirements we need to build the perfect interface. Who needs end user feedback anyway? (laughs)
OR
Ora
2 years ago
Buffy: Yeah, that sounds like a good plan. Who needs end user feedback anyway, right? (laughs)
LO
Lorita
2 years ago
User 3: I agree, forget the prototype. Let's go with the use case package for all the functional requirements.
BU
Buffy
2 years ago
User 2: Developing a use case package might be a better option to support the user interface.
NI
Nina
2 years ago
User 1: I think we should consult the stakeholder register to see if the user has authority to influence the project.
GO
Golda
2 years ago
I agree, the prototype is the best choice here. It's critical to involve the end users in the design process to avoid costly rework down the line.
DE
Delisa
2 years ago
C: Agreed. It's important to ensure the new interface supports their core business processes.
JU
Julian
2 years ago
B: That's a good idea. It will help gather functional requirements and address their concerns.
FR
Frederick
2 years ago
A: Let's involve the end users in the design process by developing a prototype.
JU
Judy
2 years ago
The prototype option seems like a great way to address the end user's concerns. It allows for gathering real-time feedback and ensuring the new interface aligns with their core processes.
EL
Elena
2 years ago
User 4: Developing a prototype seems like the best approach to make sure the new interface meets the end user's needs.
CO
Corazon
2 years ago
User 3: I agree. Getting real-time feedback through a prototype would be beneficial in addressing their concerns.
MO
Monte
2 years ago
User 2: That's a good point. It would help us ensure the new interface aligns with the end user's core processes.
FA
Fanny
2 years ago
User 1: We should definitely consider developing a prototype to gather functional requirements.
RI
Richelle
2 years ago
I agree with you, Giuseppe. Developing a prototype would help address the end user's concerns effectively.
GI
Giuseppe
2 years ago
I think the business analyst should develop a prototype to gather functional requirements.