SkarpChapter 19 of 20
Integrating Business Analysis with Project Approaches and Domains
See how business analysis practices weave through all domains—fundamentals, predictive, and agile—rather than sitting in a silo. You’ll practice recognizing BA tasks no matter what the life cycle or role title looks like in the exam scenario.
Big Picture: Where Business Analysis Fits in CAPM Domains
BA Across CAPM Domains
In the current CAPM model, business analysis is woven through all domains. Many questions describe project scenarios where no one is called "business analyst", but BA work is clearly happening.
Domains and Life Cycles
You will see BA in fundamentals/business environment, predictive approaches, and adaptive (agile, hybrid) approaches. Each treats requirements and value a bit differently.
Roles vs Responsibilities
On the exam, BA tasks may be done by a project manager, product owner, scrum master, or team member. Focus on the responsibility, not just the job title.
What This Module Covers
We will clarify who does BA work, compare BA in predictive vs adaptive, map BA and PM artifacts, practice spotting BA tasks in scenarios, and link BA to value delivery.
Who Does Business Analysis? Roles and Responsibilities
BA as Responsibilities
Business analysis is a set of responsibilities: eliciting, analyzing, prioritizing requirements, defining acceptance criteria, and validating that the solution meets needs.
Business Analyst Role
A BA often owns daily requirements work in predictive or hybrid projects, maintains the requirements traceability matrix, and facilitates workshops and process analysis.
Product Owner Role
In agile, the product owner manages the product backlog, clarifies value and priority, defines acceptance criteria, and performs continuous BA tasks during iterations.
Project Manager and Others
The project manager links requirements to scope, schedule, and budget, sometimes doing BA work directly. SMEs, developers, and testers also help discover and validate requirements.
Predictive vs Adaptive: When and How BA Happens
Two Life Cycles, Two BA Styles
Predictive life cycle fixes scope, time, and cost early. Adaptive life cycle defines detailed scope just before each iteration. This shapes when and how BA work happens.
BA in Predictive
In predictive projects, BA is front‑loaded with formal documents like detailed specs and RTMs. Change is tightly controlled through formal change requests.
BA in Adaptive
In adaptive projects, BA is continuous. Requirements live in the product backlog as user stories and features, with acceptance criteria that evolve as the team learns.
Common Exam Trap
Agile does not mean "no documentation." It means just enough documentation, created and refined when it is most useful to support value delivery.
Side‑by‑Side Scenario: Same Need, Different Approaches
The Common Need
Need: reduce average customer support call time by 20% in 6 months while keeping satisfaction scores stable. BA supports this in both predictive and adaptive projects.
Predictive Handling
In predictive, the BA runs workshops, documents detailed requirements, builds a requirements traceability matrix, and the PM creates a WBS and work packages from those requirements.
Adaptive Handling
In adaptive, a product owner builds a product backlog of user stories, the team delivers increments each iteration, and acceptance criteria define "done" for each story.
Same BA Core, Different Timing
Both approaches rely on eliciting, refining, and validating requirements. The main difference is when details are decided and how easily change is absorbed.
Connecting BA Artifacts to PM Artifacts: RTM, Backlog, WBS, Schedule
Key BA Artifacts
BA uses a requirements traceability matrix to link requirements to deliverables, and in agile the product owner manages the product backlog of needed product items.
Key PM Artifacts
The work breakdown structure decomposes total scope, and work packages at its lowest level are where cost and duration are estimated and managed.
Predictive Integration
In predictive, approved requirements feed the RTM, which links to WBS deliverables and work packages. The schedule then reflects when those requirement-driven deliverables are built.
Adaptive Integration
In adaptive, epics and stories in the product backlog drive a lightweight WBS or roadmap. Sprint backlog items map to tasks on a short-term schedule or board with simple traceability.
Thought Exercise: Mapping Requirements to WBS and Backlog
Work through this mentally (or jot notes) to practice mapping BA artifacts to PM artifacts.
Scenario
You are on a project to launch a new mobile app for a bank. A key requirement states:
"Customers must be able to view their last 12 months of transactions and filter by date, amount, and transaction type."
Task 1: Predictive view
- List 3 possible WBS elements (deliverables or work packages) that would trace back to this requirement.
- For each WBS element, note what sort of acceptance criteria would prove it is done.
- Explain how this requirement and its WBS elements would appear in a requirements traceability matrix.
Task 2: Adaptive view
- Rewrite the requirement as a user story suitable for a product backlog.
- Add at least 3 acceptance criteria for that story.
- Describe how this story would flow from product backlog to iteration backlog to "done" on the team board.
Reflect
- How did the formality change between predictive and adaptive views?
- What stayed the same about the underlying BA work?
Pause and actually outline your answers. This mirrors the kind of reasoning CAPM questions expect when they ask how to align requirements with scope and delivery.
Stakeholder Collaboration in BA Activities
Stakeholders and BA
A stakeholder is anyone who may affect or be affected by the project. BA work relies on close collaboration with these people to define and validate requirements.
Elicitation
Elicitation uses interviews, workshops, and other techniques. In predictive it is front‑loaded; in adaptive it is continuous through refinement, reviews, and demos.
Analysis and Prioritization
Stakeholders help analyze and prioritize requirements. Predictive does this before baselining; adaptive reprioritizes the product backlog frequently.
Validation and Evaluation
Predictive often uses UAT near the end; adaptive uses frequent demos. Strong exam answers show the right stakeholders engaged throughout, not just at sign‑off.
End-to-End View: From Need to Value Realization
From Why to What to Value
BA connects why we do a project, what we build, and whether it delivered value. It runs from initial need through requirements to validation and benefits tracking.
Need and Requirements
First, analyze the problem or opportunity, then translate it into requirements and acceptance criteria. Predictive does this in detail upfront; adaptive refines over time.
Delivery and Traceability
Use RTMs or backlog links so each requirement is implemented through WBS elements, work packages, or backlog items that clearly support business goals.
Validation and Value
Validate that outputs meet acceptance criteria, measure outcomes, adjust the solution, and capture lessons learned about requirements and approach choice.
Quiz 1: Spot the BA Task Across Approaches
Apply what you have learned about BA responsibilities and life cycles.
A project team using an adaptive life cycle is planning its next iteration. The product owner works with stakeholders to clarify the highest-priority user stories and define conditions that must be met before the stories can be accepted. From a CAPM perspective, what is the BEST description of what is happening?
- Scope validation is occurring, because the team is formally accepting completed deliverables.
- Business analysis activities are occurring, because the team is eliciting and refining requirements and acceptance criteria.
- Schedule control is occurring, because the team is adjusting work to fit within the iteration timebox.
- Risk management is occurring, because the team is identifying and analyzing iteration risks.
Show Answer
Answer: B) Business analysis activities are occurring, because the team is eliciting and refining requirements and acceptance criteria.
The scenario is about clarifying user stories and defining acceptance criteria before work starts. That is classic business analysis: eliciting and refining requirements and acceptance conditions. Scope validation would occur after work is done. Schedule control and risk management may also happen, but they are not the focus of the described activity.
Quiz 2: Linking Requirements to WBS and Schedule
Test your understanding of how BA artifacts connect to PM artifacts.
On a predictive project, the project manager wants to ensure that every requirement is implemented by some part of the work breakdown structure and that no extra work is added that does not support requirements. Which combination of tools or artifacts BEST supports this goal?
- Product backlog and sprint backlog
- Requirements traceability matrix and work breakdown structure
- Issue log and change log
- Risk register and schedule variance reports
Show Answer
Answer: B) Requirements traceability matrix and work breakdown structure
The requirements traceability matrix links requirements to deliverables, and the work breakdown structure shows the hierarchical decomposition of scope. Used together, they help ensure that each requirement is covered and that work aligns to documented requirements. Product backlogs are more common in adaptive approaches. Issue logs, change logs, risk registers, and schedule variance reports serve different purposes.
Key Terms Review: BA and Project Approaches
Use these flashcards to reinforce core definitions and relationships that are frequently tested on CAPM.
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- schedule variance
- A measure of schedule performance expressed as the difference between earned value and planned value.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- schedule variance
- A measure of schedule performance expressed as the difference between earned value and planned value.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.