I'm going through the PMI training videos for a CAPM. In one of them, the presenter states:

If a business analyst is assigned to a project, that individual is responsible for defining requirements activities, taking over your role as project manager. You may collaborate with business analysts to obtain, document, and manage stakeholder requirements to meet business and project objectives.

My take-away from this is as follows:

  1. If a business analyst is assigned to the project, that individual is responsible for all requirements-gathering and definition work, including the development of the traceability matrix.
  2. If a business anlyist is not assigned to the project, all responsibility for gathering and documenting requirements falls on the project manager.

Is this correct? Or am I misunderstanding something fundamental here?

Also, if a business analyst is assigned to a project, what is the role of the project manager in reviewing and recommending corrections or changes to the requirements (in the event that the PM or team discover that they are incomplete, out of scope, or inaccurate)?

  • 2
    Who made the training video? There are so many things wrong with that statement. Aug 12, 2018 at 18:18
  • Actually, it's on the curricula for CAMP at pmi.org. If you can correct the statement, I'd really appreciate it. I wouldn't be surprised if it's in error; I've already spotted a few issues with the course and I'm cataloging them.
    – Mike Hofer
    Aug 13, 2018 at 15:42

3 Answers 3


The accountability resides always with the project manager, the responsibility can be delegated.

If you look at page 25 of PMBOK v 6, table 1.4 Process 5.2 Collect Requirements is specified as a PM accountability.


The issue with this statement is that it is making a determination of PM responsibility and accountability based on roles that are or are not present. The presence of a BA role--or more precisely the presence of another individual with a BA title--is immaterial in determining whether or not the PM has any degree of responsibility or accountability in the development of business requirements. What matter is what is in scope for this project as should be indicated in the project charter, scope statement and description, and work breakdown structure. If requirements development is within scope, then the PM has responsibility / accountability for its development to specs. If there is another human on the project with the title BA, then that person has responsibility for its development, too, but the PM retains his/her degree of responsibility and overall accountability for this product as the BA would report--either matrixed or directly--to this PM.

The only caveat to the above is if the contract--assuming a seller and buyer arrangement--explicitly carves out this particular product from the PM's scope of work. Thus, the product is still in scope for the project but excluded via contract for the PM. In this case, the PM has a dependency for its development, and corresponding risks. Therefore, while not directly responsible for it, (s)he has skin in the game.

TL;DR: The presence of a BA is immaterial in the determination of PM responsibility and accountability.

Having done a bit more research here, I see what PMI has done. They have a newish (I have no idea when this certificate was created) BA certificate and, apparently, a BABoK. So in PMI parlance, there is a distinct swim lane between the BA and the PM. So in the business case flow chart, it appears that the problem identification leads to the requirements product which leads to the project charter and then to the PM. So, if you're studying for the CAPM or PMP, you need to learn it the way PMI has set it up. However, this is one of those areas that, in the real world, you'll experience something quite different in many cases. It's not that PMI is wrong here, it's that it is overly simplified. In many cases, the project charter can include the development of the business case and then the requirements. So just be aware of that as you progress in your career.

  • This is a great answer. The bit about "problem identification leads to the requirements product which leads to the project charter" is perplexing, though. How can you define requirements when it is the charter that defines what's in scope and what's out of scope?
    – Mike Hofer
    Aug 28, 2018 at 12:57

It is a PM's responsibility to overlook and own a particular project.

As per my understanding BA function is a subset of PM function.

Hope this helps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.