PMI-PBA study guide
PMI-PBA · Work through your exam, one topic at a time.
PMI-PBA - the PMI Professional in Business Analysis - appears in the Project Management Institute's certification menu under Specialized Certifications, alongside PMI-ACP, PMI-RMP, PMI-SP, PMI-CP and others. PMI frames its certifications broadly as a way to "increase your earning power, drive project success, and stand out from the crowd," and lists this credential among those it offers to practitioners. The PMI-PBA study guide has 5 sections and about 1,596 words.
01Needs Assessment: From Problem to Endorsed Direction
Needs Assessment is the business analyst's pre-solution work: defining a situation or problem statement, gathering data on the current state, identifying the desired future state, measuring the gap, and recommending whether and how to close it. Candidates must sequence the work: identify the problem or opportunity, assess the current state (capability and performance), define business goals and measurable objectives, identify and evaluate options, then recommend a solution approach.
331 words, about 2 min02Planning the Business Analysis Work
Planning answers four questions: what approach, who is involved, how requirements will be managed, and how decisions will be made. Know the components of a business analysis plan and a requirements management plan: BA approach (predictive versus adaptive/change-driven), elicitation plan, stakeholder analysis and engagement plan, communication plan, governance and decision rights, requirements attributes and traceability approach, prioritization scheme, approval and sign-off process, change control, tool selection, estimation, and measures of BA performance.
308 words, about 2 min03Analysis: Elicitation, Modeling, and Requirements Quality
Analysis converts raw elicitation into a validated, prioritized, testable requirement set. Know the techniques and when each fits: interviews (depth), workshops (consensus and conflict resolution), focus groups (opinions), observation and job shadowing (tacit work), surveys (breadth), document and interface analysis, prototyping (unclear interface), brainstorming, and reverse engineering.
316 words, about 2 min04Traceability and Monitoring
Traceability is the ability to follow a requirement's life in both directions: backward to the business need, objective, and source stakeholder that justify it; forward to design, build, test cases, and delivered functionality. Know the traceability matrix and its relationship types - derive, satisfy, verify, depend on, relate to - plus requirement attributes: ID, source, owner, priority, status, version, rationale, acceptance criteria, complexity, stability.
310 words, about 2 min05Evaluation: Did the Solution Solve the Problem?
Evaluation closes the loop opened in Needs Assessment. It assesses the delivered or partial solution against acceptance criteria and against the original business objectives, determines whether benefits are being realized, and recommends acceptance, corrective action, or retirement.
331 words, about 2 min