PMI Professional in Business Analysis PMI-PBA Reddit Questions

A requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, and managed throughout the project. It typically includes the following components12:

• Requirements work plan: This component defines the activities, tasks, resources, schedule, and deliverables for the requirements process. It also identifies the roles and responsibilities of the requirements team and other stakeholders.
• Prioritization process: This component describes the criteria and methods for prioritizing the requirements based on their value, urgency, risk, dependency, and other factors. It also defines the levels of priority and how they will be communicated and updated.
• Traceability matrix template: This component provides a format for documenting the relationships and dependencies among the requirements, the sources of the requirements, and the project deliverables. It also helps to track the status, changes, and verification of the requirements.
• Other components: Depending on the project context and complexity, the requirements management plan may also include other components, such as requirements definition, requirements attribute template, requirements change control process, requirements communication plan, requirements validation plan, and requirements metrics12. References: 1 PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 9; 2 Business Analysis for Practitioners: A Practice Guide, page 121-122

This is because it has the highest score in the “Lower maintenance cost” category, which has a weight of 2, and the second highest score in the “Improved customer satisfaction” category, which has a weight of 3. The weighted-ranking matrix is a technique that helps to compare and evaluate different options based on multiple criteria and their relative importance. Each option is assigned a score for each criterion, and the score is multiplied by the weight of the criterion. The option with the highest total score is the most preferred one.

According to the PMI Guide to Business Analysis, user acceptance testing is a technique that involves verifying and validating that the solution meets the business requirements and satisfies the stakeholder needs and expectations. User acceptance testing is usually performed by the end users or their representatives, who evaluate the solution against predefined acceptance criteria and provide feedback on its functionality, usability, performance, quality, etc. User acceptance testing can help to determine whether a solution satisfies business requirements, as it can demonstrate that the solution delivers the intended business value and benefits, and that it meets or exceeds the stakeholder satisfaction. By reviewing the results of user acceptance testing, a business analyst can assess how well the solution meets business requirements, and identify any gaps or issues that need to be addressed or resolved. Evaluating the solution against the project charter, conducting a brainstorming session with end users, or reviewing the traceability matrix are other ways to analyze and validate requirements, but they do not necessarily determine whether a solution satisfies business requirements, as they do not involve testing or evaluating the solution in real or simulated conditions. References: PMI Guide to Business Analysis, page 317-318.

The business case provides the rationale for the project and includes an analysis of the costs and benefits. It is used to assess risks, including the potential need to cancel the product. References: PMI-PBA® Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.