Hello,
i've been following the evolution of both roles since 2007. The time frame is important because at that time most of the "projects" demand a clear understanding of the requisites that compose the scope before progressing to implementation. The professional would spend a considerable part of his workday managing the requisites and everything else, e.g. writing or compiling a request for proposal with the team, analyzing the proposals, selecting the vendor and then moving forward with the implementation.
Although i do agree PM and BA are different roles working on together is harder said than done. Nowadays i'm managing a project where the vendor has a PM working with the several BAs. The BA understands the requisite and pass it down to the development team.
The PMBOK and the PMI-PBA has many similarities with the BABOK.
In the end the issue for me is does it make sense to pay both certifications?
...
1 reply by Sergio Luis Conte
Aug 08, 2018 5:31 AM
Sergio Luis Conte
...
I have both. The reason is because in the time when I earned CBAP the PMI was not a player in the buisness analysis fileld yet. For a chance of the destiny I was part of the genesis of the role working with the IIBA and then with the PMI because I worked into an USA company that contributed with both organizationa in creating the role. I will say what i do when I started the process to decide and earning a new certification. I made my own estimation on future market demmands. It depends on the market you take and it is an estimation then a degree of uncertainty is there because the amount of information you can get. If you ask me, and just it is my personal opinion, I think that PMI will prevail. For example, in the last years, I was part of the group that created all related to business analysis (as I mentioned) and I was part of the group that integrate business analysis into all related standards. So, up to this time, PMI has taken the role seriously. Just to comment, all is made as voluntary and the amount of informaiton I have about decision taken at high level into the PMI is limited. But I think the role is taken seriously inside the PMI.
Saving Changes...
Robin GoldsmithPresident| Go Pro Management Inc.Needham, Ma, United States
We seem to be getting into “the operation was a success but the patient died.” No doubt some people think of the roles in very narrow ways, such as define a product vs. define and oversee completion of the project tasks needed to deliver the product. In my experience, though, both are judged by others based on whether the delivered product/system/software provides needed value.
Effective project managers know for their project to succeed, they and the project must have a valid and reliable understanding of the needed value and how to achieve it, so they can guide the project in fact to deliver it. Business analysis is the process for obtaining such understandings.
If there is no business analyst charged with performing such business analysis, or if the people/role(s) assigned to perform the business analysis don’t do it adequately (which unfortunately is very common, even with certified and/or experienced business analysts), the project and its manager still need adequate analysis to know what to deliver, to determine how to deliver it, and to make sure it not only is delivered as defined but also in fact provides needed value. Hitting budgets and schedules is necessary but not sufficient. “The analysis was poor” is not an acceptable excuse.
...
1 reply by Kik Piney
Aug 07, 2018 3:42 AM
Kik Piney
...
Robin, I agree that the project manager may need to act as "backstop" for the business analyst or product owner if they do not do their job correctly. However, that is (or should be) an exceptional situation. In a complex program, the relationship between program manager, business analyst and project manager needs to be one of effective teamwork based on mutual respect, open communication and clear delineation of roles.I think that this thread is aiming to provide a clear definition and delineation of these roles.
Saving Changes...
Kik PineyConsultant| PROjects-BeneFITSMougins, France
Aug 06, 2018 6:06 PM
Replying to Robin Goldsmith
...
We seem to be getting into “the operation was a success but the patient died.” No doubt some people think of the roles in very narrow ways, such as define a product vs. define and oversee completion of the project tasks needed to deliver the product. In my experience, though, both are judged by others based on whether the delivered product/system/software provides needed value.
Effective project managers know for their project to succeed, they and the project must have a valid and reliable understanding of the needed value and how to achieve it, so they can guide the project in fact to deliver it. Business analysis is the process for obtaining such understandings.
If there is no business analyst charged with performing such business analysis, or if the people/role(s) assigned to perform the business analysis don’t do it adequately (which unfortunately is very common, even with certified and/or experienced business analysts), the project and its manager still need adequate analysis to know what to deliver, to determine how to deliver it, and to make sure it not only is delivered as defined but also in fact provides needed value. Hitting budgets and schedules is necessary but not sufficient. “The analysis was poor” is not an acceptable excuse.
Robin, I agree that the project manager may need to act as "backstop" for the business analyst or product owner if they do not do their job correctly. However, that is (or should be) an exceptional situation. In a complex program, the relationship between program manager, business analyst and project manager needs to be one of effective teamwork based on mutual respect, open communication and clear delineation of roles.I think that this thread is aiming to provide a clear definition and delineation of these roles. Saving Changes...
Aleksei NikitinLead expert| Higher School of EconomicsSaint-Petersburg, Russian Federation
Wow! This thread has given me more understanding than dozen of books and webinars!
In my projects I usually considered business-analysts as specialsts in modeling "as to be" IDEF0 diagrams. And I didn't understand why they thought that I was wrong, that there work was something else.
Now I have much more clearence about their role.
I wanted to get the PMI-PBA, but it is hard to prove the 3-year BA experience, if you work as PM.
...
1 reply by Sergio Luis Conte
Aug 08, 2018 5:25 AM
Sergio Luis Conte
...
Bussines Analysit is the role that assure "your dreams comes true". That is key to understand. Business Analyst start working with dreams/wishes/desires/wants/needs "translating" them into requirements of the solution to be created as part of satisfying organizational objectives. Continue working with it along the solution creation and implementation (the project) keeping those dreams in focus and demostrating (with the help or project manager too) that hose dreams are reality. When all it is implemented Business Analyst monitoring if those dreams comes true becouse expected benefits have been achieved. And the key component of the role, mostly forgotten, is: thanks to monitoring just in case expected benefits are not achieved is the business analyst the role that helps the organization to react instead of continue wirh value loss.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Aug 07, 2018 7:13 AM
Replying to Aleksei Nikitin
...
Wow! This thread has given me more understanding than dozen of books and webinars!
In my projects I usually considered business-analysts as specialsts in modeling "as to be" IDEF0 diagrams. And I didn't understand why they thought that I was wrong, that there work was something else.
Now I have much more clearence about their role.
I wanted to get the PMI-PBA, but it is hard to prove the 3-year BA experience, if you work as PM.
Bussines Analysit is the role that assure "your dreams comes true". That is key to understand. Business Analyst start working with dreams/wishes/desires/wants/needs "translating" them into requirements of the solution to be created as part of satisfying organizational objectives. Continue working with it along the solution creation and implementation (the project) keeping those dreams in focus and demostrating (with the help or project manager too) that hose dreams are reality. When all it is implemented Business Analyst monitoring if those dreams comes true becouse expected benefits have been achieved. And the key component of the role, mostly forgotten, is: thanks to monitoring just in case expected benefits are not achieved is the business analyst the role that helps the organization to react instead of continue wirh value loss. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Aug 06, 2018 6:50 AM
Replying to Tiago Romao
...
Hello,
i've been following the evolution of both roles since 2007. The time frame is important because at that time most of the "projects" demand a clear understanding of the requisites that compose the scope before progressing to implementation. The professional would spend a considerable part of his workday managing the requisites and everything else, e.g. writing or compiling a request for proposal with the team, analyzing the proposals, selecting the vendor and then moving forward with the implementation.
Although i do agree PM and BA are different roles working on together is harder said than done. Nowadays i'm managing a project where the vendor has a PM working with the several BAs. The BA understands the requisite and pass it down to the development team.
The PMBOK and the PMI-PBA has many similarities with the BABOK.
In the end the issue for me is does it make sense to pay both certifications?
I have both. The reason is because in the time when I earned CBAP the PMI was not a player in the buisness analysis fileld yet. For a chance of the destiny I was part of the genesis of the role working with the IIBA and then with the PMI because I worked into an USA company that contributed with both organizationa in creating the role. I will say what i do when I started the process to decide and earning a new certification. I made my own estimation on future market demmands. It depends on the market you take and it is an estimation then a degree of uncertainty is there because the amount of information you can get. If you ask me, and just it is my personal opinion, I think that PMI will prevail. For example, in the last years, I was part of the group that created all related to business analysis (as I mentioned) and I was part of the group that integrate business analysis into all related standards. So, up to this time, PMI has taken the role seriously. Just to comment, all is made as voluntary and the amount of informaiton I have about decision taken at high level into the PMI is limited. But I think the role is taken seriously inside the PMI. Saving Changes...
Robin GoldsmithPresident| Go Pro Management Inc.Needham, Ma, United States
@Kik, apparently I didn’t explain adequately, for being a ‘backstop’ was not at all my main focus. Rather, I’m saying to do his/her job, the Project Manager must understand the business, its needed value, and the set of what I call REAL business requirements deliverable _whats_ that will achieve the value when satisfied by a product/system/software way _how_ to satisfy the business _whats_ that the project implements.
We call the process for gaining such understandings ‘business analysis.’ It may be carried out by someone called a ‘business analyst’ or by other roles including in many instances the project manager. Regardless, to be effective, a project manager must understand business analysis sufficiently to assure it is performed, and more importantly performed adequately, to thereby provide the basis for a project which successfully provides needed value.
IMHO, neither BABOK nor PMBOK recognize or deal adequately with this essential aspect of projects; and unfortunately too narrowly following either could actually lead projects astray.
...
1 reply by Kik Piney
Aug 12, 2018 3:51 AM
Kik Piney
...
Robin,
I do agree that he project manager needs to understand the justification for the project. However, the skills for detailed business analysis, as well as the criteria for success, are different for the project manager and business analyst. To take a simple analogy, consider rally driving, in which you have a driver and a navigator. The driver (think PM) certainly needs to know where they are going and get there safely and as fast as possible; the navigator (think BA) is an expert at defining and describing each detail of the course and advising the driver on forthcoming challenges.
In a simple environment, a driver does not need a navigator, but when the going gets tough, each participant has a specific, specialized role to play. The roles should be complementary and each actor needs to accept the limits of their skills and knowledge. You may enjoy the following dysfunctional team (but beware of the foul language): https://www.youtube.com/watch?v=VOKnkFxT48U
Saving Changes...
Kik PineyConsultant| PROjects-BeneFITSMougins, France
Aug 10, 2018 5:47 PM
Replying to Robin Goldsmith
...
@Kik, apparently I didn’t explain adequately, for being a ‘backstop’ was not at all my main focus. Rather, I’m saying to do his/her job, the Project Manager must understand the business, its needed value, and the set of what I call REAL business requirements deliverable _whats_ that will achieve the value when satisfied by a product/system/software way _how_ to satisfy the business _whats_ that the project implements.
We call the process for gaining such understandings ‘business analysis.’ It may be carried out by someone called a ‘business analyst’ or by other roles including in many instances the project manager. Regardless, to be effective, a project manager must understand business analysis sufficiently to assure it is performed, and more importantly performed adequately, to thereby provide the basis for a project which successfully provides needed value.
IMHO, neither BABOK nor PMBOK recognize or deal adequately with this essential aspect of projects; and unfortunately too narrowly following either could actually lead projects astray.
Robin,
I do agree that he project manager needs to understand the justification for the project. However, the skills for detailed business analysis, as well as the criteria for success, are different for the project manager and business analyst. To take a simple analogy, consider rally driving, in which you have a driver and a navigator. The driver (think PM) certainly needs to know where they are going and get there safely and as fast as possible; the navigator (think BA) is an expert at defining and describing each detail of the course and advising the driver on forthcoming challenges.
In a simple environment, a driver does not need a navigator, but when the going gets tough, each participant has a specific, specialized role to play. The roles should be complementary and each actor needs to accept the limits of their skills and knowledge. You may enjoy the following dysfunctional team (but beware of the foul language): https://www.youtube.com/watch?v=VOKnkFxT48U Saving Changes...
Robin GoldsmithPresident| Go Pro Management Inc.Needham, Ma, United States
@Kik, I think we are largely agreeing violently. I’m not saying the PM necessarily has to have the skills to do detailed business analysis; but s/he has to know it must be done and be able to tell reasonably whether it’s been done adequately, and if not, why not and what needs to be done differently. Again, it’s also important to realize that often the PM is the one expected to do business analysis or ends up having to do it because there is no other project member with suitable skills. Pointing fingers and cursing the darkness that adequate analysis hasn’t been done do not get needed value and are pointless Project Manager behavior.
BTW, I think your video has a driver who needs to know how to avoid obstacles while following the road and a back-seat driver (not a navigator) who is just creating havoc and greater chances of a crash. I agree there is a risk of a Project Manager with business analysis skills second-guessing and micromanaging a Business Analyst on the project. It can go the other direction, because effective business analysts also have to understand project management and take an active role in managing the business analysis. Saving Changes...
Michael DelaneyPartner| Delaney Management LLCWest Chester, Pa, United States
Thanks for the question good information Saving Changes...