BASG

BABOK® v3 · Part 11

The five perspectives

Perspectives are lenses through which the same BABOK tasks are applied. They are not disciplines or methodologies — they describe the context a BA is working in. Most real initiatives blend several at once, and recognising which lens dominates helps you choose the right techniques, stakeholders, and level of formality.

01Agile

Perspective

Continuous delivery of value through short, adaptive cycles.

The Agile perspective frames BA work inside iterative, incremental delivery. Requirements emerge progressively, are kept lightweight, and are validated by working product rather than upfront sign-off. The BA collaborates closely with the team and the business — often as a Product Owner proxy, analyst on the team, or coach.

Scope of change

Frequent, small, reversible changes delivered in iterations or a continuous flow. Scope is treated as variable; time and quality are fixed.

What the BA does

  • Help define and refine the product backlog at the right level of detail just-in-time.
  • Facilitate conversations between the team, Product Owner, and stakeholders.
  • Slice work into thin, vertical, demonstrable increments of value.
  • Define acceptance criteria and ensure shared understanding before development.
  • Continuously validate delivered increments against business outcomes.

Key concepts

  • Product Backlog

    Single ordered list of everything that might be needed in the product.

  • User Story

    Short, value-centric statement of need from a user's point of view.

  • Definition of Ready / Done

    Shared agreements on when work is fit to start and fit to release.

  • Just-in-time analysis

    Detail is added only when an item nears implementation.

Common techniques

Typical stakeholders

  • Product Owner
  • Development Team
  • Customer / End users
  • Agile Coach / Scrum Master

Common pitfalls

  • !Treating user stories as mini-specs written upfront instead of conversation placeholders.
  • !Skipping discovery — diving into delivery without a clear product vision or outcome.
  • !Letting the backlog become a wishlist with no ordering by value or risk.
Exam probe

If a stem mentions backlog, iterations, Product Owner, or 'just enough' documentation, it is testing the Agile perspective.

Deep dive · 12 sections + practice quiz

Deep learning module

The frames BA work inside iterative, incremental delivery — requirements emerge progressively, validated by working product.

Problem solved: Stops BAs applying heavy upfront analysis where short cycles, just-in-time detail, and continuous validation deliver more value with less .

Related

Open in Glossary →Practise scenarios →Drill flashcards →

02Business Intelligence

Perspective

Turning data into decisions through analytics and reporting.

The BI perspective focuses on transforming raw data from across the organisation into information used for decision making. The BA bridges business questions and the data, models, and tooling needed to answer them — covering data sourcing, quality, transformation, and consumption.

Scope of change

Initiatives that build or extend reporting, dashboards, data warehouses, lakes, or analytical models — usually cross-functional and data-source heavy.

What the BA does

  • Elicit information needs and the decisions they support.
  • Define data requirements: sources, granularity, latency, quality.
  • Model data structures and the relationships between business entities.
  • Specify reports, dashboards, KPIs, and self-service analytics needs.
  • Address data governance, privacy, and lineage concerns.

Key concepts

  • Data Warehouse / Lake

    Centralised stores optimised for analysis rather than transactions.

  • ETL / ELT

    Pipelines that extract, transform, and load data from source systems.

  • KPI

    Quantifiable measure aligned to a business objective.

  • Data Quality

    Completeness, accuracy, consistency, timeliness, and validity of data.

Common techniques

Typical stakeholders

  • Business decision makers
  • Data stewards / governance
  • Data engineers and analysts
  • Compliance and privacy officers

Common pitfalls

  • !Building reports without confirming the decision they will inform.
  • !Underestimating data quality work — garbage in, garbage out.
  • !Ignoring privacy, retention, and access policies in data design.
Exam probe

Look for stems about reports, dashboards, KPIs, data sources, ETL, or 'a single version of the truth' — these signal the BI perspective.

Deep dive · 12 sections + practice quiz

Deep learning module

The (BI) covers BA work that turns data into decisions through , analytics, dashboards, and data products.

Problem solved: Brings BA discipline to data initiatives where business questions, data sources, quality, , and consumption all need to be aligned.

Related

Open in Glossary →Practise scenarios →Drill flashcards →

03Information Technology

Perspective

Aligning IT systems and services with business needs.

The IT perspective covers BA work performed within or for the IT function — implementing, integrating, modifying, or retiring software and infrastructure. It emphasises the relationship between business capability, application architecture, and supporting technology.

Scope of change

Software development, package implementation, system integration, infrastructure upgrades, and IT service changes — often constrained by enterprise architecture.

What the BA does

  • Translate business needs into functional and non-functional requirements for IT solutions.
  • Assess impact across applications, interfaces, data, and infrastructure.
  • Coordinate with architects, developers, testers, and operations.
  • Specify integrations, interfaces, and service-level expectations.
  • Support testing, deployment readiness, and post-implementation evaluation.

Key concepts

  • Functional vs Non-functional

    What the system does vs how well it does it (performance, security, usability).

  • Enterprise / Solution Architecture

    The structuring of business capabilities, applications, data, and technology.

  • SDLC

    Software Development Life Cycle — the phases a system passes through from idea to retirement.

  • Integration

    How systems exchange data and trigger behaviour across boundaries.

Common techniques

Typical stakeholders

  • Solution / Enterprise Architects
  • Developers and Testers
  • IT Operations and Support
  • Security and Compliance
  • Vendors and Implementation Partners

Common pitfalls

  • !Jumping to a technical solution before the business problem is framed.
  • !Forgetting non-functional requirements until late in the project.
  • !Treating integrations as 'someone else's problem' instead of a first-class requirement.
Exam probe

Stems mentioning systems, interfaces, software releases, NFRs, or vendor packages typically test the IT perspective.

Deep dive · 12 sections + practice quiz

Deep learning module

The Information Technology (IT) covers BA work performed within or for IT — implementing, integrating, modifying, or retiring software and infrastructure.

Problem solved: Aligns business need with system delivery — ensuring functional and non-functional requirements, architecture impact, and integration are addressed deliberately.

Related

Open in Glossary →Practise scenarios →Drill flashcards →

04Business Architecture

Perspective

Holistic view of capabilities, value streams, and strategy.

The Business Architecture perspective takes an enterprise-wide view, describing the organisation in terms of capabilities, value streams, information, and organisation structure. The BA helps align change initiatives with strategy and ensures local decisions reinforce — rather than fragment — the whole.

Scope of change

Strategic, enterprise-level transformations: mergers, restructures, capability uplift, target operating models, and portfolios of related initiatives.

What the BA does

  • Map current and future-state capabilities and value streams.
  • Trace strategy down to portfolios, programmes, and initiatives.
  • Identify capability gaps, redundancies, and dependencies across the enterprise.
  • Influence governance and investment decisions with architectural insight.
  • Maintain consistency between local solutions and enterprise direction.

Key concepts

  • Capability

    What the business does, independent of how it is done.

  • Value Stream

    End-to-end set of activities that deliver value to a stakeholder.

  • Operating Model

    How people, process, information, and technology combine to run the business.

  • Strategy Map

    Visual linkage from objectives down to capabilities and initiatives.

Common techniques

Typical stakeholders

  • Executives and Sponsors
  • Enterprise and Business Architects
  • Portfolio and Programme Managers
  • Business unit leaders

Common pitfalls

  • !Producing architecture artefacts that no decision actually depends on.
  • !Confusing organisation charts with capability models.
  • !Optimising one unit's solution at the expense of enterprise coherence.
Exam probe

Watch for stems about strategy, capabilities, value streams, operating models, or enterprise alignment — these point to Business Architecture.

Deep dive · 12 sections + practice quiz

Deep learning module

The Business Architecture (BA-Arch) takes an enterprise-wide view: capabilities, value streams, information, and organisation structure, aligned to strategy.

Problem solved: Stops local decisions fragmenting the enterprise; ensures change initiatives reinforce a coherent .

Related

Open in Glossary →Practise scenarios →Drill flashcards →

05Business Process Management

Perspective

Designing and improving end-to-end processes that deliver value.

The BPM perspective focuses on understanding, modelling, measuring, and improving the processes by which work gets done. The BA helps the organisation move from ad-hoc, siloed activity to managed, measured, and continuously improved end-to-end processes.

Scope of change

Process improvement, automation, redesign, and management — from incremental optimisation to full re-engineering of value chains.

What the BA does

  • Model current-state processes with the right level of detail and notation.
  • Identify waste, bottlenecks, hand-offs, and variation.
  • Design future-state processes that meet performance and customer goals.
  • Define process metrics and governance for ongoing management.
  • Support transition, training, and change adoption.

Key concepts

  • Value Chain

    Sequence of activities that create value end-to-end.

  • BPMN

    Standard notation for process modelling.

  • Process Performance

    Cycle time, throughput, cost, quality, and customer satisfaction metrics.

  • Process Owner

    Single accountable point for an end-to-end process.

Common techniques

Typical stakeholders

  • Process Owners
  • Operations Managers
  • Front-line workers performing the process
  • Customers of the process
  • Quality and continuous improvement teams

Common pitfalls

  • !Modelling processes in extreme detail without a clear improvement goal.
  • !Designing future-state processes that ignore the people who must run them.
  • !Treating automation as the goal rather than as one possible enabler.
Exam probe

Stems about end-to-end processes, hand-offs, cycle time, BPMN, or process owners are signalling the BPM perspective.

Deep dive · 12 sections + practice quiz

Deep learning module

The focuses on understanding, designing, executing, monitoring, and improving business processes — the repeated patterns by which work gets done.

Problem solved: Where slow, inconsistent, or wasteful processes are the dominant , gives BAs the tools to fix the work itself, not just the systems supporting it.

Related

Open in Glossary →Practise scenarios →Drill flashcards →