Skip to content
Browse
BABOK Guide
BABOK Guide
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

2.4 Tasks

2.4.2 Plan Stakeholder Communication

Guide to Business Data Analytics

Planning stakeholder communication includes identifying what needs to be communicated, to whom it needs to be communicated, how it needs to be communicated, and when it needs to be communicated. Planning stakeholder communication for an analytics initiative is like most other initiative-level communication planning. It requires analysts to know and understand who the stakeholders are and the communication preferences of individual stakeholders and stakeholder groups.

When planning stakeholder communication, analysts consider:
  • that stakeholder communications can involve an intermediate or final result since analytics initiatives are inherently iterative.
  • the formality and the level of detail may vary amongst stakeholders
  • the level of expertise required by stakeholders to interpret analytics results
  • the level of privacy and confidentiality to be maintained
  • keeping stakeholders informed about the progress and the approaches taken throughout the course of the initiative
  • maintaining an appropriate level of communication during the initiative
  • recording the responses and feedback from stakeholders for further action and follow-up