Project Management

Please login or join to subscribe to this thread

Who does product and project requirements and why?

linkedin twitter facebook   Business Analysis  
avatar
Bismarck Ansong Business Consultant| Ansong and Ansong Consulting Group Mississauga, Ontario, Canada
Hello folks! I hope all is well with everyone! My question is As Project managers who will you put in charge to do the product and project requirements?
Sort By:
< 1 2 3 4 >
avatar
Bismarck Ansong Business Consultant| Ansong and Ansong Consulting Group Mississauga, Ontario, Canada
Hmm! The question is which people are responsible for both requirements?
...
1 reply by Sergio Luis Conte
Apr 12, 2017 5:52 AM
Sergio Luis Conte
...
Take a look to this post: https://www.projectmanagement.com/blog-pos...olio-Management
You have to talk about accountability because the responsible is "the Doer" using the RACI jargon. Project manager focus is work needed to create the solution. Business Analyst focus is the solution. The relation between both roles are because most of the organizations define SOLUTION = "the thing" (product/service/result) to be created PLUS "the work needed" to create it (project). Remember that "product" is using as "something to be produced".
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Apr 11, 2017 9:48 PM
Replying to Bismarck Ansong
...
Hmm! The question is which people are responsible for both requirements?
Take a look to this post: https://www.projectmanagement.com/blog-pos...olio-Management
You have to talk about accountability because the responsible is "the Doer" using the RACI jargon. Project manager focus is work needed to create the solution. Business Analyst focus is the solution. The relation between both roles are because most of the organizations define SOLUTION = "the thing" (product/service/result) to be created PLUS "the work needed" to create it (project). Remember that "product" is using as "something to be produced".
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
The BA would work with the customer to elicit the requirements and gain a clear understanding of the problem to be solved, and the target solution.

The BA is then responsible for the product, and the PM is responsible for the project. The two roles work as a partnership for the success of the overall project.
...
1 reply by Bismarck Ansong
Apr 12, 2017 7:21 AM
Bismarck Ansong
...
Great!
avatar
Bismarck Ansong Business Consultant| Ansong and Ansong Consulting Group Mississauga, Ontario, Canada
Apr 12, 2017 6:41 AM
Replying to Drew Craig
...
The BA would work with the customer to elicit the requirements and gain a clear understanding of the problem to be solved, and the target solution.

The BA is then responsible for the product, and the PM is responsible for the project. The two roles work as a partnership for the success of the overall project.
Great!
avatar
John Tieso Author, Lecturer in Business Management| The Catholic University of America, Busch School of Business & Economics Arlington, Va, United States
Agreed that the BA owns the requirements. In some small efforts, it may be the project sponsor. Either way, the need for coordination and collaboration is critical translating those requirements by the team into products that meet the specs.
...
1 reply by Sergio Luis Conte
Apr 12, 2017 10:13 AM
Sergio Luis Conte
...
Please let me say that BA does not own the requirements. Here is the critical component to understand. Project requirements owner is the Project Manager. Solution requirements (mainly product/service/result requirements) owner is the Business Analyst. BA must give to the project manager all needed to define, plan, control, close the project. The project manager will define assumptions and restrictions from the information the business analyst provide too.
avatar
Bismarck Ansong Business Consultant| Ansong and Ansong Consulting Group Mississauga, Ontario, Canada
Great!
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Apr 12, 2017 7:56 AM
Replying to John Tieso
...
Agreed that the BA owns the requirements. In some small efforts, it may be the project sponsor. Either way, the need for coordination and collaboration is critical translating those requirements by the team into products that meet the specs.
Please let me say that BA does not own the requirements. Here is the critical component to understand. Project requirements owner is the Project Manager. Solution requirements (mainly product/service/result requirements) owner is the Business Analyst. BA must give to the project manager all needed to define, plan, control, close the project. The project manager will define assumptions and restrictions from the information the business analyst provide too.
...
1 reply by John Tieso
Apr 12, 2017 10:52 AM
John Tieso
...
Let's be practical here. A PM is selected to manage an identified project. Failing to do at least an initial business analysis to determine if any requirement exists is not logical. That would say the PM creates his/her own requirement, forms a team, then solves their own defined requirements.

In the practical world, that is not how requirements are generated, through analysis of a need for change, followed by a decision well above any PMs level to pursue that change, and the PM inherits the initial BA for use in further fleshing out their approach to solving the requirements. That may include additional analysis by the BA assigned to the team.
avatar
Bismarck Ansong Business Consultant| Ansong and Ansong Consulting Group Mississauga, Ontario, Canada
Wow! Many assumptions on these two requirements. The topic doesn't seem to be an easy and straightforward question that i thought it was. However, let's continue and wait for other folks on this platform comments.
...
2 replies by Naomi Caietti and Sergio Luis Conte
Apr 12, 2017 10:47 AM
Naomi Caietti
...
Bismarck:
Actually, it's really in the hands of your C-Suite until a core team is assigned but many here all agree on the normal standard practices.
Can you clarify the following:
Are you the client/customer or the system integrator/vendor? Is your question about the client or the vendor?
What do mean by put in charge and what phase of the project are your referring to?
Are you developing the business case, feasibility study or concept paper?
Are you developing the project charter with the sponsor?
Are you in the process of developing the RFP, RFQ or RFI and put it out to bid?
Thanks.
Apr 14, 2017 2:59 PM
Sergio Luis Conte
...
Its not a matter of assumptions. There are standards and roles definitions outside there and I am working helping organizations to implement both roles fron 1990 up to date. So, all you need is outside there. Including lot of implementations inside lot of organizations.
avatar
Naomi Caietti Senior Project Manager | ePMO | Higher Education | Healthcare & IT| Linkedin.com/In/NaomiCaietti
Apr 12, 2017 10:22 AM
Replying to Bismarck Ansong
...
Wow! Many assumptions on these two requirements. The topic doesn't seem to be an easy and straightforward question that i thought it was. However, let's continue and wait for other folks on this platform comments.
Bismarck:
Actually, it's really in the hands of your C-Suite until a core team is assigned but many here all agree on the normal standard practices.
Can you clarify the following:
Are you the client/customer or the system integrator/vendor? Is your question about the client or the vendor?
What do mean by put in charge and what phase of the project are your referring to?
Are you developing the business case, feasibility study or concept paper?
Are you developing the project charter with the sponsor?
Are you in the process of developing the RFP, RFQ or RFI and put it out to bid?
Thanks.
avatar
John Tieso Author, Lecturer in Business Management| The Catholic University of America, Busch School of Business & Economics Arlington, Va, United States
Apr 12, 2017 10:13 AM
Replying to Sergio Luis Conte
...
Please let me say that BA does not own the requirements. Here is the critical component to understand. Project requirements owner is the Project Manager. Solution requirements (mainly product/service/result requirements) owner is the Business Analyst. BA must give to the project manager all needed to define, plan, control, close the project. The project manager will define assumptions and restrictions from the information the business analyst provide too.
Let's be practical here. A PM is selected to manage an identified project. Failing to do at least an initial business analysis to determine if any requirement exists is not logical. That would say the PM creates his/her own requirement, forms a team, then solves their own defined requirements.

In the practical world, that is not how requirements are generated, through analysis of a need for change, followed by a decision well above any PMs level to pursue that change, and the PM inherits the initial BA for use in further fleshing out their approach to solving the requirements. That may include additional analysis by the BA assigned to the team.
...
2 replies by Naomi Caietti and Sergio Luis Conte
Apr 12, 2017 11:41 AM
Naomi Caietti
...
Agree John.

Organizations don't cater to standards; they embrace them, adopt them, refine them as their standard practice and embed them into their organizational culture. All PMs, BAs and sponsors adapt to their culture and continue to work to bring best practices into their organizations.
Apr 14, 2017 3:01 PM
Sergio Luis Conte
...
The project exists because a business analyst have performed the activity to define the solution, create a business case and get the approval for the project.
< 1 2 3 4 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

Conformity's an obsession with me.

- George Costanza

ADVERTISEMENT

Sponsors