Eligibility Criteria

To get certified as a PMI-PBA, the applicant needs to meet one of the following sets of requirements that are based on educational level and professional experience:

• Bachelor's or postgraduate degree from a Global Accreditation Centre (GAC) program or global equivalent supplemented with 35 contact hours of formal education as well as 24 months of unique non-overlapping professional business analysis experience.
• Bachelor's Degree or global equivalent alongside 35 contact hours of business analysis practices and 36 months of working experience as a business analysis practitioner that must be gained within the last 8 years.
• High School Diploma/Associate's degree or global equivalent along with 35 contact hours of business analysis practices and 60 months of working background as a practitioner of business analysis. The experience must be within the last 8 years.

PMI PMI-PBA Exam Syllabus Topics:

Reference: https://www.pmi.org/certifications/business-analysis-pba

To pass the PMI-PBA test on the first try, the students should gain the necessary knowledge and skills, which will help them cover all the questions in the exam. All in all, the applicants will face with the following subject areas:

Needs Assessment: The first module evaluates the expertise of the examinees in collecting and analyzing the information from different sources utilizing valuation techniques and tools to determine the value of the initiative as well as providing the clarification of the business needs and solution scope to collaborate in the designing of project objectives and goals to adjust the product with the organization’s objectives and goals. Moreover, they need to have the competence in defining or reviewing the business problem for developing a solution scope statement or providing data to design a business case. In addition, the individuals should possess the experience in utilizing the elicitation techniques to determine stakeholder values concerning the product and give a baseline for prioritizing needs.

Planning: The next domain focuses on the proficiency of the learners in reviewing the business case, project objectives, and goals to present the context for the business analysis activities, utilizing the traceability techniques and tools to determine the strategies for requirements traceability, and define the level of traceability needed to validate & monitor the requirements as well as identifying roles, stakeholders, and communication protocols, responsibilities, and methods to develop the requirements management plan to elicit, analyze, document, manage, and approve requirements to establish a roadmap for performing the expected solutions. Besides that, it checks the skills in identifying channels for communicating processes and requests for managing changes to select methods for requirements change control and determine the standard protocols for incorporation into the change management plan.

Analysis: As for this part, the test takers need to show their competence in utilizing the individual and group elicitation techniques to identify the requirements for discovering and capturing the requirements with supporting details. Furthermore, they need to have the proficiency in analyzing, decomposing and elaborating the requirements utilizing various techniques, such as data and process modeling, interface analysis, and dependency analysis to clarify product capabilities & options. In addition, the examinees should possess the expertise in utilizing the valuation and decision-making techniques to estimate product capabilities & options, and determine the rejected, deferred, or accepted requirements as well as allocating deferred or accepted requirements to create a requirements baseline, and utilizing the decision-making techniques to get sign-off on requirements baseline, facilitate stakeholder agreement, and gain stakeholder approval.

Monitoring and Traceability: The next subject area evaluates the skills of the applicants in capturing the requirements’ relationships, sources, and status to give evidence that the requirements are fulfilled as stated, monitoring the requirements throughout their lifecycles to ensure the proper supporting requirements artifacts are reviewed, produced, and approved at every period in the lifecycle as well as updating a requirement’s status as it runs through its lifecycle phases by interacting with proper stakeholders and documenting changes in the traceability tool to track requirements towards the end. Moreover, it checks their competence in communicating the status of the requirements to the project manager and other stakeholders utilizing communication methods to keep them informed of requirements risks, conflicts, issues, changes, and overall status.

Evaluation: The last section checks the experience of the students in defining if the solution meets the requirements by validating the solution’s test evidence toward the requirements acceptance standards as well as analyzing and communicating the solution's identified deltas and gaps utilizing the quality insurance methods & tools and to equip the stakeholders to determine differences between developed solution, requirements, and solution scope. Additionally, the applicants need to possess the proficiency in evaluating the expanded solution utilizing valuation techniques to define how the solution satisfies the value proposition and business case.

Before attempting the certification exam, the candidates need to thoroughly study the topics covered in it. Each of these domains contains specific technical tasks that the potential test takers should develop mastery in. The highlights of the topics and tasks measured within the PMI-PBA exam are outlined below:

• Needs Assessment (18%)

  The first task within this subject area covers defining or reviewing business problems/opportunities by using techniques used in problem & opportunity analysis to develop solution scope statement and providing input for creating a business case. The second one addresses collecting and analyzing information used to determine initiative value proposition from a diversity of sources. The third part deals with providing the business needs alongside solution scope clarification. The fourth section explores the identification of the stakeholders by going through the requirements, objectives, and goals to ensure fair representation, information, and involvement. The last task deals with determining the stakeholders’ values with regards to the product by providing a baseline used to prioritize requirements.

• Analysis (35%)

  The initial task of this section focuses on the use of individual as well as group elicitation techniques for discovering and capturing requirements and their supporting details. The next task covers analysis, decomposition, and elaboration of requirements. This uses the techniques, such as interface analysis, data & process modeling, and dependency analysis to uncover as well as clarify options in products and their capabilities. The third part requires that the candidates be able to evaluate product options and product capabilities through valuation and decision-making techniques for determining whether the requirements will be accepted, postponed, or rejected. The next task involves creating a requirements baseline. It is done by allocating the accepted or deferred requirements through resource constraints, budget, and scope schedule balancing with the value proposition. The fifth module focuses on obtaining requirements baseline sign-off through decision-making techniques, which facilitate the stakeholder's consensus and approval. The activities covered in the sixth task include using the process, interface details, and data to write the requirements specifications. The seventh module deals with using the tools & techniques, such as documentation review, demos, prototypes, or other validation methods to validate the requirements. This is to ensure that the requirements are accurate and aligned with the value proposition, goals, and objectives. The last task explores acceptance criteria and detailed metrics elaboration and specification. It uses the relevant tools & techniques for measuring and evaluating the solution to check if it meets the requirements.

• Traceability & Monitoring (15%)

  The first task here focuses on the use of traceability tools/artifacts, capturing requirement status, relationships, as well as sources. This is to track the requirements that provide evidence that the stated requirements were delivered. The second task addresses monitoring of requirements through their entire lifecycle. This uses traceability artifacts/tools to ensure production, reviewing, and approval of needed requirement artifacts at every point of the life cycle. The next part involves updating the requirement status movement in all the states in its lifecycle through communication with the stakeholders involved and recording any changes in the traceability tool. The fourth task focuses on communicating requirements status to other stakeholders and the project manager. The last area looks into the management of changes affecting requirements, including assessing dependencies, risks, and impacts.

• Evaluation (10%)

  The initial task of the fifth objective involves validation of solution reports, test results, and any other evidence that goes against the acceptance criteria agreement. This is to determine if the requirements are satisfied by the solution. The second task covers using the tools and methods for quality assurance to analyze and communicate the identified gaps & deltas in a solution that enable resolving disparities between requirements, solution scope, and the solution developed by the stakeholders. The next part addresses the utilization of decision-making techniques by the stakeholders to sign-off on the developed solution so that deployment can proceed. Lastly, the fourth module covers evaluating deployed solutions, for example, using techniques in valuation to determine if the solution meets the value proposition and business case.

• Planning (22%)

  Within the second domain of the PMI-PBA certification exam, the first task addresses reviewing a business case and project objectives & goals to provide a context for business analysis activities. The second one deals with defining the requirements for the traceability strategy by using traceability techniques and tools to establish the needed traceability level required for monitoring and validating the requirements. The third task focuses on the establishment of a roadmap needed to deliver the expected solution by developing management plan requirements. This is made through identifying the stakeholders, responsibilities & roles, communication protocol, and methods used in eliciting, managing, approving, documenting, and analyzing requirements. The fourth part is about selecting methods used to control requirements change through the identification of channels for communication processes and requests for change management to establish protocols that are standard and can be incorporated in the changes in the management plan. The fifth task involves selecting methods for controlling documents by using tools & techniques in documentation management. This is followed by business metrics and criteria for acceptance through collaboration with the stakeholders.