Business Analysis Planning and Monitoring
What to know
Business analysis planning and monitoring is about deciding how the BA work will be done and then keeping that approach fit for purpose. Know the difference between the business analysis approach (method, deliverables, timing, and level of formality) and the project management plan; exam questions often blur them. Candidates must understand stakeholder analysis-especially influence/impact grids, responsibility matrices, and engagement planning-plus governance, information management, performance measures, and risk. Plan-driven and change-driven approaches are both valid; choose based on uncertainty, regulatory constraints, and stakeholder availability, not personal preference.
Traps
A common trap is treating stakeholder engagement as a one-time kickoff activity. Engagement is planned, monitored, and adjusted. Another is assuming a detailed plan is always better; heavy documentation can be waste in a volatile environment. Watch for answer choices that describe a project schedule or budget as a BA plan. Also distinguish performance measures for BA work (such as requirement rework rate) from solution performance measures.
Worked example
A regulator has high influence but low day-to-day interest. You do not invite them to every workshop; you plan targeted reviews at approval points and record that decision in the stakeholder engagement plan. If their influence later increases, you re-plan.
Rule of thumb
Plan the BA work, but revisit the plan at every major decision point. If the approach no longer fits the level of change and uncertainty, update it.