CCBA study plan
CCBA · Give each week a clear focus.
8 weeks · About 6 hours per week
Business Analysis Planning and Monitoring
Decompose Business Analysis Planning and Monitoring into its five tasks and state the purpose, inputs, outputs, and stakeholders for each
Draft a one-page BA approach that selects predictive versus adaptive planning, defines prioritization and approval rules, and names the information management artifacts to be used
Construct a stakeholder engagement plan for a 20-person mock organization that assigns each stakeholder a role, influence level, and engagement cadence
Distinguish the responsibilities of the BA, project manager, and sponsor across planning and governance decisions in writing
Your checkpoint
A two-page planning package for a mock project: BA approach summary, stakeholder engagement grid with at least 10 stakeholders, and a governance/approval decision table with 5 rules
Elicitation and Collaboration
Sequence the five Elicitation and Collaboration tasks and identify the conditions that trigger iteration back to an earlier task
Design an elicitation activity plan for three different stakeholder groups, choosing a technique for each and justifying the choice against stakeholder location, availability, and information type
Write 12 elicitation questions that avoid leading phrasing and cover process, data, and rule perspectives
Explain how to confirm and communicate elicitation results, including the difference between stated, unconfirmed, and confirmed requirements
Identify collaboration risks and specify two mitigations for each of three conflict scenarios
Your checkpoint
An elicitation plan plus 12 vetted questions and a collaboration risk register containing 6 risks with mitigations
Requirements Life Cycle Management
Trace 15 sample requirements backward to business objectives and forward to solution components, and label each dependency type
Apply a stated prioritization scheme to the same 15 requirements and defend the resulting order against two competing stakeholder interests
Perform a change impact analysis on one sample change request, covering affected requirements, design, tests, and stakeholders
Outline the approval, baselining, and requirement-reuse workflow to be followed for the remainder of the plan
Detect and correct three deliberately introduced traceability gaps in a provided requirement set
Your checkpoint
A traceability matrix for 15 requirements plus a one-page change impact assessment and a documented approval workflow
Strategy Analysis
Analyze a mock current state using at least three techniques (for example SWOT, process modeling, or capability gap) and record 8 findings
Define a future state with measurable business objectives and success metrics for each
Assess risks and constraints for the change and rank them by likelihood and impact
Define a change strategy that compares at least two solution approaches and states the rationale for the recommended one
Explain how Strategy Analysis outputs feed into Requirements Analysis and Design Definition
Your checkpoint
A current-to-future state gap analysis identifying 8 gaps, 4 measurable business objectives, and a one-page change strategy recommending one of two options
Requirements Analysis and Design Definition
Specify 12 requirements that each pass a written quality checklist of unambiguous, testable, and traceable
Model the same requirements in one process model and one data model, and verify that every requirement appears in at least one model
Validate requirements with a simulated stakeholder review and log the resulting changes
Define design options at the architecture and component level and compare them on cost, risk, and value
Analyze potential value of each design option and recommend one with justification
Your checkpoint
A requirements specification package containing 12 verified requirements with acceptance criteria, two models, and a design-option trade-off table recommending one option
Solution Evaluation
Measure solution performance by selecting 6 measures that map to the business objectives defined in week 4
Analyze the measures to identify 4 limitations, separating solution limitations from enterprise limitations
Recommend corrective actions for each limitation and state the expected effect of each action
Describe how solution evaluation findings may trigger re-entry into Strategy Analysis or Requirements Analysis
Your checkpoint
A solution evaluation scorecard with 6 measures, a baseline-versus-actual comparison, and 4 limitations each paired with a recommended action
Business Analysis Planning and Monitoring & Elicitation and Collaboration & Requirements Life Cycle Management & Strategy Analysis & Requirements Analysis and Design Definition & Solution Evaluation
Map 40-50 named business analysis techniques to the specific tasks where each is most applicable
Classify 120 practice questions by domain and task, then record the reason for every incorrect answer
Diagnose the three weakest tasks from the error log and rewrite a condensed study note for each
Rehearse explaining a cross-domain scenario aloud, connecting a planning decision to an elicitation choice to a requirement outcome
Your checkpoint
A technique-to-task matrix covering at least 40 techniques plus an error log of 120 classified questions with a ranked list of the three weakest tasks
Business Analysis Planning and Monitoring & Elicitation and Collaboration & Requirements Life Cycle Management & Strategy Analysis & Requirements Analysis and Design Definition & Solution Evaluation
Complete two timed 90-question mock exams under exam conditions
Analyze every missed item to distinguish knowledge gaps from misread-question errors
Re-study only the tasks flagged in both mock exams and re-test each with 10 fresh questions
Assemble a one-page pre-exam sheet of decision rules for the domains that remain weakest
Your checkpoint
Two completed timed mock exams scoring at least 80 percent each, with a remediation log showing every missed task re-tested and closed out
Milestones
Week 2: Can state the five tasks, inputs, and outputs for Domains 1 and 2 from memory, and can justify a technique choice for a given stakeholder scenario in under two minutes
Week 4: Can produce a traceability chain from business objective to requirement to solution component without notes, and score at least 70 percent on a 40-question quiz covering Domains 1 through 4
Week 6: Can distinguish solution limitations from enterprise limitations in five out of five sample scenarios and has completed deliverables for all six domains
Week 8: Scores at least 80 percent on two consecutive timed 90-question mocks with no domain below 70 percent