PMI-PBA PMI Professional in Business Analysis Questions and Answers

A business requirement is a statement that describes a business need or problem that must be addressed by the project. It should be stated in terms of what the business wants to achieve or improve, not how it will be done. The requirement in the question states a solution (an API) rather than a business need (synchronizing name and address data). It should be revised to focus on the business need and avoid specifying a solution. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 7; Business Analysis for Practitioners: A Practice Guide (2015), page 35.

 According to the PMI Guide to Business Analysis, planning the requirements change process involves defining how requirement changes will be identified, analyzed, approved, and communicated throughout the project life cycle. Communication is a key aspect of managing requirement changes, as it ensures that all stakeholders are aware of the status, impact, and rationale of the changes, and that they can provide their feedback and input. How requirement changes will impact the requirements baseline, how they will be implemented, and how they will impact the validation plan are all important considerations, but they are not part of planning the requirements change process. They are part of executing, monitoring, and controlling the requirements change process. References: PMI Guide to Business Analysis, page 286-287.

A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies the requirements or works correctly. A test case is derived from the requirements and the acceptance criteria, and it specifies the input data, expected output, and execution steps. A test case is incorrect if it does not match the requirements or the acceptance criteria, or if it contains errors, ambiguities, or inconsistencies. If the business analyst receives a test result report that shows evidence of defective functionality, but verifies that the functionality behaves according to the requirements, the business analyst should first verify that the test case is incorrect. This can be done by reviewing the test case, comparing it with the requirements and the acceptance criteria, and identifying any discrepancies or flaws. By verifying that the test case is incorrect, the business analyst can avoid unnecessary changes to the requirements or the solution, and ensure that the test results are valid and reliable. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline3, page 21; Business Analysis for Practitioners: A Practice Guide4, page 101.

 The business analyst should determine if the defect is in the solution developed, in the original requirement, or in the test case. This criterion will help the business analyst to identify the root cause of the defect, and to decide the appropriate response to the defective test result. Depending on the source of the defect, the business analyst may need to revise the requirement, update the test case, or request a change to the solution. The business analyst should also communicate the defect and the response to the relevant stakeholders, and document the discrepancy report accordingly. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 25; Business Analysis for Practitioners: A Practice Guide2, page 140.

A modeling tool integrated into a version control feature that ensures that team knowledge is captured is a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding. A modeling tool is a tool that allows the business analyst to create visual representations of the product needs, such as diagrams, charts, graphs, or mockups. These models can help the stakeholders to comprehend and verify the requirements more easily than textual descriptions. A version control feature is a tool that allows the business analyst to track and manage changes to the models and ensure that they are consistent and accurate. A version control feature also enables collaboration and knowledge sharing among the team members and stakeholders. A requirements management tool that documents requirements and their properties and relationships is not a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding, as it does not provide visual or graphical representations of the product needs. A document management system and a relationship matrix that groups all related documents is not a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding, as it does not create or display models of the product needs. A workflow management tool that documents the flow of information is not a tool that should be used to improve the communication of product needs with the stakeholders and to improve their understanding, as it only focuses on one aspect of the product needs and does not capture other dimensions such as functionality, quality, or value. References: Business Analysis for Practitioners: A Practice Guide 1, page 77-78; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 2, page 16.

The business analyst would recommend formal signoff to the group if errors in the product could result in financial solvency. Formal signoff is a process that ensures that the stakeholders agree on and approve the requirements and deliverables of the project. Formal signoff can help to reduce ambiguity, confusion, or disputes among the stakeholders and increase their accountability and commitment to the project. Formal signoff is especially important when errors in the product could result in financial solvency, as it implies that there is a high level of risk, complexity, or regulation involved in the project and that any mistake or defect could have severe consequences for the organization or its customers. The industry being unregulated is not a reason to recommend formal signoff to the group, as it implies that there is less need for compliance or verification of the product quality or performance. The project impact being contained within a small department of the company is not a reason to recommend formal signoff to the group, as it implies that there is less stakeholder involvement or interest in the project outcome or value. The organization following an iterative project life cycle is not a reason to recommend formal signoff to the group, as it implies that there is more flexibility and adaptability in the project scope and deliverables and that feedback and validation are obtained frequently throughout the project. References: Business Analysis for Practitioners: A Practice Guide 1, page 113-114; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 2, page 17.

 The business analyst will need to use the product scope as an input to the business case. The product scope is the description of the features, functions, and characteristics of the product, service, or result that the project will deliver. The product scope helps to define the business problem or opportunity, the desired outcomes, and the benefits of the solution. The product scope also helps to identify the assumptions, constraints, risks, and dependencies that may affect the project feasibility and viability. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 9; Business Analysis for Practitioners: A Practice Guide2, page 36.

 According to the PMI Guide to Business Analysis, a use case is a technique that describes how an actor interacts with a system or a process to achieve a specific goal. A use case can help to prevent problems from occurring in the implementation of a new application, as it can capture the functional requirements and the expected behavior of the system or the process, as well as the exceptions and alternative flows. A use case can also help to design and execute test cases that cover all the possible scenarios and outcomes. In this case, a use case could have prevented the problem of a worker using a field that was not supposed to be used, as it could have specified the valid inputs and outputs for the report, and the actions and responses of the system or the process. Prototyping, diagrams, and document analysis are other techniques that can help to analyze and communicate requirements, but they do not necessarily prevent problems from occurring in the implementation of a new application, as they do not describe the interactions and outcomes of the system or the process in detail. References: PMI Guide to Business Analysis, page 165-166.

 Operational feasibility is the kind of feasibility assessment that the business analyst is undertaking to understand how well a potential solution fits into the organization. Operational feasibility evaluates how the solution will affect the current operations, processes, culture, and people of the organization. It also considers how the solution will be accepted, adopted, and used by the stakeholders. Technical feasibility is not the kind of feasibility assessment that the business analyst is undertaking, as it evaluates how the solution can be implemented using the available technology, infrastructure, and resources. Cost-effectiveness feasibility is not the kind of feasibility assessment that the business analyst is undertaking, as it evaluates how the solution will provide benefits that outweigh its costs. Time feasibility is not the kind of feasibility assessment that the business analyst is undertaking, as it evaluates how long it will take to implement the solution and whether it can meet the desired schedule. References: Business Analysis for Practitioners: A Practice Guide, page 41-42 1; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 14 

 The change control process is a set of procedures and tools that are used to manage changes to the requirements and the solution throughout the project life cycle. The change control process is defined in the business analysis plan, which is a document that describes how the business analysis activities will be performed, monitored, and controlled. The business analysis plan also specifies the roles and responsibilities of the business analyst and other stakeholders involved in the change control process. The business analyst should follow the change control process as defined in the business analysis plan to ensure that any changes to the requirements are properly documented, analyzed, approved, communicated, and implemented. By following the change control process, the business analyst can avoid scope creep, maintain the quality and integrity of the requirements, and align the solution with the business needs and objectives. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 24; Business Analysis for Practitioners: A Practice Guide2, page 133.

 One of the first steps of a project is to identify the stakeholders and their interests. Stakeholders are the individuals or groups who have an interest or influence in the project or its outcome. Identifying the stakeholders and their interests helps to understand their needs, expectations, roles, responsibilities, and communication preferences. It also helps to manage their involvement and engagement throughout the project life cycle, and to address any potential conflicts or issues that may arise. The other options are not the first steps of a project. Identifying the classes of users and their requirements is part of the requirements elicitation process, which occurs after the project initiation phase. Aligning the sponsor expectations along the project goals is part of the project charter development, which is also done after the project initiation phase. Evaluating the sources for requirements and prioritizing them is part of the requirements analysis process, which occurs after the requirements elicitation process. References: PMI-PBA® Examination Content Outline, page 10; PMI-PBA® Reference List, page 1, BABOK® Guide v3, page 50; 3.

 A customer metrics tool is a tool that measures the satisfaction, loyalty, retention, and advocacy of customers. It helps to evaluate the performance and quality of the products or services offered by a company, as well as the effectiveness of the customer service and support. A customer metrics tool can also provide insights into the needs, preferences, expectations, and feedback of customers, which can help to improve the customer experience and increase customer retention and referrals. Some examples of customer metrics tools are12:

Customer Satisfaction Score (CSAT): This tool measures how satisfied customers are with a specific product, service, or interaction. It typically uses a scale of 1 to 5 or 1 to 10, where higher scores indicate higher satisfaction. CSAT can be used to assess the overall satisfaction of customers, or to focus on specific aspects, such as ease of use, quality, or speed.

Customer Effort Score (CES): This tool measures how easy or difficult it is for customers to complete a task, such as placing an order, resolving an issue, or finding information. It usually uses a scale of 1 to 7, where lower scores indicate lower effort. CES can be used to identify and eliminate the pain points and friction that customers encounter, and to enhance the customer experience and loyalty.

Net Promoter Score (NPS): This tool measures how likely customers are to recommend a product, service, or company to others. It uses a scale of 0 to 10, where customers are classified as detractors (0-6), passives (7-8), or promoters (9-10). NPS can be used to gauge the loyalty and advocacy of customers, and to calculate the growth potential and profitability of a company.

Churn Rate: This tool measures the percentage of customers who stop using a product or service within a given period of time. It can be calculated by dividing the number of customers who left by the total number of customers at the beginning of the period. Churn rate can be used to monitor the retention and attrition of customers, and to identify the reasons and factors that cause customers to leave.

Customer Lifetime Value (CLV): This tool measures the total revenue or profit that a customer generates for a company over their entire relationship. It can be calculated by multiplying the average purchase value by the average purchase frequency, and then multiplying the result by the average customer lifespan. CLV can be used to estimate the value and profitability of each customer, and to allocate resources and strategies accordingly.

A focus group is not a metrics tool, but rather a research method that involves a small group of customers who share their opinions and experiences about a product, service, or topic. A focus group can provide qualitative data and insights, but not quantitative measurements. A business completion metrics tool is a tool that measures the percentage of customers who complete a desired action, such as signing up, purchasing, or renewing. It can be used to evaluate the conversion and retention rates of customers, and to optimize the customer journey and funnel. A sales and marketing metrics tool is a tool that measures the performance and effectiveness of the sales and marketing activities and campaigns of a company. It can be used to track and analyze the sales and marketing goals, strategies, and outcomes, and to improve the sales and marketing efficiency and ROI. References: 1 The Top 5 Customer Satisfaction Metrics You Need to Track; 2 Customer Satisfaction Metrics: 7 Best Metrics to Measure

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. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 14; Business Analysis for Practitioners: A Practice Guide2, page 80.

When a change request is received, the business analyst is responsible for analyzing the impact on business and underlying systems. The business analyst should assess how the change request will affect the business needs, objectives, and value, as well as the existing or planned systems, processes, and functions. The business analyst should also evaluate the feasibility, priority, and urgency of the change request, and provide recommendations and alternatives to the stakeholders. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 23; Business Analysis for Practitioners: A Practice Guide2, page 132.

Time-boxing is a prioritization technique that involves allocating a fixed amount of time or resources to each requirement or backlog item. Time-boxing can help the business analyst to review the amount of work the team is capable of delivering based on the approved project schedule by setting deadlines and constraints for each requirement or backlog item. Time-boxing can also help to focus on the most valuable and feasible requirements or backlog items and avoid scope creep or gold plating. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 11; Business Analysis for Practitioners: A Practice Guide (2015), page 66.

 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. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 14; Business Analysis for Practitioners: A Practice Guide2, page 80.

 A requirements specification is a document that describes the customer’s needs for a product and includes a functional model, a data model, and a glossary of terms. A standard operating manual is a document that provides instructions on how to use a product or service. A business case is a document that justifies the initiation of a project or investment based on its expected benefits and costs. A project charter is a document that authorizes the start of a project and defines its scope, objectives, and stakeholders. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 8; Business Analysis for Practitioners: A Practice Guide (2015), page 36.

 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. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.

External dependencies are the factors or conditions that are outside the control of the project, but may affect its scope, schedule, cost, quality, or risks. External dependencies may include legal, regulatory, cultural, environmental, political, economic, or technological factors. An organization that is evaluating the possibility of conducting business internationally should investigate these factors at the onset of the initiative, as they may have significant impacts on the feasibility, viability, and desirability of the project. The other options are not factors that should be investigated at the onset of the initiative. Deliverables to be produced are the outputs or results of the project that meet the stakeholder requirements. Impacts on requirements baseline are the changes or deviations from the approved set of requirements that define the solution scope. Change control processes are the procedures and tools that manage how changes to the project scope, schedule, cost, quality, or risks are identified, evaluated, approved, implemented, and communicated. These factors are determined or addressed during the planning or execution phases of the project, not at the onset of the initiative. References: PMI-PBA® Examination Content Outline, page 13; PMI-PBA® Reference List, page 1, BABOK® Guide v3, page 39; 4.

Version control is a technique that helps to manage changes to requirements and ensure that only authorized changes are made. It also helps to maintain a history of requirements changes, which records the date, reason, and impact of each change. Tracking the status of each requirement helps to monitor the progress and completion of requirements throughout the project life cycle. These practices help to ensure the integrity of requirements and avoid confusion, inconsistency, or ambiguity. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 8; Business Analysis for Practitioners: A Practice Guide (2015), page 38.

A configuration management system is a tool that can be used to trace the large number of requirements that will be generated by this project. A configuration management system is a system that consists of the processes, procedures, tools, and databases that are used to manage and control the configuration items of the project. A configuration item is any component of the project that has a defined and approved version, such as a requirement, a deliverable, a document, a model, a test case, etc. A configuration management system can help the business analyst and the project team to record, track, update, and maintain the configuration items throughout the project lifecycle, and to ensure their consistency, integrity, and traceability. A configuration management system can also help to handle changes, resolve issues, and measure the quality and performance of the project. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 24; Business Analysis for Practitioners: A Practice Guide2, page 133.

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.

 According to the PMI Guide to Business Analysis, one of the best practices for managing changes to requirements is to communicate them to all relevant stakeholders and solicit their feedback before approving or rejecting the change request. This ensures that the impact of the change is understood and agreed upon by all parties, and that the change does not introduce any conflicts or inconsistencies with the existing requirements. By sharing the new requirements with all stakeholders and asking them to submit their comments before the meeting, the business analyst can facilitate a constructive discussion and reach a consensus on how to proceed with the change request. References: PMI Guide to Business Analysis, page 287-288.

 According to the PMI Professional in Business Analysis objectives and content, the business analyst should recommend the option with the highest functionality score and the lowest cost score. In this case, option A, 1, Custom solution, has the highest functionality score of 10 and the lowest cost score of 1. Therefore, it should be recommended. 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

Managing solution scope is the task of ensuring that the solution meets the agreed-upon requirements and delivers the expected value to the stakeholders. Managing solution scope involves analyzing the impact of any changes to the scope, assessing the feasibility and risks of the changes, and obtaining approval from the stakeholders before implementing the changes. Managing solution scope can help the business analyst to identify the impacts, dependencies, or risks associated with the addition to the scope. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 14; Business Analysis for Practitioners: A Practice Guide (2015), page 83.

 Phased baselining is an approach that involves dividing the requirements into smaller subsets or increments that can be approved, developed, and delivered separately. Phased baselining can help to cope with the requirements’ volatility, as it allows the business analyst and the stakeholders to accommodate changes and feedback in each increment, and to adjust the scope and priorities of the subsequent increments accordingly. Phased baselining can also reduce the risk and uncertainty of the project, as it enables early validation and verification of the solution, and provides more flexibility and adaptability to the changing business environment and regulations. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 24; Business Analysis for Practitioners: A Practice Guide2, page 133.

 Agile is an approach to enable developers and product owners to be in constant communication so that changes or issues that occur during development are exposed and discussed as they develop. Agile emphasizes iterative and incremental delivery of value, collaboration, feedback, and adaptation. Agile methods include Scrum, Kanban, XP, and others. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 14; Business Analysis for Practitioners: A Practice Guide (2015), page 17.

The requirements sign-off is a process that involves obtaining the formal approval and acceptance of the requirements from the customer and other stakeholders. The requirements sign-off confirms that the requirements are clear, complete, correct, and consistent, and that they meet the customer’s needs and expectations. The requirements sign-off also establishes a baseline for the development and testing of the solution, and serves as a reference point for managing changes and resolving issues. The business analyst should first facilitate the requirements sign-off with the customer before the developers start development, to ensure that the requirements are agreed upon and validated by all parties, and to avoid rework, delays, and conflicts later in the project. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 18; Business Analysis for Practitioners: A Practice Guide2, page 92.

The business analyst should use a traceability matrix to help communicate the status of the requirements. A traceability matrix is a document that shows the relationships and dependencies among the requirements, and tracks their changes, verification, and validation throughout the project life cycle. A traceability matrix can help the business analyst and the project manager to monitor the progress and quality of the requirements, and to identify any gaps, issues, or risks. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 100.

The selected project life cycle is a characteristic of the project that is needed to determine the approach so that the business analyst can validate whether they will need to have a discussion about the budget. The project life cycle is the sequence of phases or stages that the project goes through from initiation to closure. The project life cycle can be selected based on various factors, such as the nature, complexity, size, and uncertainty of the project, the stakeholder preferences, the organizational culture, and the industry standards. The project life cycle can influence the approach that the business analyst and the project team use to plan, execute, monitor, and control the project, and to deliver the product or service. The project life cycle can also affect the budget, schedule, scope, and quality of the project, and the level of stakeholder involvement and communication. Therefore, the business analyst should understand the selected project life cycle and its implications for the project, and validate whether it is appropriate and feasible for the project, and whether it requires any adjustments or discussions with the stakeholders. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 84.

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. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.

 Quality function deployment (QFD) is a technique that involves translating customer needs or requirements into product features or specifications. QFD helps to relate the product features to customer value by using a matrix called a House of Quality, which shows how each feature satisfies a customer requirement, how important each requirement is to the customer, how well each feature performs compared to competitors, and how each feature affects other features. QFD can also help to identify gaps or opportunities for improvement in the product design. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 12; Business Analysis for Practitioners: A Practice Guide (2015), page 69.

Workshop sessions are a technique to elicit, analyze, and prioritize requirements by bringing together a group of stakeholders, such as subject matter experts, to collaborate and reach a consensus. Workshop sessions can be used to identify and prioritize the requirements for a newly approved project. The other techniques are not suitable for this purpose. Delphi technique is a technique to obtain expert opinions anonymously and iteratively until a consensus is reached. Brainstorming is a technique to generate a large number of ideas or solutions in a short time. Idea and mind mapping is a technique to visually organize ideas or information using diagrams or graphs. References: PMI-PBA® Examination Content Outline, page 10; PMI-PBA® Reference List, page 1, BABOK® Guide v3, page 50.

 A matrix is a tool that can be used to record, organize, and track the requirements throughout the lifecycle of the project. A matrix can help the business analyst to identify the sources, dependencies, relationships, and attributes of the requirements, as well as to monitor their status, changes, and traceability. A matrix can also facilitate the communication, verification, and validation of the requirements with the stakeholders, and ensure their alignment with the business needs and objectives. A matrix can be updated and reviewed regularly to reflect the current state of the requirements and the solution, and to obtain the approval and acceptance from the stakeholders. A common example of a matrix is the Requirements Traceability Matrix (RTM), which is a tool that links the requirements to the project scope, objectives, deliverables, and test cases12. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline3, page 18; Business Analysis for Practitioners: A Practice Guide4, page 92.

 According to the PMI Guide to Business Analysis, a requirements review is a formal meeting where the requirements are presented and evaluated by the stakeholders, subject matter experts, and other relevant parties. The purpose of the review is to ensure that the requirements are clear, complete, consistent, feasible, testable, and aligned with the business needs and objectives. To prepare for the review, it would be best for the team to evaluate the requirements and highlight those that cannot be met or need to be deferred, as this would help to identify any gaps, risks, issues, or dependencies that need to be addressed or resolved before proceeding to the design phase. Preparing a test procedure, starting the design, or requesting a contract amendment are not appropriate actions to take before the review, as they could introduce errors, biases, or conflicts in the requirements. References: PMI Guide to Business Analysis, page 181-182.

 A use case is a technique that describes how an actor interacts with a system to achieve a goal or perform a task. A use case consists of a main scenario and possible alternative scenarios that capture the normal, exceptional, and error flows of events. A use case can be used as a source for building tests of end-to-end business processes across business functions and systems, as it provides a comprehensive and realistic view of the expected behavior and outcomes of the solution. A use case can also help to verify and validate the functional requirements and acceptance criteria of the solution. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 99.

 A configuration management system is a capability that will help ensure that the product conforms to approved requirements, changes can be documented, and the status of each change can be reported. A configuration management system is a system that consists of the processes, procedures, tools, and databases that are used to manage and control the configuration items of the project. A configuration item is any component of the project that has a defined and approved version, such as a requirement, a deliverable, a document, a model, a test case, etc. A configuration management system can help the business analyst and the project team to record, track, update, and maintain the configuration items throughout the project lifecycle, and to ensure their consistency, integrity, and traceability. A configuration management system can also help to handle changes, resolve issues, and measure the quality and performance of the project. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 24; Business Analysis for Practitioners: A Practice Guide2, page 133.

A requirements traceability tool is a tool that provides combined functionality for business analysis and quality assurance activities. It helps to document and track the relationships and dependencies among the requirements, the sources of the requirements, and the project deliverables. It also helps to monitor the status, changes, and verification of the requirements throughout the project life cycle. A requirements traceability tool can also support the analysis, validation, and testing of the requirements, as well as the evaluation of the solution quality and performance12.

A functional specification tool is a tool that helps to define and document the functional requirements of a system or a solution. It describes the features, functions, behaviors, and inputs and outputs of the system or the solution. It also specifies the acceptance criteria and the expected results of the system or the solution. A functional specification tool is mainly used for business analysis activities, but not for quality assurance activities13.

A system use case modeling tool is a tool that helps to illustrate and communicate the interactions and scenarios between the users and the system or the solution. It uses diagrams, symbols, and text to represent the actors, use cases, relationships, and flows of events of the system or the solution. It also defines the preconditions, postconditions, and exceptions of each use case. A system use case modeling tool is mainly used for business analysis activities, but not for quality assurance activities14.

A solution quality assurance tool is a tool that helps to measure and evaluate the quality of the system or the solution. It uses various methods and techniques, such as testing, inspection, review, audit, and feedback, to check the quality of the system or the solution against the quality standards and criteria. It also identifies and reports any quality issues, defects, or errors of the system or the solution. A solution quality assurance tool is mainly used for quality assurance activities, but not for business analysis activities1 .

References: 1 PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 9-11; 2 Business Analysis for Practitioners: A Practice Guide, page 121; 3 Business Analysis for Practitioners: A Practice Guide, page 133; 4 Business Analysis for Practitioners: A Practice Guide, page 135; Business Analysis for Practitioners: A Practice Guide, page 125

The business analyst should follow the change control process to handle the new regulatory mandate that affects the project. The change control process is a set of procedures that defines how changes to the requirements or the project scope are identified, analyzed, approved, and implemented. The change control process helps to ensure that changes are aligned with the business need, the project objectives, and the stakeholder expectations. References: PMI Guide to Business Analysis, Chapter 9, Section 9.4.1; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain IV: Traceability and Monitoring, Task 2.

Tracing requirements is a technique that involves tracking the origin, dependencies, allocation, and status of each requirement throughout the project life cycle. Tracing requirements can help the business analyst to determine this issue before delivery by ensuring that each project objective is linked to one or more requirements, and that each requirement is verified and validated against the project objectives. Tracing requirements can also help to identify any missing, redundant, or conflicting requirements. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 10; Business Analysis for Practitioners: A Practice Guide (2015), page 40.

A configuration management system is a standardized, effective, and efficient way to manage changes to project documentation. A configuration management system is a set of tools and processes that help to track, control, and update the configuration items (CIs) of a project, such as documents, requirements, designs, code, tests, etc. A configuration management system helps to ensure that the project documentation is consistent, accurate, and up-to-date throughout the project life cycle. It also helps to maintain the traceability and auditability of the changes made to the project documentation. A configuration management system typically includes the following components:

A configuration management plan that defines the scope, roles, responsibilities, policies, procedures, and standards for configuration management.

A configuration management database (CMDB) that stores the information about the CIs, their attributes, relationships, versions, baselines, and changes.

A configuration identification process that assigns unique identifiers and names to the CIs and their versions.

A configuration control process that evaluates, approves, and implements changes to the CIs and their versions.

A configuration status accounting process that records and reports the status and history of the CIs and their versions.

A configuration verification and audit process that verifies and validates the CIs and their versions against the requirements and specifications.

References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 13.

According to the PMI Professional in Business Analysis objectives and content, an impact analysis is a technique that is used to assess the effects and implications of a change request on the requirements, scope, schedule, cost, quality, and other aspects of a project or product. An impact analysis can help to determine the feasibility, desirability, and priority of the change request, as well as to identify the risks, issues, and dependencies associated with the change. An impact analysis can also help to communicate the impact of the change to the stakeholders, and to support the decision-making process for approving or rejecting the change request. 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: Study.com

A requirements traceability matrix is a tool that links the requirements to their sources, objectives, and deliverables. It helps to track the status, changes, and verification of each requirement throughout the project life cycle. If the requirements traceability matrix was not updated with the change, it could result in a key requirement being missed or overlooked in the implementation. The other options are not likely to cause this problem. The requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, and managed. The scope management plan is a document that describes how the project scope will be defined, controlled, and verified. The schedule management plan is a document that describes how the project schedule will be developed, monitored, and controlled. References: PMI-PBA® Examination Content Outline, page 13; PMI-PBA® Reference List, page 1, BABOK® Guide v3, page 39; 6.

When a business analyst uses subject matter experts to define roles and identify influencers, the project artifact that is created or updated is the stakeholder register. The stakeholder register is a document that identifies and records information about the stakeholders who are involved in or affected by the project or the solution. The stakeholder register can include information such as stakeholder names, roles, responsibilities, interests, expectations, influence levels, communication preferences, etc. The business analyst can use subject matter experts as sources of information or advice to help define roles and identify influencers among the stakeholders. Subject matter experts are individuals who have specialized knowledge or expertise in a specific domain or area related to the project or the solution. A RACI matrix is not a project artifact that is created or updated when a business analyst uses subject matter experts to define roles and identify influencers. A RACI matrix is a tool that defines and clarifies the roles and responsibilities of each stakeholder for each task or deliverable in the project. A RACI matrix can use four categories: Responsible (who performs the task), Accountable (who approves or oversees the task), Consulted (who provides input or feedback for the task), and Informed (who is notified of the task outcome). A SWOT analysis is not a project artifact that is created or updated when a business analyst uses subject matter experts to define roles and identify influencers. A SWOT analysis is a technique that involves identifying and evaluating the strengths, weaknesses, opportunities, and threats of an organization, a project, or a solution. A SWOT analysis can help to assess the internal and external factors that may affect the performance or value of an organization, a project, or a solution. A stakeholder management plan is not a project artifact that is created or updated when a business analyst uses subject matter experts to define roles and identify influencers. A stakeholder management plan is a document that describes how the stakeholders will be engaged, communicated with, managed, and satisfied throughout the project lifecycle. A stakeholder management plan can include strategies, actions, tools, and metrics for stakeholder management. References: Business Analysis for Practitioners: A Practice Guide 1, page 34-35; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 2, page 14-15.

One benefit of documenting the change control process is that stakeholders know how to request changes. The change control process is a process that defines how changes to the project scope, schedule, cost, quality, or requirements are identified, evaluated, approved, implemented, and communicated. Documenting the change control process helps to establish clear and consistent guidelines and procedures for managing changes and ensuring that they are aligned with the project objectives and stakeholder expectations. Documenting the change control process also helps to inform the stakeholders about how to request changes, what information and justification are required, who is responsible for reviewing and approving changes, and what criteria and methods are used for assessing the impact and value of changes. Stakeholders are not shielded from how changes are assessed by documenting the change control process, as it implies that they are excluded or unaware of the change evaluation and decision making process. On the contrary, documenting the change control process helps to increase transparency, collaboration, and communication among the stakeholders regarding changes. Stakeholders do not have a schedule of changes to be deployed by documenting the change control process, as it implies that they have a predetermined or fixed plan of when and how changes will be implemented. On the contrary, documenting the change control process helps to ensure that changes are implemented in a timely and effective manner based on their priority, feasibility, and dependency. Stakeholders do not understand the difficulty of managing requirements by documenting the change control process, as it implies that they have a negative or pessimistic view of the requirements management process. On the contrary, documenting the change control process helps to improve the quality and stability of the requirements and reduce ambiguity, confusion, or conflicts among the stakeholders. References: Business Analysis for Practitioners: A Practice Guide 1, page 163-164; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 2, page 20.

 Using a table to map business rules to functional requirements ensures that all tax and fee calculations are implemented correctly. It helps in verifying that the system reflects current regulations and avoids calculation errors. References: PMI-PBA® Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.

 The type of requirements that do not trace to a business need are out-of-scope requirements. Out-of-scope requirements are the requirements that are not related to the project scope, objectives, or deliverables, and that do not contribute to the solution of the business problem or opportunity. Out-of-scope requirements are usually identified and excluded during the requirements analysis and traceability processes, to avoid wasting time, resources, and effort on unnecessary or irrelevant features or functions. Out-of-scope requirements can be caused by various factors, such as unclear or changing business needs, conflicting or unrealistic stakeholder expectations, poor communication or elicitation techniques, or lack of validation or verification methods. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 18; Business Analysis for Practitioners: A Practice Guide2, page 92.

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. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.

 Inspection is a technique or tool that is used to obtain acceptance of the delivered product. Inspection is a process that involves examining and measuring the product or its components against the predefined standards, criteria, or specifications, to determine its quality, completeness, and correctness. Inspection can help the business analyst and the project team to identify and correct any defects, errors, or deviations in the product, and to ensure that it meets the requirements and the stakeholder expectations. Inspection can also help to obtain the formal approval and acceptance of the product from the customer and other stakeholders, and to confirm that the product is ready for delivery or deployment. Inspection can be done using various methods, such as reviews, walkthroughs, audits, or tests. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 21; Business Analysis for Practitioners: A Practice Guide2, page 101.

 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. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 11; Business Analysis for Practitioners: A Practice Guide2, page 66.

 Documenting the source of each requirement in the requirements traceability matrix allows for easy identification of the requestor and facilitates communication with stakeholders. References: PMI-PBA® Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.

The next step that the business analyst should take after comparing the requirements to internal and external quality standards is to ensure that the requirements are validated. Validation is a process that confirms that the requirements align with the business objectives, stakeholder needs, and expected value of the project. Validation also ensures that the requirements are feasible, acceptable, and testable. Validation can be performed by using techniques such as reviews, walkthroughs, inspections, or demonstrations. Validation can help to identify and resolve any errors, gaps, or conflicts in the requirements before they are approved and implemented. Setting the priority of the requirements is not the next step that the business analyst should take after comparing the requirements to internal and external quality standards, as it is a process that determines the order and importance of the requirements based on their value, risk, urgency, or dependency. Priority can be set before or after comparing the requirements to quality standards, but it does not verify or confirm that the requirements meet the stakeholder expectations or project goals. Communicating the requirements to stakeholders is not the next step that the business analyst should take after comparing the requirements to internal and external quality standards, as it is a process that involves sharing and presenting the requirements to relevant stakeholders for feedback, approval, or implementation. Communication can be done before or after comparing the requirements to quality standards, but it does not check or ensure that the requirements are aligned with the business objectives or deliver value to the stakeholders. Baselineing the requirements is not the next step that the business analyst should take after comparing the requirements to internal and external quality standards, as it is a process that establishes an agreed-upon version of the requirements as a reference point for further changes or development. Baselineing can be done only after validating and approving the requirements, as it implies that they are complete, correct, clear, and consistent. References: Business Analysis for Practitioners: A Practice Guide 1, page 113-114; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 2, page 17.

The best approach to resolve this issue is to suggest re-estimating the requirement and following the change control process. This would allow the project team to assess the impact of the change request, evaluate the feasibility and cost of the modification, and obtain the approval of the stakeholders before implementing the change. A change control process is a method used to manage change requests for projects and big initiatives. It’s part of a change management plan, which defines the roles for managing change within a team or company1. Meeting with the customer and apologizing for misunderstanding the business’s need is not sufficient, as it does not address the root cause of the problem or propose a solution. Providing the stakeholder with a copy of the approved requirements baseline and moving forward without making a change is not acceptable, as it ignores the stakeholder’s feedback and dissatisfaction. Requiring development resources to work overtime to modify the deliverable to satisfy the stakeholder is not advisable, as it may compromise the quality of the work, increase the project cost and risk, and demoralize the team. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline2, PMI Guide to Business Analysis3, Business Analysis for Practitioners: A Practice Guide4, What Is a Change Control Process? (with Example Change Log)

According to the PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, one of the tasks under the domain of Traceability and Monitoring is to “Track the status, priority, and disposition of requirements and issues, and communicate updates as necessary” (Task 1). This implies that the business analyst is responsible for ensuring that the requirements are delivered as stated and that any changes or issues are communicated to the relevant stakeholders. One of the techniques that can be used to perform this task is the traceability matrix, which is a table that shows the relationships between requirements and other project artifacts, such as design documents, test cases, or deliverables. A traceability matrix can help the business analyst to verify that all the requirements are covered by the test cases and that the test output matches the expected results. Therefore, the technique that the business analyst could have used to ensure that requirements were delivered as stated is the traceability matrix.

A business rule is a statement that defines or constrains some aspect of the business and always resolves to either true or false. Business rules are intended to assert business structure or to control or influence the behavior of the business. Business rules describe the operations, definitions and constraints that apply to an organization. Business rules can apply to people, processes, corporate behavior and computing systems in an organization, and are put in place to help the organization achieve its goals. By documenting a business rule, the business analyst can ensure that the business need can be validated against the criteria that govern the business operations and outcomes. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 19; Business Analysis for Practitioners: A Practice Guide2, page 97.

Requesting information on the current ordering process and comparing it with other companies is a technique that involves gathering data and benchmarking best practices from similar or relevant sources. Requesting information on the current ordering process and comparing it with other companies can help the business analyst to take the next step after completing the requirements by analyzing the current state of the problem, identifying gaps or opportunities for improvement, and proposing possible solutions or alternatives. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 12; Business Analysis for Practitioners: A Practice Guide (2015), page 69.