Ola AbimbolaProject Manager| Trimble Oil and GasCalgary, Alberta, Canada
I notice from most of the project that I have engaged in that I end up collecting the project requirements and also managing the process of the same with SMEs. In real practice, I have also had to use PMIS to collect, analyze and present data.
So while I have acquired training in business analysis, I sometimes struggle to see its use in real practice (at least on some of the projects I have worked on) Saving Changes...
It dependents on the company size, structure and business model. I have been worked with both approached PM = PM+BA and PM=PM + BA=BA. The main goal of BA in the second approach is to answer why-what-how? PM's questions are when-how much-who etc. Yes, it may be a bit expensive to have these two roles in one project. However, it will save you lots of money for rework because of irrelevant business need identification.
...
1 reply by Ola Abimbola
Dec 13, 2019 9:37 AM
Ola Abimbola
...
Apt... Thanks
Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I would say no, but would also caveat with a 'depends'. We could flip the question, right, and ask if BA's double as a PM. To be quite frank, I'd say that the latter rings truer. I have had my share of experiences leading projects while my role was BA. Additionally, once I moved to the PM role from BA, I certainly utilized my experiences but did not actually fulfill the BA role while acting as the PM.
The value of the BA role stands on its own and is of significant value in many organizations.
...
1 reply by Ola Abimbola
Dec 13, 2019 9:40 AM
Ola Abimbola
...
Hmmm this is very tricky... If it is a very big project requiring heavy PM inputs a BA is most likely going to stumble on applying PM methodologies and principles to manage large projects without prior PM experience. On small scale projects especially in functional organizations such swap in roles is easier
I suppose it would depend on the size of the project team and resources available to it. In environments with limited resources and time, hiring a Business Analyst for a short period of time for a specific task maybe outside the budget requirement of the project team. As a result in such situation project managers take on many other responsibilities outside the scope of their job description in order to get the job done. However its best practise that the Business Analyst responsibility has a separate and independent function to that of the project team. The reason for this is that a Business Analysts findings are normally representative of the reasons whether a Client or project sponsor makes the decision to progress with a specific project and the level of budget, time and resources assigned to that project. Saving Changes...
Ola AbimbolaProject Manager| Trimble Oil and GasCalgary, Alberta, Canada
Dec 13, 2019 5:24 AM
Replying to Sergiy Zhuravel
...
It dependents on the company size, structure and business model. I have been worked with both approached PM = PM+BA and PM=PM + BA=BA. The main goal of BA in the second approach is to answer why-what-how? PM's questions are when-how much-who etc. Yes, it may be a bit expensive to have these two roles in one project. However, it will save you lots of money for rework because of irrelevant business need identification.
Apt... Thanks Saving Changes...
Ola AbimbolaProject Manager| Trimble Oil and GasCalgary, Alberta, Canada
Dec 13, 2019 7:16 AM
Replying to Drew Craig
...
I would say no, but would also caveat with a 'depends'. We could flip the question, right, and ask if BA's double as a PM. To be quite frank, I'd say that the latter rings truer. I have had my share of experiences leading projects while my role was BA. Additionally, once I moved to the PM role from BA, I certainly utilized my experiences but did not actually fulfill the BA role while acting as the PM.
The value of the BA role stands on its own and is of significant value in many organizations.
Hmmm this is very tricky... If it is a very big project requiring heavy PM inputs a BA is most likely going to stumble on applying PM methodologies and principles to manage large projects without prior PM experience. On small scale projects especially in functional organizations such swap in roles is easier Saving Changes...