Get Started. It's Free
or sign up with your email address
Rocket clouds
BABOK v3 by Mind Map: BABOK v3

1. 3 - BA Planning & Monitoring

1.1. 3.1 - Plan BA Approach

1.1.1. Purpose

1.1.1.1. Is to define an appropriate method to conduct business analysis activities.

1.1.2. Description

1.1.3. Input

1.1.3.1. Needs

1.1.4. Elements

1.1.4.1. Planning Approach

1.1.4.2. Formality & Level of Details of BA deliverables

1.1.4.3. BA Activities

1.1.4.4. Timing of BA work

1.1.4.5. Complexity & Risks

1.1.4.6. Acceptance

1.1.5. Guidelines & Tools

1.1.5.1. BA Performance Assessment

1.1.5.2. Business Policies

1.1.5.3. Expert Judgment

1.1.5.4. Methodologies & Frameworks

1.1.5.5. Stakeholder Engagement Approach

1.1.6. Techniques

1.1.6.1. Brainstorming

1.1.6.2. Business Case

1.1.6.3. Document Analysis

1.1.6.4. Estimation

1.1.6.5. Financial Analysis

1.1.6.6. Functional Decomposition

1.1.6.7. Interview

1.1.6.8. Item Tracking

1.1.6.9. Lessons Learned

1.1.6.10. Process Modeling

1.1.6.11. Reviews

1.1.6.12. Risk Analysis & Management

1.1.6.13. Scope Modeling

1.1.6.14. Survey & Questionnaire

1.1.6.15. Workshops

1.1.7. Stakeholders

1.1.7.1. Domain Subject Matter Expert

1.1.7.2. Project Manager

1.1.7.3. Regulator

1.1.7.4. Sponsor

1.1.8. Output

1.1.8.1. BA Approach

1.2. 3.2 - Plan Stakeholder Engagement

1.2.1. Purpose

1.2.1.1. is to plan an approach for establishing and maintaining effective working relationships with the stakeholders.

1.2.2. Description

1.2.3. Input

1.2.3.1. Needs

1.2.3.2. BA approach

1.2.4. Elements

1.2.4.1. Perform stakeholder analysis

1.2.4.1.1. Roles

1.2.4.1.2. Attitudes

1.2.4.1.3. Decision Making Authority

1.2.4.1.4. Level of power or influence

1.2.4.2. Define stakeholder collaboration

1.2.4.3. Stakeholder communication needs

1.2.5. Guidelines & Tools

1.2.5.1. BA Performance Assessment

1.2.5.2. Change Strategy

1.2.5.3. Current State Description

1.2.6. Techniques

1.2.6.1. Brainstorming

1.2.6.2. Business Rules Analysis

1.2.6.3. Document Analysis

1.2.6.4. Interviews

1.2.6.5. Lessons Learned

1.2.6.6. Mind Mapping

1.2.6.7. Organizational Modelling

1.2.6.8. Process Modeling

1.2.6.9. Risk Analysis and Management

1.2.6.10. Scope Modelling

1.2.6.11. Stakeholder List, Map or Personas

1.2.6.12. Survey or Questionaire

1.2.6.13. Workshops

1.2.7. Stakeholders

1.2.7.1. Customers

1.2.7.2. Domain SME

1.2.7.3. End User

1.2.7.4. Project Manager

1.2.7.5. Regulator

1.2.7.6. Sponsor

1.2.7.7. Supplier

1.2.8. Output

1.2.8.1. Stakeholder Engagement Approach

1.3. 3.3 - Plan Business Analysis Governance

1.3.1. Purpose

1.3.1.1. to define how decisions are made about requirements and designs, including reviews, change controle, approvals and prioritization

1.3.2. Inputs

1.3.2.1. BA Approach

1.3.2.2. Stakeholder Engagement Approach

1.3.3. Elements

1.3.3.1. Decision Making

1.3.3.2. Change Controll Process

1.3.3.2.1. Determine the process for requesting changes

1.3.3.2.2. Determine the elements of the change request

1.3.3.2.3. Determine how changes will be prioritizes

1.3.3.2.4. Determine how changes will be documented

1.3.3.2.5. Determine how changes will be communicated

1.3.3.2.6. Determine who will perform the impact analysis

1.3.3.2.7. Determine who will authorize changes

1.3.3.3. Plan Prioritization Approach

1.3.4. Guidelines & Tools

1.3.4.1. BA Performance Assessment

1.3.4.2. Business Policies

1.3.4.3. Current State Description

1.3.4.4. Legal/Regulatory Information

1.3.5. Techniques

1.3.5.1. Brainstorming

1.3.5.2. Document Analysis

1.3.5.3. Interviews

1.3.5.4. Item Tracking

1.3.5.5. Lessons Learned

1.3.5.6. Organizational Modelling

1.3.5.7. Process Modelling

1.3.5.8. Reviews

1.3.5.9. Survey or Questionaire

1.3.5.10. Workshops

1.3.6. Stakehgolders

1.3.6.1. Domain SME

1.3.6.2. Project Manager

1.3.6.3. Regulator

1.3.6.4. Sponsor

1.3.7. Ouputs

1.3.7.1. Governance Approach

1.4. 3.4 - Plan Business Analysis Information Management

1.4.1. Purpose

1.4.1.1. to develop an approach for how BA information will be stored and accessed

1.4.2. Inputs

1.4.2.1. BA Approach

1.4.2.2. Governance Approach

1.4.2.3. Stakeholder Engagement Approach

1.4.3. Elements

1.4.3.1. Organization of BA Information

1.4.3.2. Level of Abstraction

1.4.3.3. Plan Traceability Approach

1.4.3.4. Plan for Requirements Reuse

1.4.3.5. Storage and Access

1.4.3.6. Requirements Attributes

1.4.4. Guidelines & Tools

1.4.4.1. BA Performance Assessment

1.4.4.2. Business Policies

1.4.4.3. Information Management Tools

1.4.4.4. Legal/Regulatory Information

1.4.5. Techniques

1.4.5.1. Brainstorming

1.4.5.2. Interviews

1.4.5.3. Item Tracking

1.4.5.4. Lessons Learned

1.4.5.5. Mind Mapping

1.4.5.6. Process Modelling

1.4.5.7. Survey or Questionaire

1.4.5.8. Workshops

1.4.6. Stakeholders

1.4.6.1. Domain SME

1.4.6.2. Regulator

1.4.6.3. Sponsor

1.4.7. Outputs

1.4.7.1. Information Management Approach

1.5. 3.5 - Identify Business Analysis Performance Improvements

1.5.1. Purpose

1.5.1.1. to assess BA work and to plan to improve processes where required

1.5.2. Inputs

1.5.2.1. BA Approach

1.5.2.2. Performance Objectives (external)

1.5.3. Elements

1.5.3.1. Performance Analysis

1.5.3.2. Assessment Measures

1.5.3.2.1. Accuracy and Completeness

1.5.3.2.2. Knowledge

1.5.3.2.3. Effectiveness

1.5.3.2.4. Organizational Support

1.5.3.2.5. Significance

1.5.3.2.6. Strategic

1.5.3.2.7. Timeliness

1.5.3.3. Analyze Results

1.5.3.4. Recommend Actions for Improvement

1.5.3.4.1. Preventive

1.5.3.4.2. Corrective

1.5.3.4.3. Improvement

1.5.4. Guidelines & Tools

1.5.4.1. Organizational Performance Standards

1.5.5. Techniques

1.5.5.1. Brainstorming

1.5.5.2. Interviews

1.5.5.3. Item Tracking

1.5.5.4. Lessons Learned

1.5.5.5. Metrics and KPIs

1.5.5.6. Observation

1.5.5.7. Process Analysis

1.5.5.8. Process Modelling

1.5.5.9. Reviews

1.5.5.10. Risk Analysis & Management

1.5.5.11. Root Cause Analysis

1.5.5.12. Survey or Questionaire

1.5.5.13. Workshops

1.5.6. Stakeholders

1.5.6.1. Domain SME

1.5.6.2. Project Manager

1.5.6.3. Sponsor

1.5.7. Outputs

1.5.7.1. BA Performance Assessment

2. 5 - Requirements Life Cycle Management

2.1. 5.1 - Trace Requirements

2.1.1. Purpose

2.1.1.1. to ensure that requirements and designs at different levels are aligned to one another, and to manage the effects of change to one level on related requirements

2.1.2. Description

2.1.2.1. Process Traceability

2.1.2.1.1. Value Chain <--> Business Process <--> Sub-process <--> Activity <--> Task

2.1.2.2. Requirement Traceability

2.1.2.2.1. Business Needs <--> Business Req <--> Stakeholder Req <--> Solution Req (Design, Code & Test)

2.1.3. Inputs

2.1.3.1. Requirements

2.1.3.2. Designs

2.1.4. Elements

2.1.4.1. Level of Formality

2.1.4.2. Relationships

2.1.4.2.1. Derive

2.1.4.2.2. Depends

2.1.4.2.3. Satisfy

2.1.4.2.4. Validate

2.1.4.3. Traceability Repository

2.1.5. Guidelines & Tools

2.1.5.1. Domain Knowledge

2.1.5.2. Information Management Approach

2.1.5.3. Legal/Regulatory Information

2.1.5.4. Requirements Management Tools/Repository

2.1.6. Techniques

2.1.6.1. Business Rules Analysis

2.1.6.2. Functional Decomposition

2.1.6.3. Process Modelling

2.1.6.4. Scope Modelling

2.1.7. Stakeholders

2.1.7.1. Customers

2.1.7.2. Domain SME

2.1.7.3. End User

2.1.7.4. Implementation SME

2.1.7.5. Operational Support

2.1.7.6. Project Manager

2.1.7.7. Sponsor

2.1.7.8. Suppliers

2.1.7.9. Tester

2.1.8. Outputs

2.1.8.1. Requirements (traced)

2.1.8.2. Designs (traced)

2.2. 5.2 - Maintain Requirements

2.2.1. Purpose

2.2.1.1. to retain requirement accuracy and consistency throughout and beyound the change during the entire requirements life cycle, and to support reuse of requirements in other solutions

2.2.2. Inputs

2.2.2.1. Requirements

2.2.2.2. Designs

2.2.3. Elements

2.2.3.1. Maintain Requirements

2.2.3.2. Maintain Attributes

2.2.3.3. Reusing Requirements

2.2.4. Guidelines & Tools

2.2.4.1. Information Management Approach

2.2.5. Techniques

2.2.5.1. Business Rules Analysis

2.2.5.2. Data Flow Diagrams

2.2.5.3. Data Modelling

2.2.5.4. Document Analysis

2.2.5.5. Functional Decomposition

2.2.5.6. Process Modelling

2.2.5.7. Use Cases and Scenarios

2.2.5.8. User Stories

2.2.6. Stakeholders

2.2.6.1. Domain SME

2.2.6.2. Implementation SME

2.2.6.3. Operational Support

2.2.6.4. Regulator

2.2.6.5. Tester

2.2.7. Outputs

2.2.7.1. Requirements (maintained)

2.2.7.2. Designs (maintained)

2.3. 5.3 - Prioritize Requirements

2.3.1. Purpose

2.3.1.1. to rank requirements in the order of relative importance

2.3.2. Inputs

2.3.2.1. Requirements

2.3.2.2. Designs

2.3.3. Elements

2.3.3.1. Basis for Prioritization

2.3.3.1.1. Benefit

2.3.3.1.2. Penalty

2.3.3.1.3. Cost

2.3.3.1.4. Risk

2.3.3.1.5. Dependencies

2.3.3.1.6. Time Sensitivity

2.3.3.1.7. Stability

2.3.3.1.8. Regulatory or Poilicy Compliance

2.3.3.2. Challenges of Prioritization

2.3.3.3. Continual Prioritization

2.3.4. Guidelines & Tools

2.3.4.1. Business Constraints

2.3.4.2. Change Strategy

2.3.4.3. Domain Knowledge

2.3.4.4. Governance Approach

2.3.4.5. Requirements Architecture

2.3.4.6. Requirements Management Tools/Repository

2.3.4.7. Solution Scope

2.3.5. Techniques

2.3.5.1. Backlog Management

2.3.5.2. Business Cases

2.3.5.3. Decision Analysis

2.3.5.4. Estimation

2.3.5.5. Financial Analysis

2.3.5.6. Interviews

2.3.5.7. Item Tracking

2.3.5.8. Priotization

2.3.5.9. Risk Analysis and Management

2.3.5.10. Workshops

2.3.6. Stakeholders

2.3.6.1. Customer

2.3.6.2. End User

2.3.6.3. Implementation SME

2.3.6.4. Project Manager

2.3.6.5. Regulator

2.3.6.6. Sponsor

2.3.7. Outputs

2.3.7.1. Requirements (prioritized)

2.3.7.2. Design (prioritized)

2.4. 5.4 - Assess Requirements Changes

2.4.1. Purpose

2.4.1.1. to evaluate the implications of proposed changes to requirements and designs

2.4.2. Inputs

2.4.2.1. Proposed Change

2.4.2.2. Requirements

2.4.2.3. Designs

2.4.3. Elements

2.4.3.1. Assessment Formality

2.4.3.2. Impact Analysis

2.4.3.2.1. Benefit

2.4.3.2.2. Cost

2.4.3.2.3. Impact

2.4.3.2.4. Schedule

2.4.3.2.5. Urgency

2.4.3.3. Impact Resolution

2.4.4. Guidelines & Tools

2.4.4.1. Change Strategy

2.4.4.2. Domain Knowledge

2.4.4.3. Governance Approach

2.4.4.4. Legal/Regulatory Information

2.4.4.5. Requirements Architecture

2.4.4.6. Solution Scope

2.4.5. Techniques

2.4.5.1. Business Cases

2.4.5.2. Business Rules Analysis

2.4.5.3. Decision Analysis

2.4.5.4. Document Analysis

2.4.5.5. Estimation

2.4.5.6. Financial Analysis

2.4.5.7. Interface Analysis

2.4.5.8. Interviews

2.4.5.9. Item Tracking

2.4.5.10. Risk Analysis and Management

2.4.5.11. Workshops

2.4.6. Stakeholders

2.4.6.1. Customer

2.4.6.2. Domain SME

2.4.6.3. End User

2.4.6.4. Operational Support

2.4.6.5. Project Manager

2.4.6.6. Regulator

2.4.6.7. Sponsor

2.4.6.8. Tester

2.4.7. Outputs

2.4.7.1. Requirements Change Assessment

2.4.7.2. Designs Change Assessment

2.5. 5.5 - Approve Requirements

2.5.1. Purpose

2.5.1.1. to obtain agreement on and approval of requirements and designs for BA work to continue and/or solution construction to proceed

2.5.2. Inputs

2.5.2.1. Requirements (verified)

2.5.2.2. Designs

2.5.3. Elements

2.5.3.1. Understand Stakeholder Roles

2.5.3.2. Conflict and Issue Management

2.5.3.3. Gain Consensus

2.5.3.4. Track and Communicate Approval

2.5.4. Guidelines & Tools

2.5.4.1. Change Strategy

2.5.4.2. Governance Approach

2.5.4.3. Legal/Regulatory Information

2.5.4.4. Requirement Management Tools/Repository

2.5.4.5. Solution Scope

2.5.5. Techniques

2.5.5.1. Acceptance and Evaluation Criteria

2.5.5.2. Decision Analysis

2.5.5.3. Item Tracking

2.5.5.4. Reviews

2.5.5.5. Workshops

2.5.6. Stakeholders

2.5.6.1. Customer

2.5.6.2. Domain SME

2.5.6.3. End User

2.5.6.4. Operational Support

2.5.6.5. Project Manager

2.5.6.6. Regulator

2.5.6.7. Sponsor

2.5.6.8. Tester

2.5.7. Outputs

2.5.7.1. Requirements (approved)

2.5.7.2. Designs (approved)

3. 4 - Elicitation and Collaboration

3.1. 4.1 - Prepare for Elicitation

3.1.1. Purpose

3.1.1.1. to understand the scope or the elicitation activity. Select appropriate techniques and plan for appropriate supporting materials and resources

3.1.2. Inputs

3.1.2.1. Needs

3.1.2.2. Stakeholder Engagement Approach

3.1.3. Elements

3.1.3.1. Understand the Scope of Elicitation

3.1.3.2. Select Elicitation Techniques

3.1.3.3. Set up Logistics

3.1.3.4. Secure Supporting Material

3.1.3.5. Prepare Stakeholders

3.1.4. Guidelines & Tools

3.1.4.1. BA Approach

3.1.4.2. Business Objectives

3.1.4.3. Existing BA Information

3.1.4.4. Potential Value

3.1.5. Techniques

3.1.5.1. Brainstorming

3.1.5.2. Data Mining

3.1.5.3. Document Analysis

3.1.5.4. Estimation

3.1.5.5. Interviews

3.1.5.6. Mind Mapping

3.1.5.7. Risk Analysis & Management

3.1.5.8. Stakeholder List, Map or Personas

3.1.6. Stakeholders

3.1.6.1. Domain SME

3.1.6.2. Project Manager

3.1.6.3. Sponsor

3.1.7. Outputs

3.1.7.1. Elicitaion Activity Plan

3.2. 4.2 - Conduct Elicitation

3.2.1. Purpose

3.2.1.1. to draw out, explore, and identify information relevant to the change

3.2.2. Description

3.2.2.1. Collaborative

3.2.2.2. Research

3.2.2.3. Experiments

3.2.3. Inputs

3.2.3.1. Elicitation Activity Plan

3.2.4. Elements

3.2.4.1. Guide Elicitation Activity

3.2.4.2. Capture Elicitation Outcomes

3.2.5. Guidelines & Tools

3.2.5.1. BA Approach

3.2.5.2. Existing BA Information

3.2.5.3. Stakeholder Engagement Approach

3.2.5.4. Supporting Materials

3.2.6. Techniques

3.2.6.1. Benchmarking and Market Analysis

3.2.6.2. Brainstorming

3.2.6.3. Business Rules Analysis

3.2.6.4. Collaborative Games

3.2.6.5. Concept Modelling

3.2.6.6. Data Mining

3.2.6.7. Data Modelling

3.2.6.8. Document Analysis

3.2.6.9. Focus Groups

3.2.6.10. Interface Analysis

3.2.6.11. Interviews

3.2.6.12. Mind Mapping

3.2.6.13. Observation

3.2.6.14. Process Analysis

3.2.6.15. Process Modeling

3.2.6.16. Prototyping

3.2.6.17. Survey or Questionaire

3.2.6.18. Workshops

3.2.7. Stakeholders

3.2.7.1. Customer

3.2.7.2. Domain SME

3.2.7.3. End User

3.2.7.4. Implementation SME

3.2.7.5. Sponsor

3.2.7.6. Any Stakeholders

3.2.8. Outputs

3.2.8.1. Elicitation Results (unconfirmed)

3.3. 4.3 - Confirm Elicitation Results

3.3.1. Purpose

3.3.1.1. to check the information gathered during an elicitation session for accuracy and consistency with other information

3.3.2. Inputs

3.3.2.1. Elicitation Results (unconfirmed)

3.3.3. Elements

3.3.3.1. Compare Elicitation Results Against Source Information

3.3.3.2. Compare Elicitation Results Against Other Elicitation Results

3.3.4. Guidelines & Tools

3.3.4.1. Elicitation Activity Plan

3.3.4.2. Existing BA Information

3.3.5. Techniques

3.3.5.1. Document Analysis

3.3.5.2. Interviews

3.3.5.3. Reviews

3.3.5.4. Workshops

3.3.6. Stakeholders

3.3.6.1. Domain SME

3.3.6.2. Any Stakeholder

3.3.7. Outputs

3.3.7.1. Elicitation Results (confirmed)

3.4. 4.4 - Communicate BA Information

3.4.1. Purpose

3.4.1.1. to ensure stakeholders have a shared understanding of BA information

3.4.2. Inputs

3.4.2.1. BA Information

3.4.2.2. Stakeholder Engagement Approach

3.4.3. Elements

3.4.3.1. Determine Objectives and Format of Communication

3.4.3.1.1. Formal Documentation

3.4.3.1.2. Informal Documentation

3.4.3.1.3. Preseentations

3.4.3.2. Communicate BA Package

3.4.3.2.1. Group collaboration

3.4.3.2.2. Individual collaboration

3.4.3.2.3. E-mail or other non-verbal methods

3.4.4. Guideline & Tools

3.4.4.1. BA Approach

3.4.4.2. Information Management Approach

3.4.5. Techniques

3.4.5.1. Intervies

3.4.5.2. Reviews

3.4.5.3. Workshops

3.4.6. Stakeholders

3.4.6.1. End User

3.4.6.2. Customer

3.4.6.3. Domain SME

3.4.6.4. Implementation SME

3.4.6.5. Tester

3.4.6.6. Any Stakeholder

3.4.7. Outputs

3.4.7.1. BA Information (communicated)

3.5. 4.5 - Manage Stakeholder Collaboration

3.5.1. Purpose

3.5.1.1. to encourage stakeholders to work towards a common goal

3.5.2. Inputs

3.5.2.1. Stakeholder Engagement Approach

3.5.2.2. BA Performance Assessment

3.5.3. Elements

3.5.3.1. Gain Agreement on Commitments

3.5.3.2. Monitor Stakeholder Engagement

3.5.3.3. Collaboration

3.5.4. Guidelines & Tools

3.5.4.1. BA Approach

3.5.4.2. Business Objectives

3.5.4.3. Future State Description

3.5.4.4. Recommended Actions

3.5.4.5. Risk Analysis Results

3.5.5. Techniques

3.5.5.1. Collaborative Games

3.5.5.2. Lessons Learned

3.5.5.3. Risk Analysis and Management

3.5.5.4. Stakeholder List, Map or Personas

3.5.6. Stakeholders

3.5.6.1. All stakeholders

3.5.7. Outputs

3.5.7.1. Stakeholder Engagement

4. 6 - Strategy Analysis

4.1. 6.1 - Analyze Current State

4.1.1. Purpose

4.1.1.1. to understand the reasons why an enterprise needs to change some aspect of how it operates and what would be directly or indirectly affected by the change

4.1.2. Inputs

4.1.2.1. Elicitation Results

4.1.2.2. Needs

4.1.3. Elements

4.1.3.1. Business Needs

4.1.3.1.1. From the top-down

4.1.3.1.2. From the bottom-up

4.1.3.1.3. From middle management

4.1.3.1.4. From external drivers

4.1.3.2. Organizational Structure & Culture

4.1.3.3. Capabilities & Processes

4.1.3.3.1. capability-centric view

4.1.3.3.2. process-centric view

4.1.3.4. Technology & Infrastructure

4.1.3.5. Plicies

4.1.3.6. Business Architecture

4.1.3.7. Internal Assets

4.1.3.8. External Influencers

4.1.3.8.1. Industry Structure

4.1.3.8.2. Competitors

4.1.3.8.3. Customers

4.1.3.8.4. Suppliers

4.1.3.8.5. Political & Regulatory Environment

4.1.3.8.6. Technology

4.1.3.8.7. Macroeconomic Factors

4.1.3.9. Guidelines & Tools

4.1.3.9.1. BA Approach

4.1.3.9.2. Enterprise Limitation

4.1.3.9.3. Organizational Strategy

4.1.3.9.4. Solution Limitation

4.1.3.9.5. Solution Performance Goals

4.1.3.9.6. Solution Performance Measures

4.1.3.9.7. Stakeholder Analysis Results

4.1.4. Techniques

4.1.4.1. Benchmarking & Market Analysis

4.1.4.2. Business Capability Analysis

4.1.4.3. Business Model Canvas

4.1.4.4. Business Cases

4.1.4.5. Concept Modelling

4.1.4.6. Data Mining

4.1.4.7. Document Analysis

4.1.4.8. Financial Analysis

4.1.4.9. Focus Groups

4.1.4.10. Functional Decomposition

4.1.4.11. Interviews

4.1.4.12. Item Tracking

4.1.4.13. Lessons Learned

4.1.4.14. Metrics & KPIs

4.1.4.15. Mind Mapping

4.1.4.16. Observation

4.1.4.17. Organizational Modelling

4.1.4.18. Process Analysis

4.1.4.19. Process Modelling

4.1.4.20. Risk Analysis and Management

4.1.4.21. Root Cause Analysis

4.1.4.22. Scope Modelling

4.1.4.23. Survey or Questionaire

4.1.4.24. SWOT Analysis

4.1.4.25. Vendor Assessment

4.1.4.26. Workshops

4.1.5. Stakeholders

4.1.5.1. Customer

4.1.5.2. Domain SME

4.1.5.3. End User

4.1.5.4. Implementation SME

4.1.5.5. Operational Support

4.1.5.6. Project Manager

4.1.5.7. Regulator

4.1.5.8. Sponsor

4.1.5.9. Supplier

4.1.5.10. Tester

4.1.6. Outputs

4.1.6.1. Current State Description

4.1.6.2. Business Requirements

4.2. 6.2 - Define Future State

4.2.1. Purpose

4.2.1.1. to determine the set of necessary conditions to meet the business need

4.2.2. Description

4.2.2.1. business processes

4.2.2.2. functions

4.2.2.3. lines of business

4.2.2.4. organization structures

4.2.2.5. staff competencies

4.2.2.6. knowledge and skills

4.2.2.7. training

4.2.2.8. facilities

4.2.2.9. desktop tools

4.2.2.10. organization locations

4.2.2.11. data and information

4.2.2.12. application systems

4.2.2.13. technology infrastructure

4.2.3. Inputs

4.2.3.1. Business Requirements

4.2.4. Elements

4.2.4.1. Business Goals and Objectives

4.2.4.2. Scope of Solution Space

4.2.4.3. Constraints

4.2.4.3.1. budgetary restrictions

4.2.4.3.2. time restrictions

4.2.4.3.3. technology

4.2.4.3.4. infrastructure

4.2.4.3.5. policies

4.2.4.3.6. resources

4.2.4.3.7. skills of the team and stakeholders

4.2.4.3.8. certain stakeholders not be affected by the solution

4.2.4.3.9. compliance with regulations

4.2.4.4. Organizational Structure & Culture

4.2.4.5. Capabilities & Processes

4.2.4.6. Technology and Infrastructure

4.2.4.7. Policies

4.2.4.8. Business Architecture

4.2.4.9. Internal Assets

4.2.4.10. Identify Assumptions

4.2.4.11. Potential Value

4.2.5. Guidelines & Tools

4.2.5.1. Current State Description

4.2.5.2. Metrics & KPIs

4.2.5.3. Organizational Strategy

4.2.6. Techniques

4.2.6.1. Acceptance and Evaluation Criteria

4.2.6.2. Balanced Scorecard

4.2.6.3. Benchmarking and Market Analysis

4.2.6.4. Brainstorming

4.2.6.5. Business Capability Analysis

4.2.6.6. Business Cases

4.2.6.7. Business Model Canvas

4.2.6.8. Decision Analysis

4.2.6.9. Decision Modelling

4.2.6.10. Financial Analysis

4.2.6.11. Functional Decomposition

4.2.6.12. Interviews

4.2.6.13. Lessons Learned

4.2.6.14. Metrics & KPIs

4.2.6.15. Mind Mapping

4.2.6.16. Organizational Modelling

4.2.6.17. Process Modelling

4.2.6.18. Prototyping

4.2.6.19. Scope Modelling

4.2.6.20. Survey or Questionaire

4.2.6.21. SWOT Analysis

4.2.6.22. Vendor Assessment

4.2.6.23. Workshops

4.2.7. Stakeholders

4.2.7.1. Customer

4.2.7.2. Domain SME

4.2.7.3. End User

4.2.7.4. Implementation SME

4.2.7.5. Operational Support

4.2.7.6. Project Manager

4.2.7.7. Regulator

4.2.7.8. Sponsor

4.2.7.9. Supplier

4.2.7.10. Tester

4.2.8. Outputs

4.2.8.1. Business Objectives

4.2.8.2. Future State Description

4.2.8.3. Potential Value

4.3. 6.3 - Assess Risks

4.3.1. Purpose

4.3.1.1. to understand the undesirable consequences of internal and external forces on the enterprise during a transition to, or once in, the future state.

4.3.2. Description

4.3.2.1. possible consequences if the risk occurs

4.3.2.2. impact of those consequences

4.3.2.3. likelihood of the risk

4.3.2.4. potential time frame when the risk might occur

4.3.3. Inputs

4.3.3.1. Business Objectives

4.3.3.2. Elicitation Results (confirmed)

4.3.3.3. Influences

4.3.3.4. Potential Value

4.3.3.5. Requirements (prioritized)

4.3.4. Elements

4.3.4.1. Unknowns

4.3.4.2. Constraints, Assumptions & Dependencies

4.3.4.3. Negative Impact to Value

4.3.4.4. Risk Tolerance

4.3.4.4.1. Risk-aversion

4.3.4.4.2. Neutrality

4.3.4.4.3. Risk-seeking

4.3.4.5. Recommendation

4.3.5. Guidelines & Tools

4.3.5.1. BA Approach

4.3.5.2. Business Policies

4.3.5.3. Change Strategy

4.3.5.4. Current State Description

4.3.5.5. Future State Description

4.3.5.6. Identified Risks

4.3.5.7. Stakeholder Engagement Approach

4.3.6. Techniques

4.3.6.1. Brainstorming

4.3.6.2. Business Cases

4.3.6.3. Decision Analysis

4.3.6.4. Financial Analysis

4.3.6.5. Interviews

4.3.6.6. Lessons Learned

4.3.6.7. Mind Mapping

4.3.6.8. Risk Analysis and Management

4.3.6.9. Root Cause Analysis

4.3.6.10. Survey or Questionaire

4.3.6.11. Workshops

4.3.7. Stakeholders

4.3.7.1. Domain SME

4.3.7.2. Implementation SME

4.3.7.3. Operational Support

4.3.7.4. Project Manager

4.3.7.5. Regulator

4.3.7.6. Sponsor

4.3.7.7. Supplier

4.3.7.8. Tester

4.3.8. Outputs

4.3.8.1. Risk Analysis Results

4.4. 6.4 - Define Change Strategy

4.4.1. Purpose

4.4.1.1. to develop and assess alternative approaches to the change, and then select the recommended approach

4.4.2. Inputs

4.4.2.1. Current State Description

4.4.2.2. Future State Description

4.4.2.3. Risk Analysis Results

4.4.2.4. Stakeholder Engagement Approach

4.4.3. Elements

4.4.3.1. Solution Scope

4.4.3.2. Gap Analysis

4.4.3.2.1. processes

4.4.3.2.2. functions

4.4.3.2.3. lines of business

4.4.3.2.4. organizational structures

4.4.3.2.5. staff competencies

4.4.3.2.6. knowledge and skills

4.4.3.2.7. training

4.4.3.2.8. facilities

4.4.3.2.9. locations

4.4.3.2.10. data and information

4.4.3.2.11. application systems

4.4.3.2.12. technology infrastructure

4.4.3.3. Enterprise Readiness Assessment

4.4.3.4. Change Strategy

4.4.3.5. Transition States & Release Planning

4.4.4. Guidelines & Tools

4.4.4.1. BA Approach

4.4.4.2. Design Options

4.4.4.3. Solution Recommendations

4.4.5. Techniques

4.4.5.1. Balanced Scorecard

4.4.5.2. Benchmarking and Market Analysis

4.4.5.3. Brainstorming

4.4.5.4. Business Capability Analysis

4.4.5.5. Business Cases

4.4.5.6. Business Model Canvas

4.4.5.7. Decision Analysis

4.4.5.8. Estimation

4.4.5.9. Financial Analysis

4.4.5.10. Focus Groups

4.4.5.11. Functional Decomposition

4.4.5.12. Interviews

4.4.5.13. Lessons Learned

4.4.5.14. Mind Mapping

4.4.5.15. Organizational Modelling

4.4.5.16. Process Modelling

4.4.5.17. Scope Modelling

4.4.5.18. SWOT Analysis

4.4.5.19. Vendor Assessment

4.4.5.20. Workshops

4.4.6. Stakeholders

4.4.6.1. Customer

4.4.6.2. Domain SME

4.4.6.3. End User

4.4.6.4. Implementation SME

4.4.6.5. Operational Support

4.4.6.6. Project Manager

4.4.6.7. Regulator

4.4.6.8. Sponsor

4.4.6.9. Supplier

4.4.6.10. Tester

4.4.7. Outputs

4.4.7.1. Change Strategy

4.4.7.2. Solution Scope

5. 7 - Requirements Analysis and Design Definition

5.1. 7.1 - Specify and Model Requirements

5.1.1. Purpose

5.1.1.1. to analyze, synthesize, and refine elicitation results into requirements and designs.

5.1.2. Inputs

5.1.2.1. Elicitation Results

5.1.3. Elements

5.1.3.1. Model Requirements

5.1.3.1.1. Matrices

5.1.3.1.2. Diagrams

5.1.3.1.3. Categories

5.1.3.2. Analyze Requirements

5.1.3.3. Represent Requirements & Attributes

5.1.3.4. Implement the Appropriate Levels of Abstraction

5.1.4. Guideline & Tools

5.1.4.1. Modelling Notations/Standards

5.1.4.2. Modelling Tools

5.1.4.3. Requirements Architecture

5.1.4.4. Requirements Life Cycle Management Tools

5.1.4.5. Solution Scope

5.1.5. Techniques

5.1.5.1. Acceptance and Evaluation Criteria

5.1.5.2. Business Capability Analysis

5.1.5.3. Business Model Canvas

5.1.5.4. Business Rules Analysis

5.1.5.5. Concept Modelling

5.1.5.6. Data Dictionary

5.1.5.7. Data Flow Diagrams

5.1.5.8. Data Modelling

5.1.5.9. Decision Modelling

5.1.5.10. Functional Decomposition

5.1.5.11. Glossary

5.1.5.12. Interface Analysis

5.1.5.13. Non-Functional Requirements Analysis

5.1.5.14. Organizational Modelling

5.1.5.15. Process Modelling

5.1.5.16. Prototyping

5.1.5.17. Roles and Permissions Matrix

5.1.5.18. Root Cause Analysis

5.1.5.19. Scope Modelling

5.1.5.20. Sequence Diagrams

5.1.5.21. Stakeholder List, Map, or Personas

5.1.5.22. State Modelling

5.1.5.23. Use Cases and Scenarios

5.1.5.24. User Stories

5.1.6. Outputs

5.1.6.1. Requirements (specified & modeled)

5.2. 7.2 - Verify Requirements

5.2.1. Purpose

5.2.1.1. to ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve

5.2.2. Inputs

5.2.2.1. Requirements (specified and modelled)

5.2.3. Elements

5.2.3.1. Characteristics of Requirements & Designs Quality

5.2.3.1.1. Atomic

5.2.3.1.2. Complete

5.2.3.1.3. Consistent

5.2.3.1.4. Concise

5.2.3.1.5. Feasible

5.2.3.1.6. Unambiguous

5.2.3.1.7. Testable

5.2.3.1.8. Prioritized

5.2.3.1.9. Understandable

5.2.3.2. Verification Activities

5.2.3.3. Checklists

5.2.4. Guidelines & Tools

5.2.4.1. Requirements Life Cycle Management Tools

5.2.5. Techniques

5.2.5.1. Acceptance and Evaluation Criteria

5.2.5.2. Item Tracking

5.2.5.3. Metrics and Key Performance Indicators (KPIs)

5.2.5.4. Reviews

5.2.6. Outputs

5.2.6.1. Requirements (verified)

5.3. 7.3 - Validate Requirements

5.3.1. Purpose

5.3.1.1. to ensure that all requirements and designs align to the business requirements and support the delivery of needed value.

5.3.2. Inputs

5.3.2.1. Requirements (specified and modelled)

5.3.3. Elements

5.3.3.1. Identify Assumptions

5.3.3.2. Define Measurable Evaluation Criteria

5.3.3.3. Evaluate Alignment with Solution Scope

5.3.4. Guidelines & Tools

5.3.4.1. Business Objectives

5.3.4.2. Future State Description

5.3.4.3. Potential Value

5.3.4.4. Solution Scope

5.3.5. Techniques

5.3.5.1. Acceptance and Evaluation Criteria

5.3.5.2. Document Analysis

5.3.5.3. Financial Analysis

5.3.5.4. Item Tracking

5.3.5.5. Metrics and Key Performance Indicators (KPIs)

5.3.5.6. Reviews

5.3.5.7. Risk Analysis and Management

5.3.6. Output

5.3.6.1. Requirements (validated)

5.4. 7.4 - Define Requirements Architecture

5.4.1. Purpose

5.4.1.1. to ensure that the requirements collectively support one another to fully achieve the objectives

5.4.2. Inputs

5.4.2.1. Information Management Approach

5.4.2.2. Requirements (any state)

5.4.2.3. Solution Scope

5.4.3. Elements

5.4.3.1. Requirements Viewpoints and Views

5.4.3.1.1. Business Models

5.4.3.1.2. Business Process Models

5.4.3.1.3. Data models and information

5.4.3.1.4. User interactions, including Use Cases and/or User Experience

5.4.3.1.5. Audit and security

5.4.3.2. Template Architectures

5.4.3.3. Completeness

5.4.3.4. Relate and Verify Requirements Relationships

5.4.3.4.1. Defined

5.4.3.4.2. Necessary

5.4.3.4.3. Correct

5.4.3.4.4. Unanbiguous

5.4.3.4.5. Consistent

5.4.3.5. Business Analysis Information Architecture

5.4.4. Guidelines & Tools

5.4.4.1. Architecture Management Software

5.4.4.2. Legal/Regulatory Information

5.4.4.3. Methodologies & Frameworks

5.4.5. Techniques

5.4.5.1. Data Modelling

5.4.5.2. Functional Decomposition

5.4.5.3. Interviews

5.4.5.4. Organizational Modelling

5.4.5.5. Scope Modelling

5.4.5.6. Workshops

5.4.6. Output

5.4.6.1. Requirements Architecture

5.5. 7.5 - Define Design Options

5.5.1. Purpose

5.5.1.1. to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state

5.5.2. Inputs

5.5.2.1. Requirements (validated, prioritized)

5.5.2.2. Change Strategy

5.5.2.3. Requirements Architecture

5.5.3. Elements

5.5.3.1. Define Solution Approaches

5.5.3.1.1. Create

5.5.3.1.2. Purchase

5.5.3.1.3. Combination of both

5.5.3.2. Identify Improvement Opportunities

5.5.3.2.1. Increase Efficiencies

5.5.3.2.2. Improve Access to Information

5.5.3.2.3. Identify Additional Capabilities

5.5.3.3. Requirements Allocation

5.5.3.4. Describe Design Options

5.5.4. Guidelines & Tools

5.5.4.1. Existing Solutions

5.5.4.2. Future State Description

5.5.4.3. Requirements (traced)

5.5.4.4. Solution Scope

5.5.5. Techniques

5.5.5.1. Benchmarking and Market Analysis

5.5.5.2. Brainstorming

5.5.5.3. Document Analysis

5.5.5.4. Interviews

5.5.5.5. Lessons Learned

5.5.5.6. Mind Mapping

5.5.5.7. Root Cause Analysis

5.5.5.8. Survey or Questionnaire

5.5.5.9. Vendor Assessment

5.5.5.10. Workshops

5.5.6. Output

5.5.6.1. Design Options

5.6. 7.6 - Analyze Potential Value & Recommend Solution

5.6.1. Purpose

5.6.1.1. to estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements

5.6.2. Inputs

5.6.2.1. Potential Value

5.6.2.2. Design Options

5.6.3. Elements

5.6.3.1. Expected Benefits

5.6.3.2. Expected Costs

5.6.3.2.1. timeline

5.6.3.2.2. effort

5.6.3.2.3. operating costs

5.6.3.2.4. purchase and/or implementation costs

5.6.3.2.5. maintenance costs

5.6.3.2.6. physical resources

5.6.3.2.7. information resources

5.6.3.2.8. human resources

5.6.3.3. Determine Value

5.6.3.4. Assess Design Options and Recommend Solution

5.6.3.4.1. Available Resources

5.6.3.4.2. Constraints on the Solution

5.6.3.4.3. Dependencies between requirements

5.6.4. Guidelines & Tools

5.6.4.1. Business Objectives

5.6.4.2. Current State Description

5.6.4.3. Future State Description

5.6.4.4. Risk Analysis Results

5.6.4.5. Solution Scope

5.6.5. Techniques

5.6.5.1. Acceptance and Evaluation Criteria

5.6.5.2. Backlog Management

5.6.5.3. Brainstorming

5.6.5.4. Business Cases

5.6.5.5. Business Model Canvas

5.6.5.6. Decision Analysis

5.6.5.7. Estimation

5.6.5.8. Financial Analysis

5.6.5.9. Focus Groups

5.6.5.10. Interviews

5.6.5.11. Metrics and Key Performance Indicators (KPIs)

5.6.5.12. Risk Analysis and Management

5.6.5.13. Survey or Questionnaire

5.6.5.14. SWOT Analysis

5.6.5.15. Workshops

5.6.6. Output

5.6.6.1. Solution Recommendation

6. 8 - Solution Evaluation

6.1. 8.1 - Measure Solution Performance

6.1.1. Purpose

6.1.1.1. to define performance measures and use the data collected to evaluate the effectiveness of a solution in relation to the value it brings.

6.1.2. Inputs

6.1.2.1. Business Objectives

6.1.2.2. Implemented Solution (external)

6.1.3. Elements

6.1.3.1. Define Solution Performance Measures

6.1.3.1.1. Quantitative Measures

6.1.3.1.2. Qualitative Measures

6.1.3.2. Validate Performance Measures

6.1.3.3. Collect Performance Measures

6.1.3.3.1. Volume or Sample Size

6.1.3.3.2. Frequency and Timing

6.1.3.3.3. Currency

6.1.4. Guidelines & Tools

6.1.4.1. Change Strategy

6.1.4.2. Future State Description

6.1.4.3. Requirements (validated)

6.1.4.4. Solution Scope

6.1.5. Techniques

6.1.5.1. Acceptance and Evaluation Criteria

6.1.5.2. Benchmarking and Market Analysis

6.1.5.3. Business Cases

6.1.5.4. Data Mining

6.1.5.5. Decision Analysis

6.1.5.6. Focus Groups

6.1.5.7. Metrics and Key Performance Indicators (KPIs)

6.1.5.8. Non-Functional Requirements Analysis

6.1.5.9. Observation

6.1.5.10. Prototyping

6.1.5.11. Survey or Questionnaire

6.1.5.12. Use Cases and Scenarios

6.1.5.13. Vendor Assessment

6.1.6. Output

6.1.6.1. Solution Performance Measures

6.2. 8.2 - Analyze Performance Measures

6.2.1. Purpose

6.2.1.1. to provide insights into the performance of a solution in relation to the value it brings

6.2.2. Inputs

6.2.2.1. Potential Value

6.2.2.2. Solution Performance Measures

6.2.3. Elements

6.2.3.1. Solution Performance versus Desired Value

6.2.3.2. Risks

6.2.3.3. Trends

6.2.3.4. Accuracy

6.2.3.5. Performance Variances

6.2.4. Guidelines & Tools

6.2.4.1. Change Strategy

6.2.4.2. Future State Description

6.2.4.3. Risk Analysis Results

6.2.4.4. Solution Scope

6.2.5. Techniques

6.2.5.1. Acceptance and Evaluation Criteria

6.2.5.2. Benchmarking and Market Analysis

6.2.5.3. Data Mining

6.2.5.4. Interviews

6.2.5.5. Metrics and Key Performance Indicators (KPIs)

6.2.5.6. Observation

6.2.5.7. Risk Analysis and Management

6.2.5.8. Root Cause Analysis

6.2.5.9. Survey or Questionnaire

6.2.6. Output

6.2.6.1. Solution Performance Analysis

6.3. 8.3 - Assess Solution Limitations

6.3.1. Purpose

6.3.1.1. to determine the factors internal to the solution that restrict the full realization of value

6.3.2. Inputs

6.3.2.1. Implemented Solution (external)

6.3.2.2. Solution Performance Analysis

6.3.3. Elements

6.3.3.1. Identify Internal Solution Component Dependencies

6.3.3.2. Investigate Solution Problems

6.3.3.3. Impact Assessment

6.3.3.3.1. severity

6.3.3.3.2. probability

6.3.3.3.3. impact

6.3.3.3.4. capacity to absorb the impact

6.3.4. Guidelines & Tools

6.3.4.1. Change Strategy

6.3.4.2. Risks Analysis Results

6.3.4.3. Solution Scope

6.3.5. Techniques

6.3.5.1. Acceptance and Evaluation Criteria

6.3.5.2. Benchmarking and Market Analysis

6.3.5.3. Business Rules Analysis

6.3.5.4. Data Mining

6.3.5.5. Decision Analysis

6.3.5.6. Interviews

6.3.5.7. Item Tracking

6.3.5.8. Lessons Learned

6.3.5.9. Risk Analysis and Management

6.3.5.10. Root Cause Analysis

6.3.5.11. Survey or Questionnaire

6.3.6. Output

6.3.6.1. Solution Limitation

6.4. 8.4 - Assess Enterprise Limitations

6.4.1. Purpose

6.4.1.1. to determine how factors external to the solution are restricting value realization

6.4.2. Inputs

6.4.2.1. Current State Description

6.4.2.2. Implemented (or Constructed) Solution (external)

6.4.2.3. Solution Performance Analysis

6.4.3. Elements

6.4.3.1. Enterprise Culture Assessment

6.4.3.2. Stakeholder Impact Analysis

6.4.3.2.1. Functions

6.4.3.2.2. Locations

6.4.3.2.3. Concerns

6.4.3.3. Organizational Structure Changes

6.4.3.4. Operational Assessment

6.4.3.4.1. policies and procedures

6.4.3.4.2. capabilities and processes that enable other capabilities

6.4.3.4.3. skill and training needs

6.4.3.4.4. human resources practices

6.4.3.4.5. risk tolerance and management approaches

6.4.3.4.6. tools and technology that support a solution

6.4.4. Guidelines & Tools

6.4.4.1. Business Objectives

6.4.4.2. Change Strategy

6.4.4.3. Future State Descriptions

6.4.4.4. Risk Analysis Results

6.4.4.5. Solution Scope

6.4.5. Techniques

6.4.5.1. Benchmarking and Market Analysis

6.4.5.2. Brainstorming

6.4.5.3. Data Mining

6.4.5.4. Decision Analysis

6.4.5.5. Document Analysis

6.4.5.6. Interviews

6.4.5.7. Item Tracking

6.4.5.8. Lessons Learned

6.4.5.9. Observation

6.4.5.10. Organizational Modelling

6.4.5.11. Process Analysis

6.4.5.12. Process Modelling

6.4.5.13. Risk Analysis and Management

6.4.5.14. Roles and Permissions Matrix

6.4.5.15. Root Cause Analysis

6.4.5.16. Survey or Questionnaire

6.4.5.17. SWOT Analysis

6.4.5.18. Workshops

6.4.6. Stakeholders

6.4.6.1. Customer

6.4.6.2. Domain Subject Matter Expert

6.4.6.3. End User

6.4.6.4. Regulator

6.4.6.5. Sponsor

6.4.7. Output

6.4.7.1. Enterprise Limitation

6.5. 8.5 - Recommend Actions to Increase Solution Value

6.5.1. Purpose

6.5.1.1. to understand the factors that create differences between potential value and actual value, and to recommend a course of action to align them

6.5.2. Inputs

6.5.2.1. Solution Limitation

6.5.2.2. Enterprise Limitation

6.5.3. Elements

6.5.3.1. Adjust Solution Performance Measures

6.5.3.2. Recommendations

6.5.3.2.1. Do Nothing

6.5.3.2.2. Organizational Change

6.5.3.2.3. Reduce Complexity of Interfaces

6.5.3.2.4. Eliminate Redundancy

6.5.3.2.5. Avoid Waste

6.5.3.2.6. Identify Additional Capabilities

6.5.3.2.7. Retire the Solution

6.5.3.2.8. additional factors

6.5.4. Guidelines & Tools

6.5.4.1. Business Objectives

6.5.4.2. Current State Description

6.5.4.3. Solution Scope

6.5.5. Techniques

6.5.5.1. Data Mining

6.5.5.2. Decision Analysis

6.5.5.3. Financial Analysis

6.5.5.4. Focus Groups

6.5.5.5. Organizational Modelling

6.5.5.6. Prioritization

6.5.5.7. Process Analysis

6.5.5.8. Risk Analysis and Management

6.5.5.9. Survey or Questionnaire

6.5.6. Stakeholders

6.5.6.1. Customer

6.5.6.2. Domain Subject Matter Expert

6.5.6.3. End User

6.5.6.4. Regulator

6.5.6.5. Sponsor

6.5.7. Output

6.5.7.1. Recommended Actions

7. 9 - Underlying Competencies

7.1. 9.1 - Analytical Thinking and Problem Solving

7.1.1. 9.1.1 - Creative Thinking

7.1.2. 9.1.2 - Decision Making

7.1.3. 9.1.3 - Learning

7.1.4. 9.1.4 - Problem Solving

7.1.5. 9.1.5 - Systems Thinking

7.1.6. 9.1.6 Conceptual Thinking

7.1.7. 9.1.7 - Visual Thinking

7.2. 9.2 - Behavioural Characteristics

7.2.1. 9.2.1 - Ethics

7.2.2. 9.2.2 - Personal Accountability

7.2.3. 9.2.3 - Trustworthiness

7.2.4. 9.2.4 - Organization and Time Management

7.2.5. 9.2.5 - Adaptability

7.3. 9.3 - Business Knowledge

7.3.1. 9.3.1 - Business Acumen

7.3.2. 9.3.2 - Industry Knowledge

7.3.3. 9.3.3 - Organization Knowledge

7.3.4. 9.3.4 - Solution Knowledge

7.3.5. 9.3.5 - Methodology Knowledge

7.4. 9.4 - Communication Skills

7.4.1. 9.4.1 - Verbal Communication

7.4.2. 9.4.2 - Non-Verbal Communication

7.4.3. 9.4.3 - Written Communication

7.4.4. 9.4.4 - Listening

7.5. 9.5 - Interaction Skills

7.5.1. 9.5.1 - Facilitation

7.5.2. 9.5.2 - Leadership and Influencing

7.5.3. 9.5.3 - Teamwork

7.5.4. 9.5.4 - Negotiation and Conflict Resolution

7.5.5. 9.5.5 - Teaching

7.6. 9.6 - Tools and Technology

7.6.1. 9.6.1 - Office Productivity Tools and Technology

7.6.2. 9.6.2 - Business Analysis Tools and Technology

7.6.3. 9.6.3 - Communication Tools and Technology

8. 10 - Techniques

8.1. 10.1 - Acceptance and Evaluation Criteria

8.1.1. Value Attributes

8.1.2. Assessment

8.1.2.1. Testability

8.1.2.2. Measures

8.2. 10.2 - Backlog Management

8.2.1. Items in the Backlog

8.2.2. Prioritization

8.2.3. Estimation

8.2.4. Managing Changes to the Backlog

8.3. 10.3 - Balanced Scorecard

8.3.1. Learning and Growth Dimension

8.3.2. Business Process Dimension

8.3.3. Customer Dimension

8.3.4. Financial Dimension

8.3.5. Measures or Indicators

8.4. 10.4 - Benchmarking and Market Analysis

8.4.1. Benchmarking

8.4.2. Market Analysis

8.5. 10.5 - Brainstorming

8.5.1. Preparation

8.5.2. Session

8.5.3. Wrap-up

8.6. 10.6 - Business Capability Analysis

8.6.1. Capabilities

8.6.2. Using Capabilities

8.6.3. Performance Expectations

8.6.4. Risk Model

8.6.5. Strategic Planning

8.6.6. Capability Maps

8.7. 10.7 - Business Cases

8.7.1. Need Assessment

8.7.2. Desired Outcomes

8.7.3. Assess Alternatives

8.7.3.1. Scope

8.7.3.2. Feasibility

8.7.3.3. Assumptions, Risks, and Constraints

8.7.3.4. Financial Analysis and Value Assessment

8.7.4. Recommended Solution

8.8. 10.8 - Business Model Canvas

8.8.1. Key Partnerships

8.8.2. Key Activities

8.8.2.1. Value-add

8.8.2.2. Non-value-add

8.8.2.3. Business non-value-add

8.8.3. Key Resources

8.8.3.1. Physical

8.8.3.2. Financial

8.8.3.3. Intellectual

8.8.3.4. Human

8.8.4. Value Proposition

8.8.4.1. products

8.8.4.2. services

8.8.5. Customer Relationships

8.8.5.1. customer acquisition

8.8.5.2. customer retention

8.8.6. Channels

8.8.6.1. communication-oriented

8.8.6.2. delivery-oriented

8.8.7. Customer Segments

8.8.7.1. group customers

8.8.8. Cost Structure

8.8.9. Revenue Streams

8.8.9.1. revenue resulting (a one-time purchase)

8.8.9.2. recurring revenue (periodic payments)

8.8.9.3. Licensing or Subscription fees

8.8.9.4. Transaction or Usage fees

8.8.9.5. Sales

8.8.9.6. Lending, Renting, or Leasing

8.8.10. 10.9 - Business Rules Analysis

8.8.10.1. Definitional Rules

8.8.10.2. Behavioural Rules

8.9. 10.9 - Business Rules Analysis

8.9.1. Business Policy

8.9.2. Regulations

8.9.3. Contracts

8.9.4. Undocumented business policies

8.9.5. norms of the corporate culture

8.9.6. Generally accepted business practies

8.9.7. Definitional Rules

8.9.7.1. A customer must be considered a Preferred Customer if they place more than 10 orders per month.

8.9.8. Behavioural Rules

8.9.8.1. An order must not be placed when the billing address provided by the customer does not match the address on file with the credit card provider.

8.9.8.2. levels of enforcement

8.9.8.2.1. Allow no violations (strictly enforced)

8.9.8.2.2. Override by authorized actor

8.9.8.2.3. Override with explanation

8.9.8.2.4. No active enforcement

8.10. 10.10 - Collaborative Games

8.10.1. Game Purpose

8.10.2. Process

8.10.2.1. an opening step

8.10.2.2. the exploration step

8.10.2.3. a closing step

8.10.3. Outcome

8.10.4. Examples

8.10.4.1. Product Box

8.10.4.2. Affinity Map

8.10.4.3. Fishbowl

8.11. 10.11 - Concept Modelling

9. 11 - Perspectives

9.1. 11.1 - The Agile Perspective

9.1.1. Change Scope

9.1.1.1. Breadth of Change

9.1.1.2. Depth of Change

9.1.1.3. Value and Solutions Delivered

9.1.1.4. Delivery Approach

9.1.1.5. Major Assumptions

9.1.2. Business Analysis Scope

9.1.2.1. Change Sponsor

9.1.2.2. Change Targets and Agents

9.1.2.2.1. Agile team leader

9.1.2.2.2. Customer representative or product owner

9.1.2.2.3. Team members

9.1.2.2.4. External stakeholders

9.1.2.3. Business Analyst Position

9.1.2.4. Business Analysis Outcomes

9.1.3. Approaches and Techniques

9.1.3.1. Approaches

9.1.3.1.1. Crystal Clear

9.1.3.1.2. Disciplined Agile Delivery (DAD)

9.1.3.1.3. Dynamic Systems Development Method (DSDM)

9.1.3.1.4. Evolutionary Project Management (Evo)

9.1.3.1.5. Extreme Programming (XP)

9.1.3.1.6. Feature Driven Development (FDD)

9.1.3.1.7. Kanban

9.1.3.1.8. Scaled Agile Framework®(SAFe™)

9.1.3.1.9. Scrum

9.1.3.2. Techniques

9.1.3.2.1. Behaviour Driven Development (BDD)

9.1.3.2.2. Kano Analysis

9.1.3.2.3. Lightweight Documentation

9.1.3.2.4. MoSCoW Prioritization

9.1.3.2.5. Personas

9.1.3.2.6. Planning Workshop

9.1.3.2.7. Purpose Alignment Model

9.1.3.2.8. Real Options

9.1.3.2.9. Relative Estimation

9.1.3.2.10. Retrospectives

9.1.3.2.11. Story Decomposition

9.1.3.2.12. Story Mapping

9.1.3.2.13. Storyboarding

9.1.3.2.14. Value Stream Mapping

9.1.4. Underlying Competencies

9.1.4.1. Communication and collaboration

9.1.4.2. Patience and tolerance

9.1.4.3. Flexibility and adaptability

9.1.4.4. Ability to handle change

9.1.4.5. Ability to recognize business value

9.1.4.6. Continuous improvement

9.1.5. Impact on Knowledge Areas

9.1.5.1. Business Analysis Planning and Monitoring

9.1.5.2. Elicitation and Collaboration

9.1.5.3. Requirements Life Cycle Management

9.1.5.4. Strategy Analysis

9.1.5.5. Requirements Analysis and Design Definition

9.1.5.6. Solution Evaluation

9.2. 11.2 - The Business Intelligence Perspective

9.2.1. Change Scope

9.2.1.1. Breadth of Change

9.2.1.2. Depth of Change

9.2.1.2.1. executive level

9.2.1.2.2. management level

9.2.1.2.3. process level

9.2.1.2.4. the overall impact of the change on the organization

9.2.1.3. Value and Solutions Delivered

9.2.1.3.1. strategic processes such as market analysis, customer engagement, and product development

9.2.1.3.2. tactical processes such as stock control and financial planning

9.2.1.3.3. operational processes such as credit assessment, fault detection, and accounts payable monitoring

9.2.1.4. Delivery Approach

9.2.1.4.1. at different levels in the organization

9.2.1.4.2. in target functional areas in the organization

9.2.1.5. Major Assumptions

9.2.2. Business Analysis Scope

9.2.2.1. Change Sponsor

9.2.2.2. Change Targets

9.2.2.3. Business Analyst Position

9.2.2.3.1. primary liaison between business intelligence stakeholders and solution providers

9.2.2.3.2. enterprise data modelling

9.2.2.3.3. decision modelling

9.2.2.3.4. dashboards

9.2.2.3.5. ad hoc query design

9.2.2.3.6. Business Analysis Outcomes

9.2.2.4. Methodologies and Approaches

9.2.2.4.1. Methodologies

9.2.2.4.2. Approaches

9.2.2.4.3. Underlying Competencies

9.2.2.4.4. Impact on Knowledge Areas