Handbook
BA perspectives (blueprint)
Purpose: Context-specific guides for how business analysis practices adapt to different organizational and initiative contexts. Each perspective describes how the six knowledge areas shift in emphasis, which techniques…
Audience: Teams adopting Business analysis (BA) who need to calibrate BA practices for their specific situation.
| Guide | Focus | When to Use |
|---|---|---|
| Agile Perspective | Iterative discovery, just-in-time requirements, embedded BA role, collaboration over documentation | Teams using Scrum, Kanban, XP, Dual-Track Agile, or any iterative delivery methodology |
| Business Intelligence | Data requirements, analytics, reporting, data quality, data governance | BI/analytics initiatives, data-driven product decisions, data warehouse/lake projects |
| Business Architecture | Enterprise capability mapping, value streams, organizational alignment, cross-product strategy | Enterprise transformations, capability-based planning, portfolio-level BA |
| Business Process Management | Process modeling, optimization, automation, continuous improvement | Process improvement initiatives, workflow automation, operational efficiency programs |
BABOK v3 IT Perspective: In this blueprint, IT concerns (software architecture, CI/CD, deployment, operations) are already covered by Software delivery. The IT perspective is not duplicated here — instead, the BA ↔ SDLC ↔ PDLC bridge covers how BA interfaces with software delivery.
Combining perspectives: Initiatives often touch multiple perspectives. An enterprise data platform project might use Business Architecture for strategic alignment, Business Intelligence for data requirements, and Agile for delivery methodology. Use perspectives as lenses, not constraints.