PMI Professional in Business Analysis PMI-PBA PMI Study Notes

One of the main purposes for creating a requirements traceability matrix is to track how requirements can be connected to the solution. A requirements traceability matrix is a tool that links the requirements to the project scope, objectives, deliverables, and test cases. A requirements traceability matrix can help the business analyst to track the origin, allocation, dependencies, and status of the requirements throughout the project lifecycle, and to ensure that the solution meets the requirements and the stakeholder expectations. A requirements traceability matrix can also help to manage changes, resolve issues, and measure the quality and performance of the solution. A requirements traceability matrix can be created using various formats, such as a table, a spreadsheet, or a database12. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline3, page 18; Business Analysis for Practitioners: A Practice Guide4, page 92.

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.

 The business analyst should trace the requirements and measure the impact of the requested changes on the existing delivery date. Tracing the requirements means identifying the source, dependencies, and relationships of the requirements, and ensuring their alignment with the business needs, objectives, and expectations. Measuring the impact of the changes means assessing how the changes will affect the scope, schedule, cost, quality, and risk of the project. These actions can help the business analyst and the project team to evaluate the feasibility and priority of the changes, and to communicate the implications and alternatives to the customer and other stakeholders. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 23; Business Analysis for Practitioners: A Practice Guide2, page 131.

 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.