PMI CD-BA study plan

Map the full Analysis domain task list into a one-page checklist with each task restated as an action you can perform on a real project

Distinguish elicitation from analysis by writing five example activities and labeling which of the two each belongs to

Practice selecting elicitation techniques by matching six short scenario descriptions to a technique and justifying each choice in one sentence

Draft a stakeholder question bank of 15 open-ended elicitation questions that avoid leading phrasing

Decompose a sample business problem into a context diagram, a functional decomposition, and at least three user stories with acceptance criteria

Compare four requirements modeling approaches (process, data, behavior, rule) and state when each is the better fit

Write verifiable requirements by rewriting ten vague statements into testable ones with explicit acceptance criteria

Identify and correct five common requirements defects such as ambiguity, conflation of solution and need, and missing rationale

Translate the Planning domain tasks into a stakeholder engagement plan template with roles, influence, and communication cadence

Draft a business analysis approach section that names the chosen methodology, its rationale, and the tailoring decisions behind it

Build a governance and information management section covering decision rights, approval thresholds, and requirement storage and access rules

Construct a risk register with six project risks, each with probability, impact, response, and owner

Sequence planning activities against analysis activities on a single timeline and mark the dependencies between them

Run a timed 40-question mixed Planning and Analysis practice set and log the reasoning error behind every miss

Revise your planning document to close gaps revealed by the practice set, noting each change and why

Explain in writing how planning decisions constrain analysis choices, using two concrete examples from your own document

Identify the business problem and its root causes for a given scenario using at least two independent techniques and reconcile the findings

Assess capability gaps by mapping current-state versus desired-state capabilities and flagging the shortfalls

Produce a business case outline with options, costs, benefits, assumptions, constraints, and a recommendation

Define measurable success criteria and a high-level solution scope boundary for the same scenario

Build a requirements traceability matrix linking business need to requirement to design element to test case for a sample initiative

Define a change control process with request intake, impact analysis, approval authority, and communication steps

Practice performing impact analysis on three proposed changes and record affected requirements, effort, and risk for each

Design a monitoring approach that specifies which requirement attributes are tracked, how often, and by whom

Plan a solution evaluation by selecting measures, data sources, and acceptance thresholds tied back to the success criteria from week 5

Analyze three sample evaluation results to determine whether a solution gap exists and recommend a follow-up action for each

Distinguish verification from validation by classifying ten activities and writing one sentence of justification per classification

Review your traceability matrix and confirm every requirement can be evaluated, fixing any orphaned entries

Complete two full-length timed practice exams under exam conditions and record domain-level accuracy for each

Re-study only the two weakest task areas from your error logs and rewrite the affected study notes

Recite from memory the inputs, outputs, and purpose of each domain and correct any gaps against your notes

Build a one-page exam-day reference covering decision rules for ambiguous scenario questions