Business Analysis Planning and Monitoring
Organizes and coordinates the efforts of business analysts and stakeholders. Defines how BA work will be performed, governed, and improved across the initiative — including the approach, stakeholder engagement, governance, information management, and performance measurement.
Decides how the BA work itself will be organised, governed, and improved.
Every other knowledge area is performed inside the plan this one produces. If planning is wrong — wrong stakeholders, wrong cadence, wrong decision rights — the rest of the work degrades silently. BAPM is also where the BA earns the right to push back on scope, governance, and engagement before the project's politics harden.
In practice
On day one, the BA sketches the approach (predictive, adaptive, hybrid), maps stakeholders by influence and attitude, agrees how requirements will be approved and changed, and defines what 'good' BA work looks like for this initiative. Plans are revisited after every major scope or stakeholder change — they are living artefacts, not one-off deliverables.
Relationships with other knowledge areas
- →Feeds Elicitation & Collaboration with the engagement plan and approach.
- →Feeds Requirements Life Cycle Management with governance and prioritisation rules.
- →Receives performance feedback from Solution Evaluation to improve future BA work.
- →Bounded by Strategy Analysis: planning serves the change strategy, not the other way around.
Where this lands on the exam
BACCM touchpoints
- Stakeholder. Identifies and analyses every stakeholder before work begins.
- Context. Tailors the BA approach to the organisation's culture and constraints.
- Change. Establishes how the change will be steered and re-planned.
Language to listen for in scenario stems
When a stem asks 'what should the BA do first', 'how should BA work be organised', or 'who decides', it is testing BAPM.
Key concepts
The ideas that anchor everything else in this knowledge area.
Predictive (plan-driven, waterfall) approaches define requirements upfront; adaptive (agile) approaches discover them iteratively. Most real initiatives sit on a spectrum.
Identifying who has influence, interest, authority, and attitude toward the change — and tailoring collaboration accordingly.
Who makes decisions, how requirements are approved, prioritized, and changed, and how conflicts are resolved.
Quality and timeliness of BA work itself — measured, reviewed, and improved like any other discipline.
Common pitfalls
Patterns that frequently cost initiatives — and exam points.
- ⚠Treating planning as a one-off activity instead of revisiting it as the initiative evolves.
- ⚠Identifying stakeholders as job titles only, missing influence and attitude.
- ⚠No agreed governance — every requirement change becomes a debate.
- ⚠Measuring BA effort (hours) instead of BA outcomes (quality, value).
Tasks
The 5 tasks that make up this knowledge area. Click any task to expand its inputs, outputs, techniques, and guidelines. Technique tags are clickable.