WHY THIS MATTERS TO YOU

When there is both a PM and a BA on a project, the relationship between them is one of the most important dynamics on the engagement. Done well, it is a force multiplier: the PM manages the container, the BA fills it with quality content. Done poorly, it is a source of confusion, duplication, and gaps.
This module covers how to build an effective PM-BA partnership, how to divide work without creating gaps, and how to manage the friction that sometimes develops between the two roles.

The PM-BA Division of Labor

The cleanest way to think about the distinction: the PM manages the project; the BA manages the requirements. The PM owns the schedule, the budget, the risk register, and the communication plan. The BA owns the requirements documentation, the process flows, the acceptance criteria, and the traceability between requirements and deliverables.

In practice, there is overlap and the lines blur. Both the PM and BA manage stakeholder relationships. Both flag risks. Both communicate status. The key is to be explicit about who owns what so nothing falls through the gap between the roles.

Activity	Typically PM-Led	Typically BA-Led
Project schedule management	Yes	Informs but does not own
Requirements documentation	No	Yes
Risk register management	Yes (owns)	Contributes risks
Stakeholder workshops	May facilitate or observe	Usually leads
Status reporting	Yes	May contribute BA workstream status
Change control	Yes (process)	Evaluates requirements impact
Acceptance criteria	No	Yes
Issue log	Owns overall log	Contributes and resolves BA-domain issues

When There Is No PM

On many consulting engagements, especially smaller ones, there is no dedicated PM. The BA is expected to manage the project as well as the requirements. This is common and manageable if you recognize it upfront and apply at least a minimum viable PM structure: a charter or scope document, a basic schedule with milestones, a risk log, a change log, and a communication plan.

The failure mode is assuming someone else is handling the PM responsibilities without confirming it. When a project has no PM and the BA does not step into that gap, critical project management activities simply do not happen.

PMP / PMBOK NOTE

PMI defines the BA role in its Business Analysis Practice Guide, which explicitly addresses the BA’s responsibilities on projects with and without a dedicated PM. The PMP exam may present scenarios where a BA or functional manager is performing project management work and ask what activities are required.

Navigating PM-BA Tension

Tension between PMs and BAs usually comes from one of three sources: role ambiguity (both think the other person owns something), quality vs. speed conflict (the BA wants requirements to be more thorough; the PM wants to hit the milestone), or authority questions (can the BA approve a requirement without the PM?).

• Role ambiguity: resolve with an explicit RACI; have the conversation early, not when the conflict arises
• Quality vs. speed: agree on minimum viable completeness for each phase; document the trade-off if something ships incomplete
• Authority: the BA has content authority (is this requirement correct?); the PM has process authority (did this go through change control?)

 

WHAT THEY SAY	WHAT THEY MEAN
The PM keeps asking me for status updates I already gave them	The PM may need status in a different format or at a different cadence; align on a single communication mechanism
The BA keeps adding detail that slows us down	The detail is there to prevent rework; have a conversation about minimum viable requirements for the current phase
I thought the PM was handling the stakeholder communication	Clarify who owns which stakeholder relationships; both roles have communication responsibilities
The PM approved a scope change without consulting me on the requirements impact	The BA must be part of impact assessment; establish this expectation with the PM at project start

COMMON MISTAKE

MISTAKE: Assuming the PM is handling project governance when you are the only one actually doing it.
What it looks like: A project has a named PM who is managing three other engagements simultaneously. The PM is present for steering committee meetings but is not doing day-to-day project management. The BA fills the gap by default but does not have the title, authority, or compensation for the PM role. Issues escalate without a clear owner.
Reality: If you are performing PM functions, that should be explicitly recognized and resourced. If the PM is not fulfilling their role, that should be escalated through the appropriate channel.

QUESTIONS TO ASK YOUR STAKEHOLDER

Is there a clear division of responsibilities between the PM and BA on this project?
Are there any activities where both the PM and BA think the other person owns it?

If there is no dedicated PM, has the BA formally taken on PM responsibilities with appropriate authority?
Are there any current PM-BA tensions that are affecting project quality or team dynamics?
Does the PM include the BA in change impact assessments before approving change requests?

 

Module Quiz

1. On a project with both a PM and a BA, who typically owns the requirements documentation?
2. The PM
3. The BA
4. Both equally
5. The sponsor

Answer: B

Why it matters: Requirements documentation is the BA’s core deliverable. The PM manages the process around it (milestones, change control) but does not own the content.

2. A BA discovers they are performing project management activities because the PM is overcommitted. What is the most professional response?
3. Continue quietly and list it on the resume
4. Formally acknowledge the gap, document what PM activities are being performed, and escalate to have it resourced appropriately
5. Stop doing the PM activities so the gap becomes visible
6. Ask the client if they want to replace the PM

Answer: B

Why it matters: Performing unacknowledged PM work creates risk and unfair burden. The professional response is to surface it, document it, and seek appropriate resourcing.

3. A PM approves a scope change without consulting the BA on requirements impact. What principle is being violated?
4. The BA should be involved in change impact assessment because requirements are their domain
5. The PM has no authority to approve scope changes
6. The BA should have been the one to approve it
7. No principle is violated; the PM can approve anything

Answer: A

Why it matters: The BA owns requirements content. A scope change has requirements implications that only the BA can properly assess. Excluding them from the impact assessment risks accepting a change with hidden requirements consequences.

4. Quality vs. speed tension between a PM and BA is best resolved by:
5. Always prioritizing the PM’s schedule over BA’s requirements quality
6. Always prioritizing BA’s thoroughness over schedule
7. Agreeing on minimum viable completeness for each phase and documenting any trade-offs explicitly
8. Having the sponsor decide

Answer: C

Why it matters: Neither quality nor speed is always the right answer. The professional resolution is a documented agreement about what level of completeness is acceptable for each phase, with trade-offs acknowledged.

5. What is the cleanest way to prevent role ambiguity between a PM and BA?
6. Have the PM manage all activities
7. Create an explicit RACI covering all key project activities at project start
8. Have the BA defer to the PM on all decisions
9. Avoid overlapping responsibilities entirely

Answer: B

Why it matters: A RACI assigns Accountable ownership to each activity. When both the PM and BA know who owns what, ambiguity conflicts are prevented before they occur.