The business analyst is planning an approach to formally manage updates to requirements that may
be requested by stakeholders.
What should the business analyst do?
A
Explanation:
A change control process is a set of procedures that defines how changes to the requirements are
identified, assessed, approved, implemented, and communicated. A change control process helps to
ensure that changes are aligned with the business objectives, do not introduce unnecessary risks,
and do not adversely affect the quality of the solution.
A change control process also helps to
manage stakeholder expectations and avoid scope creep. Reference: PMI Professional in Business
Analysis (PMI-PBA)® Examination Content Outline1, page 13; Business Analysis for Practitioners: A
Practice Guide2
, page 77.
Company A has set aside capital to invest in an upgrade to their scheduling system. Documentation
of the current structure was presented to the business analyst. However, the description of certain
steps is not documented clearly, and the business analyst has not been allowed to inspect the
existing system. During elicitation, the business analyst asked questions of the schedulers as they
performed functions in order to gain an understanding of the process.
Which type of elicitation technique did the business analyst use in this instance?
A
Explanation:
Active observation is an elicitation technique that involves observing the work performed by
stakeholders in their own environment and asking questions to clarify or confirm the understanding
of the process. Active observation allows the business analyst to gain insights into the current state,
identify gaps or issues, and discover undocumented or implicit requirements. Active observation is
different from participatory observation, which involves performing the work alongside the
stakeholders, and from interview, which involves asking structured or unstructured questions to elicit
information from stakeholders.
Simulation is an elicitation technique that involves creating a model
or a prototype of the solution or a part of it and using it to elicit feedback from
stakeholders. Reference: PMI Professional in Business Analysis (PMI-PBA)® Examination Content
Outline1, page 10; Business Analysis for Practitioners: A Practice Guide2
, page 62.
A system enhancement project has been initiated to address the concerns of an external group of
stakeholders not included in the first release. What should be done to ensure stakeholder satisfaction
with the enhancement?
C
Explanation:
Engaging all stakeholders early in the requirements gathering phase is a good practice to ensure
stakeholder satisfaction with the enhancement. By involving the stakeholders in the elicitation
process, the business analyst can understand their needs, expectations, preferences, and constraints.
By defining the acceptance criteria with the stakeholders, the business analyst can establish a clear
and measurable definition of what constitutes a successful solution. Engaging all stakeholders early
can also help to build trust, collaboration, and buy-in for the change. Requesting that the project
manager identify all affected project stakeholders is not sufficient to ensure stakeholder satisfaction,
as it does not involve direct communication with the stakeholders. Providing all signed-off project
documentation to the stakeholders for information purposes only is not effective, as it does not allow
for feedback or validation from the stakeholders.
Soliciting feedback and adding requirements to the
project backlog is not advisable, as it can lead to scope creep, rework, and delays. Reference: PMI
Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 11; Business
Analysis for Practitioners: A Practice Guide2
, page 66.
A project team delivers a solution based on the approved requirements and is confident that it meets
the defined acceptance criteria.
What should the business analyst do to obtain signoff?
D
Explanation:
A RACI matrix is a tool that defines the roles and responsibilities of stakeholders in a project or a
process. It clarifies who is Responsible, Accountable, Consulted, and Informed for each task or
deliverable. The business analyst should refer to the RACI matrix to identify who is responsible for
signoff, as this person has the authority and accountability to approve the solution and its testing
results. Contacting the sponsor, the stakeholder who provided the majority of requirements, or the
project manager may not be appropriate, as they may not be the designated person for signoff
according to the RACI matrix.
No signoff is necessary is incorrect, as signoff is an important step to
confirm that the solution meets the requirements and acceptance criteria. Reference: PMI
Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 13; Business
Analysis for Practitioners: A Practice Guide2
, page 77.
Which tool can be used to analyze how the system responds to various combinations of input
conditions with the probability of each outcome?
A
Explanation:
A decision tree is a tool that can be used to analyze how the system responds to various
combinations of input conditions with the probability of each outcome. A decision tree is a graphical
representation of a decision problem that shows the possible choices and their consequences. A
decision tree can help to evaluate the expected value of each alternative and choose the optimal
one. Functional decomposition is a tool that can be used to break down a complex system or process
into smaller and simpler components. Expected monetary value is a tool that can be used to
calculate the average outcome of a decision under uncertainty by multiplying the value of each
outcome by its probability and summing them up.
Weighted criteria is a tool that can be used to
prioritize requirements or alternatives based on their importance and performance
scores. Reference: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1,
page 15; Business Analysis for Practitioners: A Practice Guide2
, page 95.
Testing on a project has been completed. In order to proceed with deployment, a decision is needed.
Who should the business analyst contact to review the testing results and get approval to proceed
with deployment?
B
Explanation:
The person identified in the RACI matrix as accountable for deployment approval is the one who
should be contacted by the business analyst to review the testing results and get approval to proceed
with deployment. The RACI matrix defines who is Responsible, Accountable, Consulted, and
Informed for each task or deliverable in a project or a process. The accountable person has the
authority and accountability to approve or reject the work. The tester identified in the testing
strategy is not necessarily the one who can approve deployment, as they may only be responsible for
conducting testing. The project manager identified in the project charter may not have the authority
to approve deployment, as they may only be responsible for managing the project. The project
sponsor identified in the scope document may not be involved in deployment approval, as they may
only be informed of the project progress and outcomes.
During user acceptance testing, a defect is logged by a user from a department that did not
participate in the requirements analysis. To avoid this situation and minimize impact on the project,
the user should have been:
C
Explanation:
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. Reference: PMI Professional in Business Analysis (PMI-PBA)® Examination
Content Outline1, page 9; Business Analysis for Practitioners: A Practice Guide2
, page 55.
A project team has completed the system use cases along with accompanying screen mockups. The
business analyst schedules a review meeting with the client team to walk through the artifacts.
What is the purpose of this meeting?
C
Explanation:
The purpose of reviewing the system use cases and screen mockups with the client team is to
validate that the system is aligned with the stakeholder requirements. Validation is a process of
ensuring that the solution meets the needs and expectations of the stakeholders and delivers value
to them. Validation involves checking whether the solution is feasible, acceptable, complete, correct,
consistent, and testable. By walking through the artifacts with the client team, the business analyst
can obtain feedback, confirm understanding, identify gaps or errors, and resolve issues. Verifying
that the documents are aligned with the transition requirements or the solution requirements are
possible outcomes of the review meeting, but they are not the main purpose.
Verifying that the
system is aligned with the quality requirements is not relevant to this scenario, as quality
requirements are related to how well the solution performs rather than what it does. Reference: PMI
Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 13; Business
Analysis for Practitioners: A Practice Guide2
, page 76.
A type of requirements document that would be the most valuable to a database administrator
would be:
C
Explanation:
An entity relationship diagram (ERD) is a type of requirements document that would be most
valuable to a database administrator. An ERD is a graphical representation of data entities and their
relationships in a database. An ERD shows how data is organized, stored, accessed, and manipulated
in a database. An ERD can help to design, document, and communicate a database schema. A data
flow diagram (DFD) is a graphical representation of how data flows through a system or a process. A
DFD shows where data comes from, where it goes, how it is transformed, and what it is used for. A
DFD can help to analyze, design, or improve a system or a process. A business process diagram (BPD)
is a graphical representation of how activities are performed by actors in a business process. A BPD
shows who does what, when, where, why, and how in a business process. A BPD can help to model,
document, or optimize a business process. An object diagram is a graphical representation of objects
and their relationships in an object-oriented system. An object diagram shows how objects interact
with each other through messages or operations.
An object diagram can help to illustrate or test an
object-oriented design. Reference: PMI Professional in Business Analysis (PMI-PBA)® Examination
Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2
, page 95.
A company is working on the next big release of their best-selling product. The requirements will be
validated through in-person validation sessions.
What would be the most viable technique to use in this scenario?
B
Explanation:
A review of the solution prototype would be the most viable technique to use in this scenario for
validating requirements through in-person sessions. A solution prototype is a simplified version of
part or all of a solution that can be used to elicit feedback from stakeholders. A review of a solution
prototype involves presenting or demonstrating it to stakeholders and asking them questions to
assess their satisfaction, understanding, agreement, or concerns. A review of a solution prototype
can help to validate that the solution meets the stakeholder requirements and delivers value to
them. A brainstorming session is a technique for generating ideas or solutions by encouraging free
and creative thinking from participants. A brainstorming session can help to elicit or analyze
requirements but not validate them. A use-case development session is a technique for creating use
cases that describe how actors interact with a system to achieve their goals. A use-case development
session can help to elicit or specify requirements but not validate them. A review of the previous
version is a technique for examining an existing solution or product to identify its strengths,
weaknesses, opportunities, or threats.
A review of the previous version can help to elicit or analyze
requirements but not validate them. Reference: PMI Professional in Business Analysis (PMI-PBA)®
Examination Content Outline1, page 13; Business Analysis for Practitioners: A Practice Guide2
, page
76.
A sponsor requests a new requirement. The business analyst explains that most of the information
needed for this requirement does not exist and that the requirement cannot be implemented. The
business analyst recommends deferring the requirement until the needed information is available
and then adding it to a subsequent project. The sponsor agrees.
What should the business analyst do next?
C
Explanation:
The business analyst should communicate that the status of this requirement has changed to the
relevant stakeholders, such as the project manager, the sponsor, the development team, and the
quality assurance team. Communication is an essential skill for business analysts, as it helps to
ensure that everyone involved in the project is aware of the current state of the requirements, the
rationale behind any changes, and the impact of those changes on the project scope, schedule,
budget, quality, and risks. Communication also helps to manage stakeholder expectations and avoid
confusion or conflicts. Bringing the subsequent project to the change control board (CCB) is not
necessary at this stage, as the requirement has been deferred and not added to another project.
Asking the stakeholders to review the requirement before any other action is taken is not effective,
as the requirement cannot be implemented until the needed information is available.
Marking the
requirement as complete so that it is not forgotten is incorrect, as it does not reflect the true status
of the requirement and may cause errors or inconsistencies in the requirements documentation and
traceability. Reference: PMI Professional in Business Analysis (PMI-PBA)® Examination Content
Outline1, page 13; Business Analysis for Practitioners: A Practice Guide2
, page 77.
A company is pleased with its delivered solution and reports that it has heard only minimal
complaints for the first three months of use.
How can the business analyst determine how well the solution meets the business case?
A
Explanation:
A user survey is a technique that can be used to determine how well the solution meets the
business case. A user survey is a method of collecting feedback from the end users of the solution
about their satisfaction, preferences, expectations, needs, problems, or suggestions. A user survey
can help to measure the performance, quality, usability, and value of the solution and compare it
with the expected benefits and outcomes defined in the business case. A user survey can also help to
identify areas for improvement or enhancement of the solution. Asking the sponsor for feedback is
not sufficient to determine how well the solution meets the business case, as it does not capture the
perspective of the end users who are directly affected by the solution. Surveying the project is not
relevant to this scenario, as it does not focus on the solution but rather on the project management
processes and practices.
Comparing the results of day-in-the-life (DITL) testing and integration
testing is not effective, as it does not reflect the actual usage and experience of the solution by the
end users after deployment. Reference: PMI Professional in Business Analysis (PMI-PBA)®
Examination Content Outline1, page 14; Business Analysis for Practitioners: A Practice Guide2
, page
80.
A business analyst is working on a project to implement a new call management system for a help
desk. They expected the average time interval to answer a call to decrease over time, but the interval
has increased instead.
Which technique should the business analyst use to investigate the problem?
B
Explanation:
Root cause analysis (RCA) is a technique that can be used to investigate the problem of increased
call interval in a new call management system. Root cause analysis is a method of identifying and
resolving the underlying causes of a problem or an issue, rather than treating the symptoms or the
effects. Root cause analysis involves asking questions, collecting data, analyzing evidence, finding
patterns, drawing conclusions, and recommending solutions. Root cause analysis can help to prevent
recurrence of the problem, improve performance, reduce risks, and increase customer satisfaction.
Interviews are a technique that can be used to elicit information from stakeholders, but they may not
be sufficient to investigate the problem in depth and find its root causes. Observation is a technique
that can be used to understand how stakeholders perform their work in their own environment, but
it may not be able to explain why the problem occurs and what causes it.
Process modeling is a
technique that can be used to represent how activities are performed in a process, but it may not be
able to identify and resolve the problem in the process. Reference: PMI Professional in Business
Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A
Practice Guide2
, page 95.
The software developers have delivered a completed solution. The quality assurance team has
passed the solution. What should the business analyst do next?
B
Explanation:
User acceptance testing (UAT) is a process that should be done by the business analyst after the
software developers have delivered a completed solution and the quality assurance team has passed
it. User acceptance testing is a process of verifying that the solution meets the requirements and
expectations of the end users and delivers value to them. User acceptance testing involves preparing
test cases, scenarios, or scripts based on the acceptance criteria, executing them with representative
users or stakeholders, collecting feedback, identifying defects or issues, and obtaining sign-off or
approval for deployment. User acceptance testing can help to ensure that the solution is fit for use,
suitable for purpose, and aligned with business objectives. Evaluating the solution against the project
charter is not necessary at this stage, as it does not involve testing or validation by the end users or
stakeholders. Evaluating the solution with the sponsor(s) is not sufficient at this stage, as it does not
capture the perspective of all relevant users or stakeholders who will use or benefit from the
solution.
Conducting performance testing is not relevant at this stage, as it is usually done by the
quality assurance team before delivering the solution to ensure that it meets the non-functional
requirements such as speed, reliability, scalability, etc. Reference: PMI Professional in Business
Analysis (PMI-PBA)® Examination Content Outline1, page 14; Business Analysis for Practitioners: A
Practice Guide2
, page 80.
A company’s management team has decided to deploy a new product. However, there is concern
that users may not accept a new product that forces them to change existing practices.
The business analyst should:
C
Explanation:
The business analyst should clearly communicate project objectives and attempt to defuse tensions
when there is concern that users may not accept a new product that forces them to change existing
practices. Communication is a key skill for business analysts, as it helps to ensure that stakeholders
understand the purpose, scope, benefits, and risks of the project and the solution. Communication
also helps to manage stakeholder expectations, address their concerns, resolve conflicts, and gain
their support and buy-in for the change. By communicating project objectives and trying to defuse
tensions, the business analyst can demonstrate the value of the new product, explain the rationale
behind the change, listen to the feedback and suggestions of the users, and foster a positive and
collaborative relationship with them. Adhering to the project plan to achieve project objectives is not
sufficient, as it does not address the user resistance or dissatisfaction with the new product. Voicing
user concerns to management and recommending that the project be closed is not advisable, as it
may undermine the project success and waste the resources invested in it.
Delaying the application’s
deployment until the conflicts have been resolved is not effective, as it may cause delays, rework, or
scope creep in the project. Reference: PMI Professional in Business Analysis (PMI-PBA)® Examination
Content Outline1, page 9; Business Analysis for Practitioners: A Practice Guide2
, page 55.