PMI Professional in Business Analysis PMI-PBA Updated Exam

Communication is an essential part of requirements management, as it ensures that the requirements are clear, consistent, and agreed upon by all the project stakeholders. Stakeholders are the individuals or groups who have an interest or influence in the project, and who can provide input, feedback, and approval for the requirements. Communication also helps to avoid surprises, misunderstandings, and conflicts among the stakeholders, and to manage their expectations and satisfaction. Communication should be timely, accurate, relevant, and transparent, and should follow the communication plan and strategy defined in the requirements management plan12.

One of the aspects of communication is the status of the requirements, which indicates the progress and completion of the requirements throughout the project life cycle. The status of the requirements can be tracked and documented using a traceability matrix, which is a tool that links the requirements to their sources and traces them throughout the project. The status of the requirements can also be monitored and controlled using a change control process, which is a process that evaluates, approves, and implements any changes to the requirements. The status of the requirements can have different values, such as proposed, approved, implemented, verified, deferred, deleted, or rejected12.

When the status of a requirement changes, it should be communicated to all the project stakeholders, not just the source of the requirement or the project team. This is because the change in the status of a requirement may have an impact on the scope, schedule, cost, quality, or risk of the project, and may affect the interests or expectations of the stakeholders. Communicating the status of the requirements to all the project stakeholders helps to keep them informed and engaged, and to obtain their feedback and approval. It also helps to prevent surprises, such as the one experienced by the major stakeholder in the question, who was unaware that a particular requirement was deferred12.

Therefore, the best option is C. The status should have been communicated to all project stakeholders. Option A is not the best option, because the status should have been communicated to more than just the requirement’s source. Option B is not the best option, because the status should have been communicated earlier than prior to project launch. Option D is not the best option, because updating the status in the traceability matrix is not enough, as the stakeholders may not have access to or awareness of the matrix. References: 1 PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 9-11; 2 Requirements Management 101 | Smartsheet 2

The business analyst should check the traceability matrix to identify affected use cases. A traceability matrix can help the business analyst to find out which use cases are related to the new set of regulations, and how they will impact the scope, schedule, cost, quality, and risk of the project. The business analyst should also communicate the changes to the relevant stakeholders, and update the requirements documentation and the business analysis plan accordingly. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 100.

 Stakeholder analysis is a process of identifying and analyzing the stakeholders who have an interest or influence on the project and its outcomes. Stakeholder analysis helps to ensure that the requirements are elicited from all relevant sources and that the stakeholders are appropriately engaged throughout the project. By identifying the user from a department that did not participate in the requirements analysis as a stakeholder, the business analyst could have avoided the situation of logging a defect during user acceptance testing and minimized the impact on the project. Interviewing the user to understand how the user’s work would be impacted, involving the user in the development and sign-off of the business requirements, and giving the user the opportunity to review the user acceptance test scripts are possible actions that could be taken after identifying the user as a stakeholder, but they are not sufficient to avoid the situation and minimize the impact on the project. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 9; Business Analysis for Practitioners: A Practice Guide2, page 55.

A questionnaire is an elicitation technique that involves sending a set of written questions to a large number of users or stakeholders to gather information about their needs, preferences, opinions, or feedback. A questionnaire is best suited for eliciting information from a large group of users in a short period of time, as it is cost-effective, easy to administer, and allows for anonymity and standardization. A questionnaire can also reach users who are geographically dispersed or unavailable for face-to-face meetings. References: PMI Guide to Business Analysis, Chapter 6, Section 6.3.2.9; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain III: Analysis, Task 2.