BABOK Guide Notes: Chapter 3 - Business Analysis Planning and Monitoring - Comprehensive Study Notes

Plan Business Analysis Approach

• Purpose: define an appropriate method to conduct business analysis activities.
• Description: describes the overall method to perform BA work on an initiative, including how and when tasks will be performed and the deliverables to be produced. May include an initial set of techniques; this list may evolve as understanding of the change and stakeholders deepens.
  • Can be defined by a specific methodology or organizational standards.
  • In some organizations, elements are standardized into a repeatable BA process that can be reused for multiple efforts; even then it may be tailored for a specific initiative.
  • Tailoring is governed by standards that define permitted approaches, what can be tailored, and general guidelines for selection.
  • If no organizational standards exist, the BA collaborates with stakeholders to determine how work will be completed.
  • If delivered via a project, standards and approach may be developed during project planning.
• The BA approach should:
  • align to the overall goals of the change,
  • coordinate BA tasks with the broader change activities and deliverables,
  • include tasks to manage risks affecting quality or efficiency,
  • leverage approaches, techniques, and tools that have historically been effective.
• Inputs: Needs (the problem or opportunity) shape the BA approach; understanding evolves during planning.
• Outputs: BA Approach; BA Performance Assessment; Stakeholder Engagement Approach; Governance Approach; Information Management Approach; Performance Improvements; needs; other related outputs.
• 3.1.5 Guidelines and Tools
  • BA Performance Assessment: leverage results of previous assessments in planning.
  • Business Policies: define decision limits (regulations, contracts, deals, warranties, certifications, etc.) and can influence the BA approach.
  • Expert Judgment: from stakeholders, Centers of Excellence, consultants, industry groups; prior experiences of BA and stakeholders considered when selecting or adjusting an approach.
  • Methodologies and Frameworks: shape the approach; may require tailoring.
  • Stakeholder Engagement Approach: stakeholder understanding and engagement shape decisions about the BA approach.
• 3.1.6 Techniques
  • Brainstorming; Business Cases; Document Analysis; Estimation; Financial Analysis; Functional Decomposition; Interviews; Item Tracking; Lessons Learned; Process Modelling; Reviews; Risk Analysis and Management; Scope Modelling; Survey/Questionnaire; Workshops.
• 3.1.7 Stakeholders (examples)
  • Domain Subject Matter Expert; Project Manager; Regulator; Sponsor.
• 3.1.8 Outputs
  • Business Analysis Approach: identifies the approach and activities, including who will perform them, timing, sequencing, deliverables, and techniques.
  • Notes: remaining planning outputs may be integrated or stand-alone depending on methodology.

Core Concept Model in Plan BA Planning and Monitoring

• The Core Concept Model (BACCM) describes relationships among six core concepts.
• In Plan BA Planning and Monitoring, each core concept has a usage description:
  • Change: transformation in response to a need; determine how changes to BA results will be requested/authorized.
  • Need: problem or opportunity; select an approach that provides adequate analysis for the change.
  • Solution: a way to satisfy needs; evaluate whether BA performance contributed to successful implementation.
  • Stakeholder: group/individual related to change, need, or solution; perform stakeholder analysis to reflect needs and characteristics.
  • Value: worth/importance/usefulness to a stakeholder; conduct performance analysis to ensure BA activities continue to provide value.
  • Context: circumstances that influence/are influenced by the change; ensure complete understanding of context to develop an efficient BA approach.
• Figure/Table reference: Table 3.0.1 shows the usage of BACCM concepts in this knowledge area (The Core Concept Model in BA Planning and Monitoring). $Table exttt{ 3.0.1}$

Input/Output Diagram (illustrative)

• Figure 3.0.1: Input/Output Diagram for Plan BA Approach and related tasks.
• Inputs include: Needs; Business Analysis Approach; Stakeholder Engagement Approach; Governance Approach; Information Management Approach; Performance Improvements; external Needs/Performance Objectives.
• Outputs include: 3.1 BA Approach; 3.2 Stakeholder Engagement Approach; 3.3 Governance Approach; 3.4 Information Management Approach; 3.5 BA Performance Assessment; and other related outputs.

Plan Stakeholder Engagement

3.2 Plan Stakeholder Engagement

• Purpose: plan an approach for establishing and maintaining effective working relationships with stakeholders.
• Description: conduct thorough stakeholder analysis to identify all involved stakeholders and analyze their characteristics; results define collaboration and communication approaches and plan for stakeholder risks.
• Inputs:
  • Needs: understanding the business need and affected parts of the enterprise helps identify stakeholders; needs may evolve as analysis progresses.
  • BA Approach: incorporate the overall BA approach into stakeholder analysis, ensuring consistency.
• 3.2.4 Elements
  • 3.2.1 Perform Stakeholder Analysis: identify stakeholders and their characteristics; analyze information repeatedly as BA activities continue; ensure stakeholders are not overlooked; late identification can miss critical needs.
  • Stakeholder roles: define who contributes and how.
  • Attitudes: assess stakeholder attitudes toward goals, BA, change, and collaboration to tailor engagement.
  • Decision Making Authority: identify who can propose, review, approve changes and decisions; escalate when consensus cannot be reached.
  • Level of Power/Influence: map influence structures to plan buy-in and collaboration; adjust plans if mismatch exists.
  • Define Stakeholder Collaboration: plan for internal vs external collaboration; timelines, location, tools, delivery method, and stakeholder preferences.
  • Stakeholder Communication Needs: determine what to communicate, delivery method, audience, timing, frequency, geography, level of detail, and formality; document in a Stakeholder Communication Plan.
• 3.2.5 Guidelines and Tools
  • BA Performance Assessment; Change Strategy; Current State Description; Legal/Regulatory Information; Information about stakeholders and communication needs.
• 3.2.6 Techniques
  • Brainstorming; Business Rules Analysis; Document Analysis; Interviews; Lessons Learned; Mind Mapping; Organizational Modelling; Process Modelling; Risk Analysis and Management.
• 3.2.7 Stakeholders (examples)
  • Customers; Domain Subject Matter Expert; End User; Project Manager; Regulator; Sponsor; Supplier.
• 3.2.8 Outputs
  • Stakeholder Engagement Approach: lists stakeholders, their characteristics, roles/responsibilities, collaboration and communication approaches.

Plan Business Analysis Governance

3.3 Plan Business Analysis Governance

• Purpose: define how decisions are made about requirements and designs, including reviews, change control, approvals, and prioritization.
• Description: ensure a governance process is in place; clarifies ambiguities; identifies decision makers, processes, and information required for decisions; describes approvals/prioritization for requirements/designs.
• Inputs:
  • BA Approach; Stakeholder Engagement Approach; Business Policies; Current State Description; etc.
• 3.3.4 Elements
  • 1) Decision Making: decisions are made throughout the initiative; roles may include participant, SME, reviewer, approver; escalation paths defined for when consensus fails.
  • 2) Change Control Process: define process for requesting changes, elements of change requests, prioritization, documentation, communication, and authorization.
  • 3) Plan Prioritization Approach: determine formality, participants, process, criteria (e.g., cost, risk, value).
  • 4) Plan for Approvals: determine type of content to be approved, timing, process, and who approves; consider organizational culture and regulatory needs; track approvals.
• 3.3.5 Guidelines and Tools
  • BA Performance Assessment; Business Policies; Current State Description; Legal/Regulatory Information.
• 3.3.6 Techniques
  • Brainstorming; Document Analysis; Interviews; Item Tracking; Lessons Learned; Organizational Modelling; Process Modelling; Reviews; Survey/Questionnaire; Workshops.
• 3.3.7 Stakeholders
  • Domain Subject Matter Expert; Project Manager; Regulator.
• 3.3.8 Outputs
  • Governance Approach: defines stakeholders with decision rights, prioritization and change management for BA work.

Plan Business Analysis Information Management

3.4 Plan Business Analysis Information Management

• Purpose: develop an approach for storing and accessing BA information.
• Description: BA information includes elicitation results, requirements, designs, models, stakeholder concerns, and options; captures working artifacts from lightweight user stories to formal documents and prototypes.
• Inputs:
  • BA Approach; Governance Approach; Stakeholder Engagement Approach (for information needs);
• 3.4.4 Elements
  • 1) Organization of BA Information: structure to ensure efficient access, avoid conflicts/duplication, support cross-initiative use, and enable long-term storage.
  • 2) Level of Abstraction: breadth/depth of information; tailor detail to stakeholder roles; higher detail for high-risk or important topics.
  • 3) Plan Traceability Approach: based on complexity, number of views, risks, standards, regulatory requirements, and cost/benefit of tracing; balance value with overhead.
  • 4) Plan for Requirements Reuse: identify reusable requirements (regulatory, contractual, quality standards, SLAs, business rules, processes, product descriptions); consider reuse across systems.
  • 5) Storage and Access: decisions on where/in what tools to store information; consider access needs and tool capabilities; include status tracking and versioning.
  • 6) Requirements Attributes: metadata to support trade-offs, stakeholder impact, and change impact; common attributes include Absolute reference, Author, Complexity, Ownership, Priority, Risks, Source, Stability, Status, Urgency.
• 3.4.5 Guidelines and Tools
  • BA Performance Assessment; Business Policies; Information Management Tools; Legal/Regulatory Information.
• 3.4.6 Techniques
  • Brainstorming; Interviews; Item Tracking; Lessons Learned; Mind Mapping; Process Modelling.
• 3.4.7 Stakeholders
  • Domain Subject Matter Expert; Regulator; Sponsor.
• 3.4.8 Outputs
  • Information Management Approach: defines how information is stored, accessed, and used during and after the change.

Identify Business Analysis Performance Improvements

3.5 Identify Business Analysis Performance Improvements

• Purpose: assess BA work and plan improvements where needed.
• Description: establish performance measures, conduct performance analysis, report results, and identify preventive, corrective, and developmental actions to improve BA processes; performance analysis should occur throughout the initiative.
• Inputs:
  • BA Approach (deliverables, activities, timing, participants, techniques);
  • External Performance Objectives describing desired outcomes.
• 3.5.4 Elements
  • 1) Performance Analysis: effectiveness depends on context; reporting can be informal or formal; align reports to reviewers’ needs.
  • 2) Assessment Measures: reuse existing measures or elicit new ones; measures can be based on deliverable due dates, etc.
  • 3) Analyze Results: compare process/deliverables against measures; may be assessed by stakeholders, COE, or managers; targets set by organizations.
  • 4) Recommend Actions for Improvement: categorize actions as Preventive, Corrective, or Improvement; may lead to changes in BA approach, processes, and tools.
• 3.5.5 Guidelines and Tools
  • Organizational Performance Standards; previous performance data; information about performance expectations.
• 3.5.6 Techniques
  • Brainstorming; Interviews; Item Tracking; Lessons Learned; Metrics/KPIs; Observation; Process Analysis; Process Modelling; Reviews; Risk Analysis and Management; Root Cause Analysis; Survey/Questionnaire; Workshops.
• 3.5.7 Stakeholders
  • Domain Subject Matter Experts; Project Manager; Sponsor.
• 3.5.8 Outputs
  • BA Performance Assessment: comparison of planned vs. actual performance; root causes of variances; proposed corrective/preventive/improvement actions; findings to guide future work.

Connections, Implications, and Practical Takeaways

• Integrated planning: The five planning outputs (Approach, Stakeholder Engagement, Governance, Information Management, and Performance Improvements) are designed to be coherent and mutually reinforcing; changes in one area may necessitate updates in others.
• Iterative planning: Planning typically occurs more than once; plans are updated as conditions change and new issues arise. Flexibility and tailoring are essential.
• Risk and compliance emphasis: Governance, change control, approvals, and information management are critical for risk mitigation, regulatory compliance, and auditability.
• Stakeholder-centric mindset: The Stakeholder Engagement planning emphasizes stakeholder analysis, attitudes, power/influence, collaboration, and communication needs to ensure sustained engagement and buy-in.
• Value realization: BACCM concepts guide decision making to ensure changes deliver value to stakeholders within the given context.
• Ethical and practical considerations:
  • Ensure inclusive engagement and avoid bias in stakeholder analysis and collaboration.
  • Maintain transparency in decision-making and escalation paths.
  • Respect data privacy and regulatory constraints in information management.
  • Balance formality with adaptability; overly rigid processes can hinder timely value delivery in dynamic environments.

Quick Reference: Key BACCM Concepts in Planning and Monitoring

• Change: transformation in response to a need; planning queries revolve around how requests for changes to BA results will be made and authorized.
• Need: problem or opportunity; select an approach that provides adequate analysis for the change.
• Solution: a means to satisfy one or more needs; assess whether BA contributed to successful implementation.
• Stakeholder: individuals or groups affected by the change; perform stakeholder analysis to reflect needs and characteristics.
• Value: usefulness or importance to stakeholders within the context; assess ongoing value delivery through performance analysis.
• Context: circumstances surrounding the change; ensure a complete understanding to plan an efficient BA approach.

Figures and Diagrams Mentioned

• Figure 3.0.1: BA Planning and Monitoring Input/Output diagram (illustrates inputs/outputs among planning tasks).
• Figure 3.1.1: Plan BA Approach Input/Output Diagram (illustrates how inputs flow into outputs for 3.1).

Notable Enumerations and Examples (from the transcript)

• 3.1 Plan BA Approach includes inputs (Needs) and outputs (BA Approach; related planning outputs).
• 3.2 Plan Stakeholder Engagement includes performs stakeholder analysis, stakeholder roles, attitudes, authority, influence, collaboration planning, and communication planning.
• 3.3 Plan BA Governance includes decision making, change control, prioritization, approvals, and documentation/communication of changes.
• 3.4 Plan BA Information Management includes organization, abstraction level, traceability, reuse, storage/access, and attributes for requirements (e.g., Absolute reference, Complexity, Ownership, Priority, Status, Urgency).
• 3.5 Identify BA Performance Improvements includes performance analysis, assessment measures, results analysis, and actionable improvements (preventive, corrective, improvement).

Important Definitions and Terms (glossary-style)

• Governance approach: the structure and process by which BA decisions are made, approved, prioritized, and documented.
• Change control: the formal process for proposing, evaluating, prioritizing, and communicating changes to BA deliverables.
• Traceability: the ability to follow requirements from origin to implementation and across changes; planned to add value with acceptable overhead.
• Reuse: planning for requirements that can be used across multiple initiatives or over time to save effort and maintain consistency.
• Stakeholder analysis: repeated process of identifying stakeholders, understanding their characteristics, needs, and influence on the change.
• Attitudes: stakeholders’ positive/negative dispositions toward goals and BA activities; informs collaboration strategy.
• KPIs and performance measures: quantitative and qualitative metrics used to assess BA performance and guide improvements.

Formatted Equations/LaTeX Snippets (examples for study use)

• Core Concept Model: BACCM includes the following six concepts: Change, Need, Solution, Stakeholder, Value, Context. Used to guide planning/monitoring decisions across the BA planning knowledge areas.
• Example of a table reference: $Table\ 3.0.1$: The Core Concept Model in Business Analysis Planning and Monitoring.
• Example of a section reference: Plan Business Analysis Approach is labeled as $3.1$; Plan Stakeholder Engagement as $3.2$; Plan BA Governance as $3.3$; Plan BA Information Management as $3.4$; Identify BA Performance Improvements as $3.5$.