top of page

Analyze Current State

Purpose

  • Understand need for changes

  • Identify impacts

Description

  • Rooted in need comprehension

  • Analysts articulate business needs

  • Context includes stakeholders, processes, tech

  • Validates change need and strategy

  • Identifies changes for future state

  • Scope sets analysis boundaries

  • Dynamic Nature

    • Current state changes during development

    • Influencers impact state and strategy

Inputs

  • Elicitation Results: Define current state.

  • Needs: Identify problems/opportunities.

Elements

  • Business Needs

    • Definition: Strategic issues.

    • Identification Levels: Top-down, bottom-up, external.

    • Importance: Crucial for success.

    • Considerations: Impacts, benefits, causes.

  • Structure and Culture

    • Structure: Formal relationships.

    • Culture: Shared beliefs, values.

  • Capabilities and Processes

    • Definition: Activities, knowledge, products.

    • Views: Innovation, performance.

  • Technology and Infrastructure

    • Systems, environment.

  • Policies

    • Scope: Decision boundaries.

    • Influence: Constraints, drivers.

  • Business Architecture

    • Interconnectedness: Essential for change.

  • Assets

    • Identification: Tangible, intangible resources.

  • External Influences

    • Industry, Competitors, Customers, Suppliers, Regulation, Technology, Macroeconomics.

    • Impact: Constraints, dependencies.

Guidelines and Tools

  • Business Analysis Approach: Guides analysis.

  • Enterprise Limitation: Understands challenges.

  • Organizational Strategy: Sets goals.

  • Solution Limitation: Identifies challenges.

  • Solution Performance Goals: Measures performance.

  • Solution Performance Measures: Describes performance.

  • Stakeholder Analysis Results: Understands perspectives.

Techniques

  • Benchmarking and Market Analysis: Identifies opportunities.

  • Business Capability Analysis: Prioritizes gaps.

  • Business Model Canvas: Understands value.

  • Business Cases: Captures need.

  • Concept Modelling: Defines terms.

  • Data Mining: Gathers information.

  • Document Analysis: Reviews documentation.

  • Financial Analysis: Assesses profitability.

  • Focus Groups: Solicits feedback.

  • Functional Decomposition: Breaks down systems.

  • Interviews: Gathers insights.

  • Item Tracking: Manages issues.

  • Lessons Learned: Assesses past efforts.

  • Metrics and KPIs: Measures performance.

  • Mind Mapping: Explores aspects.

  • Observation: Provides insights.

  • Organizational Modelling: Describes roles.

  • Process Analysis: Identifies opportunities.

  • Process Modelling: Describes workflows.

  • Risk Analysis: Identifies risks.

  • Root Cause Analysis: Understands problems.

  • Scope Modelling: Defines boundaries.

  • Survey or Questionnaire: Gathers insights.

  • SWOT Analysis: Evaluates factors.

  • Vendor Assessment: Evaluates vendors.

  • Workshops: Collaborates on needs.

Stakeholders:

  • Customer: Provides feedback.

  • Domain SME: Offers expertise.

  • End User: Provides direct feedback.

  • Implementation SME: Offers implementation expertise.

  • Operational Support: Provides operational insights.

  • Project Manager: Uses information for planning.

  • Regulator: Informs compliance.

  • Sponsor: Provides performance context.

  • Supplier: External influencer.

  • Tester: Identifies issues.

Outputs:

  • Current State Description: Context of enterprise elements.

  • Business Requirements: Defined problems/opportunities.

bottom of page