CBAP study plan
CBAP · Give each week a clear focus.
8 weeks · About 6 hours per week
Requirements Analysis and Design Definition & Business Analysis Planning and Monitoring
Map the six BABOK knowledge areas to the six exam domains and identify which tasks in Requirements Analysis and Design Definition produce the heaviest question volume
Define the difference between requirements, designs, and solution options, and write a one-paragraph distinction for each with a business example
Build a personal glossary of at least 30 core terms drawn from the analysis and planning domains, including traceability, backlog, and prioritization vocabulary
Draft a one-page planning checklist covering how you would decide on approach, stakeholder engagement, governance, and information management for a new initiative
Your checkpoint
A 30-term glossary plus a one-page planning checklist reviewed against your own notes, with at least five gaps flagged for week 2
Requirements Analysis and Design Definition & Business Analysis Planning and Monitoring
Compare the main requirements models (process, data, and behavior-oriented) and select the appropriate model for three different stakeholder scenarios
Practice decomposing a vague business need into verifiable requirements, producing at least ten candidate requirements with acceptance criteria
Analyze how prioritization techniques differ and justify a chosen technique for a fixed-deadline project
Identify the planning tasks that must be revisited when scope changes mid-initiative
Your checkpoint
A requirements package for a fictional initiative: ten verifiable requirements, a chosen model for each, a prioritization rationale, and a traceability stub
Elicitation and Collaboration & Requirements Life Cycle Management
Distinguish elicitation from collaboration and list which elicitation techniques suit which stakeholder availability constraints
Design a stakeholder engagement approach for a project with one hostile and two disengaged stakeholder groups
Draft a requirements life cycle plan covering baselining, change control, and approval authority
Explain how traceability supports impact analysis and construct a small traceability chain from business need to requirement to design element
Your checkpoint
A stakeholder engagement plan plus a change-control and traceability plan for the same fictional initiative, each with named roles and decision rights
Strategy Analysis & Elicitation and Collaboration
Analyze a current-state description and identify at least five capability gaps with supporting evidence
Define future-state capabilities and articulate the business value of each in measurable terms
Assess three solution options against feasibility, risk, and value, and recommend one with a written rationale
Prepare and rehearse a fifteen-minute elicitation session plan including opening, probing questions, and close
Your checkpoint
A strategy analysis brief: current state, at least five gaps, future-state capabilities, and a ranked recommendation across three options
Requirements Life Cycle Management & Requirements Analysis and Design Definition
Trace a requirement through a simulated change request and document the resulting impact on design, testing, and scope
Apply requirements verification criteria to a set of twenty requirements and rewrite the weakest five
Explain how requirements attributes support prioritization and reuse, and assign attributes to your requirement set
Reconcile conflicting requirements from two stakeholder groups using a documented resolution approach
Your checkpoint
A revised requirement set of twenty requirements with attributes, verification notes, and a written conflict resolution record
Solution Evaluation & Strategy Analysis
Define solution performance measures and distinguish them from project delivery measures
Assess a delivered solution against its intended value and identify at least three limiting factors
Recommend corrective action for a solution that underperforms on adoption but meets functional expectations
Revisit your week 4 recommendation and note what new evaluation evidence would change it
Your checkpoint
A solution evaluation report with four performance measures, three limiting factors, and recommended actions tied to evidence
Business Analysis Planning and Monitoring & Requirements Life Cycle Management & Solution Evaluation
Integrate planning, life cycle, and evaluation concepts by writing a governance summary for a multi-phase initiative
Diagnose which domain a given scenario question is testing before choosing an answer, practicing on at least forty scenario items
Identify your three weakest domain areas from practice results and list the specific tasks to review
Review your glossary and correct or expand at least ten entries based on new understanding
Your checkpoint
A practice log of forty scenario items with domain classification, your answer, the correct reasoning, and a ranked list of three weak areas
Elicitation and Collaboration & Strategy Analysis & Requirements Analysis and Design Definition
Complete at least two full timed practice sets and record domain-level accuracy for each
Rework every missed item from week 7 and week 8 until you can state the underlying concept without notes
Consolidate the planning checklist, engagement plan, strategy brief, and evaluation report into a single one-page concept map
Confirm readiness by stating the decision criteria you would apply to any question where two answers seem defensible
Your checkpoint
A final readiness summary showing domain-level accuracy trends, a one-page concept map, and a written list of remaining weak spots with a review schedule
Milestones
Week 2: Can produce ten verifiable requirements with acceptance criteria and justify a model choice for each without notes
Week 4: Can articulate current state, future state, gaps, and a ranked solution recommendation in under fifteen minutes
Week 6: Can distinguish solution performance measures from delivery measures and name three limiting factors in a sample scenario
Week 8: Domain-level practice accuracy is stable across two timed sets and every missed item has been reworked to a stated concept