Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
As business analyzes is an important stage for project success!! I want to know the roles and responsibility of business analyst during project life cycle? what is critical stage for him? Which stage should be focus on? Is there any intersection between him and PM during on project life cycle? Saving Changes...
A business analyst has many roles and responsibilities:-
However he/she is responsible for discovering the actual needs of stakeholders and for organization's benefits.In Agile he/she called a " product owner".
There is an intersection between Business analyst and PM both of them pushing the project describable and goals to be aligned with the business strategy and origination's benefits.
BR,
Mansour
...
1 reply by Tamer Zeyad Sadiq
Dec 02, 2018 12:27 AM
Tamer Zeyad Sadiq
...
Thanks Mansour!!!
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Business Analyst is accountable for solution requirements, acceptance and benefit monitoring (where assumptions and restrictions must be consider requirements too) while project manager is acountable for project (work needed) requirements. Project requirements are defined and managed from solution requitements. With that on hand, you will understand that the business analyst work starts before the project exists, continue while the project runs, do not end when the project ends. My recommendation is taking a look to Business Analysis for Practitioners Guide because in my personal opinion is a good reference about the interaction of both roles and could help to answer your question.
...
1 reply by Tamer Zeyad Sadiq
Nov 23, 2018 2:15 PM
Tamer Zeyad Sadiq
...
Thanks for your respond Sergio
Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
Nov 23, 2018 10:23 AM
Replying to Sergio Luis Conte
...
Business Analyst is accountable for solution requirements, acceptance and benefit monitoring (where assumptions and restrictions must be consider requirements too) while project manager is acountable for project (work needed) requirements. Project requirements are defined and managed from solution requitements. With that on hand, you will understand that the business analyst work starts before the project exists, continue while the project runs, do not end when the project ends. My recommendation is taking a look to Business Analysis for Practitioners Guide because in my personal opinion is a good reference about the interaction of both roles and could help to answer your question.
The BA manages business requirements, like the PM manages project requirements and the Systems Engineer manages product requirements.
The BA is involved earlier than the other two, but most of the cost of any project is established very early in the project lifecycle, thus the BA becomes less involved as the project develops. Saving Changes...
Moushumi JaniDar Es Salaam, Ilala, Tanzania, United Republic Of
I would assume that the business analyst's input is very critical during the scope definition stage.
In some cases, a BA would likely be involved even before a project is initiated, as he would be coming up with the business needs that may evolve into a project.
The interaction between the two (PM and BA) is likely to be intense at the beginning of the project and then at deliverable stages. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Partner with business and enterprise groups to ensure alignment to technical and organizational strategies. Each 'stage' has its own vital components to ensure the product solves the needs of the business. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
All good responses. The theoretical and practical answer to the question would be quite different though. Since most of the responses give the theoretical view I'll give the practical view - In a vendor environment I found that the BA is rarely involved before project initiation . The BA will also be used to overlap with the PM, more than it should. The primary focus of the BA is on creating documentation during the project life cycle. (There are many reasons but a different discussion) As you can see WHAT the BA does and WHAT the BA SHOULD be doing can be very different.
...
1 reply by Sergio Luis Conte
Nov 26, 2018 4:27 AM
Sergio Luis Conte
...
Sorry Anton, but it is a wrong line of thinking. I was part of the "genesis" of business analysis when I worked in one of the six companies that created the role. That was time before the PMI took the role and it was when the IIBA was created. All those companies are IT/Software services and products sellers. The role was created by vendors. Pre-sales people are the business analyst inside vendors. Because the genesis in the very begining the business analyst role was considered IT/Software related only. In fact, the definition statement said that. But it was changed time after.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Nov 25, 2018 11:57 PM
Replying to Anton Oosthuizen
...
All good responses. The theoretical and practical answer to the question would be quite different though. Since most of the responses give the theoretical view I'll give the practical view - In a vendor environment I found that the BA is rarely involved before project initiation . The BA will also be used to overlap with the PM, more than it should. The primary focus of the BA is on creating documentation during the project life cycle. (There are many reasons but a different discussion) As you can see WHAT the BA does and WHAT the BA SHOULD be doing can be very different.
Sorry Anton, but it is a wrong line of thinking. I was part of the "genesis" of business analysis when I worked in one of the six companies that created the role. That was time before the PMI took the role and it was when the IIBA was created. All those companies are IT/Software services and products sellers. The role was created by vendors. Pre-sales people are the business analyst inside vendors. Because the genesis in the very begining the business analyst role was considered IT/Software related only. In fact, the definition statement said that. But it was changed time after. Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
Nov 23, 2018 7:41 AM
Replying to MANSOUR THABET ALQUBATY
...
A business analyst has many roles and responsibilities:-
However he/she is responsible for discovering the actual needs of stakeholders and for organization's benefits.In Agile he/she called a " product owner".
There is an intersection between Business analyst and PM both of them pushing the project describable and goals to be aligned with the business strategy and origination's benefits.