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

PMI-PBA Exam - Topic 7 Question 92 Discussion

Actual exam question for PMI's PMI-PBA exam
Question #: 92
Topic #: 7
[All PMI-PBA Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

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


by Arthur at Oct 23, 2024, 04:00 PM

Limited Time Offer

25%

Off

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Tomas
3 months ago
Use case packages can really help in aligning the interface with user processes!
upvoted 0 times
...
Tammi
3 months ago
Documenting business data objects is important too, but not the main focus here.
upvoted 0 times
...
Charolette
3 months ago
Not sure a prototype is enough to address all concerns though.
upvoted 0 times
...
Clarinda
4 months ago
Definitely agree, prototypes help clarify requirements!
upvoted 0 times
...
Carmen
4 months ago
I think developing a prototype is key to understanding user needs.
upvoted 0 times
...
Bulah
4 months ago
Documenting business data objects sounds important, but I don’t see how that directly addresses the user’s concerns about the new interface.
upvoted 0 times
...
Adelaide
4 months 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.
upvoted 0 times
...
Lynsey
4 months 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.
upvoted 0 times
...
Timothy
5 months 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?
upvoted 0 times
...
Ardella
5 months 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.
upvoted 0 times
...
Quentin
5 months 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.
upvoted 0 times
...
Karl
5 months 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.
upvoted 0 times
...
Leslee
5 months 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.
upvoted 0 times
...
Octavio
1 year 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)
upvoted 0 times
Jerrod
1 year ago
D) Document the business data objects using an entity relationship diagram.
upvoted 0 times
...
Pansy
1 year ago
C) Develop a use case package to support the user interface.
upvoted 0 times
...
Keith
1 year ago
B) Develop a prototype to gather functional requirements.
upvoted 0 times
...
Willow
1 year ago
A) Consult the stakeholder register to evaluate if the user has authority to influence the project.
upvoted 0 times
...
...
Rosalia
1 year 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)
upvoted 0 times
...
Muriel
1 year 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)
upvoted 0 times
Ora
1 year ago
Buffy: Yeah, that sounds like a good plan. Who needs end user feedback anyway, right? (laughs)
upvoted 0 times
...
Lorita
1 year ago
User 3: I agree, forget the prototype. Let's go with the use case package for all the functional requirements.
upvoted 0 times
...
Buffy
1 year ago
User 2: Developing a use case package might be a better option to support the user interface.
upvoted 0 times
...
Nina
1 year ago
User 1: I think we should consult the stakeholder register to see if the user has authority to influence the project.
upvoted 0 times
...
...
Golda
1 year 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.
upvoted 0 times
Delisa
1 year ago
C: Agreed. It's important to ensure the new interface supports their core business processes.
upvoted 0 times
...
Julian
1 year ago
B: That's a good idea. It will help gather functional requirements and address their concerns.
upvoted 0 times
...
Frederick
1 year ago
A: Let's involve the end users in the design process by developing a prototype.
upvoted 0 times
...
...
Judy
1 year 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.
upvoted 0 times
Elena
1 year ago
User 4: Developing a prototype seems like the best approach to make sure the new interface meets the end user's needs.
upvoted 0 times
...
Corazon
1 year ago
User 3: I agree. Getting real-time feedback through a prototype would be beneficial in addressing their concerns.
upvoted 0 times
...
Monte
1 year ago
User 2: That's a good point. It would help us ensure the new interface aligns with the end user's core processes.
upvoted 0 times
...
Fanny
1 year ago
User 1: We should definitely consider developing a prototype to gather functional requirements.
upvoted 0 times
...
...
Richelle
1 year ago
I agree with you, Giuseppe. Developing a prototype would help address the end user's concerns effectively.
upvoted 0 times
...
Giuseppe
1 year ago
I think the business analyst should develop a prototype to gather functional requirements.
upvoted 0 times
...

Save Cancel