10.1 Business Analysis in Predictive and Agile Approaches
Key Takeaways
- In predictive projects, business analysis happens primarily upfront with detailed requirements documentation before development begins
- In agile projects, business analysis is continuous — requirements are refined iteratively through backlog refinement and sprint planning
- The BA role in predictive projects focuses on comprehensive documentation, formal sign-offs, and detailed traceability
- The BA role in agile projects may be performed by the Product Owner or embedded in the development team as a dedicated BA
- Hybrid projects combine upfront business requirements analysis with agile delivery of solution requirements
Last updated: March 2026
Business Analysis in Predictive and Agile Approaches
How business analysis is performed depends significantly on the project methodology. The CAPM exam tests your understanding of how BA processes, roles, and artifacts differ between predictive and agile approaches.
Business Analysis in Predictive Projects
In predictive projects, business analysis is primarily a front-loaded activity:
BA Activities by Phase
| Phase | BA Activities |
|---|---|
| Initiating | Needs assessment, business case development, stakeholder identification |
| Planning | Requirements elicitation, analysis, documentation, RTM creation |
| Executing | Requirements clarification, change request analysis |
| Monitoring & Controlling | Requirements status tracking, scope validation support |
| Closing | Requirements completion verification, lessons learned |
Key Predictive BA Artifacts
| Artifact | Purpose |
|---|---|
| Business Requirements Document (BRD) | Captures high-level business needs and objectives |
| Functional Requirements Specification (FRS) | Details what the system must do |
| Non-Functional Requirements | Defines performance, security, and usability standards |
| Requirements Traceability Matrix | Links requirements to deliverables and tests |
| Use Case Specifications | Describes actor-system interactions in detail |
| Process Flow Diagrams | Visualizes business processes |
| Data Dictionary | Defines data elements and their attributes |
Predictive BA Characteristics
- Comprehensive documentation before development begins
- Formal sign-offs at phase gates
- Change control for any requirement modifications
- Dedicated BA role separate from the development team
- Sequential — requirements must be "complete" before design begins
Business Analysis in Agile Projects
In agile projects, business analysis is a continuous, iterative activity:
BA Activities by Event
| Scrum Event | BA Activities |
|---|---|
| Backlog Refinement | Write user stories, define acceptance criteria, estimate, prioritize |
| Sprint Planning | Clarify requirements for selected stories, answer team questions |
| Daily Scrum | Clarify requirements as questions arise during development |
| Sprint Review | Validate delivered functionality against acceptance criteria |
| Sprint Retrospective | Improve requirements processes |
Key Agile BA Artifacts
| Artifact | Purpose |
|---|---|
| Product Backlog | Prioritized list of all requirements (user stories, epics) |
| User Stories | Lightweight requirement descriptions from user perspective |
| Acceptance Criteria | Conditions that define when a story is complete |
| Story Maps | Visual layout of user journey and story priorities |
| Personas | Fictional user profiles representing target user groups |
| Wireframes/Prototypes | Visual representations of the solution |
Agile BA Characteristics
- Just-in-time requirements elaboration
- Collaborative — team refines requirements together
- Flexible — requirements can change based on feedback
- Embedded — BA is part of the team or role is absorbed by Product Owner
- Iterative — requirements are refined over multiple sprints
Comparing BA in Predictive vs. Agile
| Aspect | Predictive BA | Agile BA |
|---|---|---|
| Timing | Upfront, before development | Continuous, throughout project |
| Documentation | Comprehensive, formal | Lightweight, just enough |
| Requirements format | SRS, BRD, use cases | User stories, acceptance criteria |
| Change management | Formal change control | Welcome change, reprioritize backlog |
| Stakeholder involvement | At phase gates and reviews | Continuous collaboration |
| Traceability | Formal RTM | Product backlog hierarchy |
| BA Role | Dedicated business analyst | Product Owner or embedded BA |
| Sign-offs | Formal approval before next phase | Acceptance at Sprint Review |
| Risk of requirements | May be outdated by delivery | May lack formal documentation |
Business Analysis in Hybrid Projects
Hybrid projects combine elements of both approaches:
| Phase/Area | Approach |
|---|---|
| Business requirements | Predictive (formal BRD, needs assessment) |
| Solution requirements | Agile (user stories refined iteratively) |
| Compliance requirements | Predictive (formal documentation and traceability) |
| UI/UX requirements | Agile (prototyping and iterative design) |
| Architecture | Predictive (upfront architectural decisions) |
| Feature delivery | Agile (sprints with continuous feedback) |
Common Hybrid BA Patterns
- Requirements funnel: Formal business requirements flow into an agile backlog
- Two-speed BA: High-level planning follows predictive; delivery follows agile
- Compliance overlay: Agile delivery with predictive documentation for audits
- Phase-gated agile: Agile sprints within predictive project phases
Test Your Knowledge
In a predictive project, when does most business analysis work occur?
A
B
C
D
Test Your Knowledge
In an agile project, who typically performs business analysis activities?
A
B
C
D
Test Your Knowledge
In a hybrid project, which requirements are typically handled using a predictive approach?
A
B
C
D