PMI Professional in Business Analysis (PMI-PBA) Exam Questions

PMI Professional in Business Analysis Exam Objectives

1. 1

   1.0 Needs Assessment (18%)

   • Task 1.1: Define or review a business problem or opportunity using problem and opportunity analysis techniques in order to develop a solution scope statement and/or to provide input to create a business case.
   • Task 1.2: Collect and analyze information from a variety of sources using valuation tools and techniques to contribute to determining the value proposition of the initiative.
   • Task 1.3: Collaborate in the development of project goals and objectives by providing clarification of business needs and solution scope in order to align the product with the organization’s goals and objectives.
   • Task 1.4: Identify stakeholders by reviewing goals, objectives, and requirements in order that the appropriate parties are represented, informed and involved.
   • Task 1.5: Determine stakeholder values regarding the product, using elicitation techniques in order to provide a baseline for prioritizing requirements.
2. 2

   2.0 Planning (22%)

   • Task 2.1: Review the business case, and the project goals and objectives, in order to provide context for business analysis activities.
   • Task 2.2: Define strategy for requirements traceability using traceability tools and techniques in order to establish the level of traceability necessary to monitor and validate the requirements.
   • Task 2.3: Develop requirements management plan by identifying stakeholders, roles and responsibilities, communication protocols, and methods for eliciting, analyzing, documenting, managing, and approving requirements in order to establish a roadmap for delivering the expected solution.
   • Task 2.4: Select methods for requirements change control by identifying channels for communicating requests and processes for managing changes in order to establish standard protocols for incorporation into the change management plan.
   • Task 2.5: Select methods for document control by using documentation management tools and techniques in order to establish a standard for requirements traceability and versioning.
   • Task 2.6: Define business metrics and acceptance criteria by collaborating with stakeholders for use in evaluating when the solution meets the requirements.
3. 3

   3.0 Analysis (35%)

   • Task 3.1: Elicit or identify requirements, using individual and group elicitation techniques in order to discover and capture requirements with supporting details (e.g., origin and rationale).
   • Task 3.2: Analyze, decompose, and elaborate requirements using techniques such as dependency analysis, interface analysis, and data and process modeling in order to collaboratively uncover and clarify product options and capabilities.
   • Task 3.3: Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.
   • Task 3.4: Allocate accepted or deferred requirements by balancing scope schedule, budget, and resource constraints with the value proposition using prioritization, dependency analysis, and decision-making tools and techniques in order to create a requirements baseline.
   • Task 3.5: Obtain sign-off on requirements baseline using decision-making techniques in order to facilitate stakeholder consensus and achieve stakeholder approval.
   • Task 3.6: Write requirements specifications using process (such as use cases, user stories), data, and interface details in order to communicate requirements that are measurable and actionable (that is, suitable for development).
   • Task 3.7: Validate requirements using tools and techniques such as documentation review, prototypes, demos, and other validation methods in order to ensure requirements are complete, accurate and aligned with goals, objectives, and value proposition.
   • Task 3.8: Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques for use in evaluating whether the solution meets requirements.
4. 4

   4.0 Traceability and Monitoring (15% )

   • Task 4.1: Track requirements using a traceability artifact or tools, capturing the requirements' status, sources and relationships (including dependencies), in order to provide evidence that the requirements are delivered as stated.
   • Task 4.2: Monitor requirements throughout their lifecycles using a traceability artifact or tool in order to ensure the appropriate supporting requirements artifacts (such as models, documentation, and test cases) are produced, reviewed and approved at each point in the lifecycle.
   • Task 4.3: Update a requirement’s status as it moves through its lifecycle states by communicating with appropriate stakeholders and recording changes in the traceability artifact or tool in order to track requirements towards closure.
   • Task 4.4: Communicate requirements status to project manager and other stakeholders using communication methods in order to keep them informed of requirements issues, conflicts, changes, risks, and overall status.
   • Task 4.5: Manage changes to requirements by assessing impacts, dependencies, and risks in accordance with the change control plan, and comparing to the requirements baseline in order to maintain the integrity of the requirements and associated artifacts.
5. 5

   5.0 Evaluation (10%)

   • Task 5.1: Validate the solution's test results, reports, and other test evidence against the requirements acceptance criteria in order to determine whether the solution satisfies the requirements.
   • Task 5.2: Analyze and communicate the solution's identified gaps and deltas using quality assurance tools and methods in order to enable stakeholders to resolve discrepancies between solution scope, requirements, and developed solution.
   • Task 5.3: Obtain stakeholder sign-off on the developed solution using decision-making techniques in order to proceed with deployment.
   • Task 5.4: Evaluate the deployed solution using valuation techniques in order to determine how well the solution meets the business case and value proposition.