CBAP · Question #300
Holly is the business analyst for her organization. Holly encourages teamwork and open communications among the business analysis team and the stakeholders. She wants stakeholders to drop by her offic
The correct answer is C. Stakeholders may miss information and the requirements could become ambiguous.. Informal communications lack the structure and documentation trail needed to ensure all stakeholders receive consistent information, creating a risk of ambiguous requirements and critical gaps.
Question
Holly is the business analyst for her organization. Holly encourages teamwork and open communications among the business analysis team and the stakeholders. She wants stakeholders to drop by her office and freely discuss the requirements, the solution scope, and other concerns about the solution she's working on. Holly definitely prefers informal communications. What is the danger Holly may experience with informal communications?
Options
- AThere is no danger; informal communications is a preferred business analysis technique.
- BThe stakeholders may address the business analysis team and the project team directly
- CStakeholders may miss information and the requirements could become ambiguous.
- DThe stakeholders may not know who's in charge of the solution.
How the community answered
(37 responses)- A3% (1)
- B8% (3)
- C73% (27)
- D16% (6)
Why each option
Informal communications lack the structure and documentation trail needed to ensure all stakeholders receive consistent information, creating a risk of ambiguous requirements and critical gaps.
Informal communications carry a genuine and well-recognized risk in business analysis - the absence of documentation can cause requirements to be lost, misunderstood, or inconsistently communicated across stakeholder groups.
Stakeholders and team members communicating directly is generally encouraged in collaborative environments and is not the primary danger of informal communications.
Without formal documentation, stakeholders who are not present for an informal conversation will miss information that was discussed, and there is no written record to resolve conflicting interpretations later. This inconsistency directly leads to ambiguous requirements and a weaker requirements baseline, which can cause solution defects or rework downstream.
Roles, authority, and ownership of a solution are established through formal project governance artifacts such as a RACI matrix or project charter, not through the communication style chosen by the business analyst.
Concept tested: Risks of informal communication in requirements elicitation
Topics
Community Discussion
No community discussion yet for this question.