PMI-PBA — PMI Professional in Business Analysis Study Plan
A practical time-based study plan for the PMI Professional in Business Analysis (PMI-PBA) exam, with 7-day, 14-day, 30-day, and 60/90-day paths.
Who this study plan is for
This Study Plan is for candidates preparing for PMI’s PMI Professional in Business Analysis (PMI-PBA) exam, code PMI-PBA. It is designed for working professionals who need to turn available study time into a realistic schedule.
The plan focuses on the skills the exam commonly tests through business analysis scenarios: needs assessment, stakeholder analysis, requirements planning and elicitation, analysis and modeling, traceability, change control, solution evaluation, and value delivery across predictive, agile, and hybrid environments.
Use the plan that matches your time left. If you are unsure, start with a diagnostic set, identify your weakest business analysis areas, and follow the shortest plan that still leaves time for at least one timed mock and full explanation review.
Which plan should you use?
| Time until exam | Best for | Weekly study time | Main goal | Mock exam timing |
|---|---|---|---|---|
| 7 days | Final review, retake preparation, or candidates who already studied | 10-18 hours total | Close gaps, sharpen scenario judgment, avoid overload | 1 timed mock or 2 half-mocks early/midweek |
| 14 days | Candidates with partial preparation or strong BA/project background | 18-30 hours total | Cover every domain once, then practice mixed scenarios | 1 mock around day 7-9, optional second mock day 12 |
| 30 days | Most balanced path for working professionals | 5-8 hours/week | Build domain knowledge, then convert to scenario practice | 2 full timed mocks in weeks 3-4 |
| 60/90 days | First-time candidates or those new to formal business analysis | 3-6 hours/week | Learn concepts, practice by domain, then build exam stamina | First mock after core review, then 2-4 additional timed mocks |
If your exam is already scheduled, do not try to “finish everything.” Prioritize high-yield review, missed-question analysis, and timed decision-making.
What to study for PMI-PBA
Use the official PMI-PBA exam identity as your anchor, but organize your study around practical exam tasks. The exam is not only about definitions. You need to recognize what a business analyst should do next in a given situation.
| Study area | What to know | Practice focus |
|---|---|---|
| Needs assessment | Business problem, opportunity, goals, business case, value, feasibility, current state vs. future state | Identify the real need before jumping to requirements or solutions |
| Business analysis planning | BA approach, stakeholder engagement, communication, governance, elicitation planning, requirements management approach | Choose an approach that fits predictive, agile, or hybrid delivery |
| Requirements elicitation and analysis | Elicitation techniques, requirement types, models, prioritization, acceptance criteria, validation | Determine which technique or model fits the scenario |
| Traceability and monitoring | Requirements traceability, baselines, approvals, change impact, requirement status, alignment to objectives | Maintain control without blocking value delivery |
| Solution evaluation | Acceptance, validation, benefits, performance, transition, lessons learned, value realization | Evaluate whether the solution solves the business need |
| Stakeholder, risk, and change judgment | Conflicting stakeholder expectations, unclear scope, regulatory constraints, risk responses, change requests | Select the best next action, not just a technically correct action |
| Delivery approach awareness | Predictive, agile, and hybrid contexts | Adapt BA work to the project environment rather than applying one method everywhere |
Daily practice rhythm
Use the same rhythm on most study days. The exact length can vary, but the sequence should stay consistent.
| Session length | Best use | Structure |
|---|---|---|
| 45 minutes | Busy weekday maintenance | 10 min review, 25 min questions, 10 min missed-question notes |
| 60-75 minutes | Standard weekday session | 15 min concept review, 35 min practice, 15-25 min explanation review |
| 90 minutes | Strong weekday or weekend session | 20 min review, 45 min timed set, 25 min missed-question analysis |
| 2-3 hours | Weekend deep work | Domain review, timed mixed set, error log update, targeted rereading |
| 4+ hours | Mock exam day | Timed mock, break, full explanation review, weakness list |
A good PMI-PBA study day is not measured by pages read. It is measured by whether you can explain why the best answer is best in a business analysis scenario.
The 7-day final review plan
Use this if you have one week left. The goal is not to learn everything from scratch. The goal is to stabilize your decision-making, review weak areas, and avoid final-week overload.
| Day | Focus | Study actions | Output |
|---|---|---|---|
| 1 | Diagnostic and triage | Take a timed mixed set or half-mock. Mark misses by domain and cause. | Top 3 weak areas and top 3 error patterns |
| 2 | Needs assessment and planning | Review business need, business case, stakeholder analysis, BA approach, governance, communication. Do targeted questions. | One-page planning checklist |
| 3 | Requirements analysis | Review elicitation, requirement types, models, prioritization, validation, acceptance criteria. Practice scenario sets. | List of model/technique selection rules |
| 4 | Traceability, change, and monitoring | Review traceability, baselines, approvals, change impact, requirement status, scope alignment. | Change-impact decision checklist |
| 5 | Timed mock or two timed blocks | Complete one full timed mock if possible, or two timed mixed blocks. Review explanations carefully. | Final weakness list |
| 6 | Explanation review and light targeted practice | Rework missed questions without looking at answers first. Focus on why distractors are wrong. | Final notes only; no new broad material |
| 7 | Light review and readiness check | Review formulas/checklists/terms, stakeholder-risk-change patterns, and timing strategy. Stop heavy study early. | Calm exam-day plan |
7-day rules
- Stop adding new broad study material after day 3 or 4.
- Prioritize missed-question explanations over new question volume.
- Do not take a full mock the day before the exam if it will create fatigue.
- Review agile, predictive, and hybrid clues in scenarios.
- Practice reading the last sentence of each question carefully before choosing an answer.
The 14-day focused plan
Use this if you have two weeks and some background in business analysis, project management, product work, systems analysis, or requirements management.
| Day | Focus | Actions |
|---|---|---|
| 1 | Diagnostic | Timed mixed set. Build an error log by domain and error type. |
| 2 | Needs assessment | Business problem, opportunity, value, goals, business case, solution options. |
| 3 | Stakeholders and planning | Stakeholder identification, engagement, communication, governance, BA approach. |
| 4 | Elicitation | Interviews, workshops, observation, surveys, document analysis, prototypes, backlog refinement. |
| 5 | Requirements analysis | Requirement types, models, acceptance criteria, prioritization, validation. |
| 6 | Predictive, agile, hybrid split | Compare requirement baselines, change control, backlog management, iterative validation. |
| 7 | Timed domain practice | Mixed timed set covering days 2-6. Review every explanation. |
| 8 | Traceability and monitoring | Traceability matrix, status, approvals, requirement relationships, scope alignment. |
| 9 | Change, risk, and conflict | Change impact, stakeholder disagreement, risk triggers, escalation, facilitation. |
| 10 | Solution evaluation | Acceptance, benefits, transition, value realization, performance gaps. |
| 11 | Timed mock | Full timed mock or longest realistic timed block. Track pacing and fatigue. |
| 12 | Mock review | Rework misses. Write the decision rule behind each miss. |
| 13 | Final weak-area repair | Target only weak areas. Avoid new sources unless a concept is truly unclear. |
| 14 | Light final review | Review error log, key decision patterns, timing strategy, and exam-day checklist. |
14-day priorities
Spend more time on scenario judgment than memorization. For each missed answer, ask:
- What was the business analysis objective?
- What was the delivery context: predictive, agile, or hybrid?
- Was the question asking for the first action, best action, next action, or problem cause?
- Did the answer preserve business value, stakeholder alignment, and requirements integrity?
The 30-day balanced plan
Use this if you want a realistic schedule while working full time. Plan for 5 study days per week, with one longer weekend session.
30-day weekly structure
| Week | Main focus | Practice target | Mock target |
|---|---|---|---|
| Week 1 | Diagnostic, needs assessment, BA planning | Short domain sets | No full mock unless already prepared |
| Week 2 | Elicitation, requirements analysis, modeling, prioritization | Timed domain sets | Optional half-mock |
| Week 3 | Traceability, change, monitoring, solution evaluation | Mixed scenario sets | Full timed mock near end of week |
| Week 4 | Mixed review, mock analysis, final weak areas | Timed mixed sets | Final mock or timed blocks early in week |
30-day detailed schedule
| Days | Focus | Actions |
|---|---|---|
| 1 | Baseline diagnostic | Take a timed mixed set. Create your error log. |
| 2-3 | Needs assessment | Business need, objectives, value, feasibility, current/future state. |
| 4-5 | Stakeholders and BA planning | Stakeholder register, engagement, communication, governance, BA approach. |
| 6 | Weekly review | Rework misses from days 1-5. |
| 7 | Rest or light flash review | No heavy study unless behind. |
| 8-9 | Elicitation | Technique selection, facilitation, workshops, prototypes, interviews, backlog conversations. |
| 10-11 | Requirements analysis | Functional/nonfunctional requirements, user stories, use cases, models, acceptance criteria. |
| 12 | Prioritization and validation | MoSCoW-style thinking, value/risk/dependency tradeoffs, validation vs. verification. |
| 13 | Timed practice | Timed mixed set from week 2 topics. |
| 14 | Review/rest | Update error log and weak-area list. |
| 15-16 | Traceability | Requirement relationships, traceability matrix, baselines, status. |
| 17 | Change control and impact | Change requests, backlog changes, scope alignment, impact analysis. |
| 18 | Risk and stakeholder conflict | Conflicting needs, escalations, assumptions, constraints, negotiation. |
| 19 | Solution evaluation | Acceptance, transition, benefits, performance, value realization. |
| 20 | Full mock or long timed block | Simulate exam conditions as closely as practical. |
| 21 | Mock review | Spend more time reviewing than testing. |
| 22-23 | Weakest domain repair | Review concepts only where misses show a pattern. |
| 24 | Agile/predictive/hybrid comparison | Practice choosing BA actions by delivery context. |
| 25 | Mixed timed set | Focus on pacing and scenario interpretation. |
| 26 | Final mock or two timed blocks | Use if you have enough energy to review it fully. |
| 27 | Mock explanation review | Rework misses and near-misses. |
| 28 | Final domain sweep | Needs, planning, analysis, traceability, evaluation. |
| 29 | Light review | Error log, decision rules, key terms. |
| 30 | Exam readiness | Rest, logistics, timing plan, light confidence review. |
The 60/90-day full preparation path
Use this if you are new to PMI-style exams, new to formal business analysis, or returning to certification study after a long break.
60-day path
| Phase | Days | Focus | Actions |
|---|---|---|---|
| Foundation | 1-10 | Exam orientation and diagnostic | Review the PMI-PBA scope, take a diagnostic set, build a study tracker. |
| Domain build | 11-25 | Needs assessment and BA planning | Study concepts, then answer domain questions. Do not rush to mocks. |
| Requirements work | 26-38 | Elicitation, analysis, modeling, prioritization | Practice technique selection and scenario judgment. |
| Control and evaluation | 39-48 | Traceability, monitoring, change, solution evaluation | Connect requirements to objectives, value, and outcomes. |
| Integration | 49-55 | Mixed scenario practice | Timed sets across all domains. Review explanations deeply. |
| Final readiness | 56-60 | Mock review and final repair | One final mock or timed blocks, then light review and rest. |
90-day path
| Phase | Weeks | Focus | Actions |
|---|---|---|---|
| Setup and baseline | 1 | Diagnostic and schedule | Identify weak areas and set weekly study blocks. |
| Concepts round 1 | 2-4 | Needs assessment, planning, stakeholders | Build vocabulary and process understanding. |
| Concepts round 2 | 5-7 | Elicitation, requirements analysis, models | Practice selecting tools and techniques by scenario. |
| Lifecycle control | 8-9 | Traceability, change, monitoring, evaluation | Link requirements to benefits, acceptance, and value. |
| Delivery context | 10 | Agile, predictive, hybrid comparison | Practice how BA work changes by delivery approach. |
| Mock cycle | 11-12 | Timed mock exams and repair | Take mocks, review explanations, and target weak areas. |
| Final review | 13 | Light review and readiness | Stop adding new material, stabilize timing, review error log. |
How to use the longer path well
- Do not spend the first half only reading. Start practice questions in week 1.
- Rotate between concept review and scenario practice.
- Keep an error log from the beginning.
- Add timed sets gradually before attempting full timed mocks.
- Use the final third of the plan for mixed practice, not new content collection.
What to practice next
Use this decision table after each study session.
| If your result shows… | Practice next | Avoid |
|---|---|---|
| You miss definition-based questions | Short concept review, then 10-15 targeted questions | Repeating full mocks without fixing basics |
| You know concepts but miss scenarios | Mixed scenario sets and explanation review | More passive reading |
| You run out of time | Timed blocks of 20-30 questions | Untimed practice only |
| You change correct answers to wrong ones | Mark uncertainty, choose once, review decision triggers | Overanalyzing every option |
| You miss agile-context questions | Compare backlog, iteration, product owner, acceptance, and change handling | Applying predictive change control to every case |
| You miss predictive-context questions | Review baselines, approvals, traceability, impact analysis, governance | Treating every change as informal backlog refinement |
| You miss stakeholder questions | Practice conflict, engagement, facilitation, communication, escalation | Choosing answers that ignore stakeholder alignment |
| You miss evaluation questions | Review acceptance, benefits, transition, value realization | Stopping study at requirements approval |
Missed-question review method
A missed question is useful only if you turn it into a rule you can apply later.
Use a simple error log
| Field | What to record |
|---|---|
| Date | When you missed it |
| Domain or topic | Needs, planning, analysis, traceability, evaluation, stakeholder, change, agile, hybrid |
| Question type | Definition, scenario, next action, best action, exception, sequence |
| Why you missed it | Knowledge gap, misread, timing, distractor, delivery-context confusion |
| Correct rule | The principle that would have led to the right answer |
| Recheck date | When you will retry the topic |
Classify each miss
| Miss type | Example | Fix |
|---|---|---|
| Knowledge gap | You did not know a requirement type or elicitation technique | Review the concept, then answer targeted questions |
| Context error | You treated an agile scenario like a predictive change-control scenario | Identify delivery clues before reading options |
| Sequence error | You chose a later action before analysis, validation, or stakeholder engagement | Practice “first/best/next” wording |
| Stakeholder error | You ignored a key stakeholder or communication issue | Ask who must be engaged before a decision is made |
| Value error | You focused on documentation but missed business outcome | Tie the answer back to the original need and benefit |
| Distractor error | You chose a plausible but incomplete answer | Explain why each wrong answer is wrong |
| Timing error | You rushed or spent too long | Use timed sets and a skip/mark strategy |
The 3-pass review process
- Immediate review: Read the explanation and identify why the correct answer is better.
- Delayed rework: Reattempt the missed question or topic 2-3 days later without looking at the answer.
- Rule extraction: Write one sentence that starts with: “In a PMI-PBA scenario, when I see ___, I should ___.”
Timed mock exam strategy
Timed mocks are valuable only when you have enough time to review them. A mock without review is mostly stamina practice.
| Preparation stage | Timed mock use | What to measure |
|---|---|---|
| Early stage | Avoid frequent full mocks | Baseline weaknesses from smaller timed sets |
| Middle stage | Use half-mocks or long timed blocks | Pacing, endurance, recurring weak domains |
| Final third | Use full timed mocks if possible | Exam stamina, decision quality, explanation gaps |
| Final 3-4 days | Use only if it will not cause fatigue | Confidence, light timing practice, not score chasing |
Mock review checklist
After each mock or long timed block, answer:
- Which domains caused the most misses?
- Which misses were due to delivery context: agile, predictive, or hybrid?
- Which questions did I miss even though I knew the concept?
- Did I choose answers that were too technical, too passive, or too document-focused?
- Did I identify the business need before choosing an action?
- Did I review all flagged questions, or did I run out of time?
- What are the three topics I will repair before the next timed set?
PMI-PBA scenario decision habits
PMI-PBA questions often reward judgment. Train yourself to pause before answering.
| Scenario clue | Think about |
|---|---|
| Business problem is unclear | Needs assessment before solution design |
| Stakeholders disagree | Facilitation, engagement, communication, and shared understanding |
| Requirements are changing | Impact analysis, traceability, prioritization, and governance |
| Agile delivery context | Backlog refinement, collaboration, iterative validation, acceptance criteria |
| Predictive delivery context | Baselines, approvals, traceability, change control, formal signoff |
| Hybrid context | Match the response to the part of the work that is iterative or controlled |
| Solution is delivered but value is uncertain | Evaluation, benefits, adoption, performance, and business outcomes |
| A requirement conflicts with a business objective | Revisit value, priority, assumptions, and stakeholder agreement |
Final-week rules
In the final week, your goal is to protect performance.
Stop adding new material
Stop adding new books, courses, or large source materials about 3-5 days before the exam. Use that time for:
- Error log review
- Mock explanation review
- Light targeted practice
- Delivery-context comparison
- Final timing strategy
- Rest and exam logistics
Keep final review focused
| Review item | Final-week action |
|---|---|
| Needs assessment | Know how to identify the real business need and value driver |
| BA planning | Review stakeholder, communication, governance, and approach decisions |
| Requirements analysis | Review requirement types, models, prioritization, validation, acceptance criteria |
| Traceability | Review how requirements connect to objectives, deliverables, tests, and benefits |
| Change | Review impact analysis and delivery-context clues |
| Evaluation | Review acceptance, transition, benefits, and solution performance |
| Mock misses | Rework only the misses that show repeat patterns |
Exam-readiness checks
You are likely ready when most of these are true:
- You can complete timed sets without rushing the final questions.
- Your missed questions are spread out rather than concentrated in one major area.
- You can explain why the correct answer is best, not just recognize it.
- You can identify agile, predictive, and hybrid clues in scenarios.
- You know when to assess need, engage stakeholders, analyze impact, validate requirements, or evaluate the solution.
- You have reviewed your most recent mock or timed set in full.
- You are no longer adding large amounts of new material.
- Your final notes are short enough to review in one sitting.
If several of these are not true, use your remaining time to repair the highest-risk pattern first. Do not try to repair everything equally.
Practical next step
Choose the plan that matches your exam date, take a diagnostic or timed mixed set, and build your error log today. Your next study session should be based on evidence from your misses, not on a guess about what to review next.