Project Management

Please login or join to subscribe to this thread

Trust and reliance on Business Analyst on a project

linkedin twitter facebook   Requirements Management   Risk Management   Scope Management  
avatar
Teresa Sabino Project Manager| Open to Work! Ct, United States
Project sponsors and project teams don't always know exactly what they want or need in a project. This is where, in my company, the Business Analyst digs in and helps define the requirements for meeting the objectives of the project.

Should a project manager rely on / trust in the accuracy of the assigned business analyst to ensure all necessary requirements are identified and documented?

What can a PM do to ensure all requirements and scope are defined up front to prevent scope creep and change requests?
Sort By:
< 1 2 >
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Aug 10, 2017 5:06 AM
Replying to Anton Oosthuizen
...
By all means, disagree. That is how we all learn and grow.

The PM is ultimately responsible for the overall project schedule but it cannot be done in isolation. The PM will build out the schedule based on the information received from various other entities ie. the BA. The BA should develop a schedule for all BA related activities and then work with the PM to integrate this into the overall project schedule.I am not saying that there is an overlap in accountability since accountability cannot be shared. But there is a definite overlap in responsibility and how this overlap is handled is up to the org structure and culture. In an organization where you have a mature BA practice, this is normally understood and applied.

This is the same principle that applies to risks. Again I did not say that the BA take accountability for the risk register but the BA is responsible for working with the PM to ensure that risks are identified and documented appropriately.

So I guess it is important to understand that there are very specific areas for which the PM and BA are accountable but there are many areas where there is a shared responsibility and this is where a strong trust relationship must exist between the PM and BA.
Thank you Anton. Now I understand your point about overlaping. And I agree with that.
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
The BA is responsible for working with the customer to define all requirements related to the specific need. The PM works to execute the tasks with the defined timeline. Within execution there are risks, issues, and change requests the PM will also manage. Change requests that come in would also be reviewed by the BA - looking back at the Requirements Specificiation document to ensure within scope and leverage their relationship, business process, and product vision to assist in keeping the agreed upon product to be developed on track.

As Sergio mentions, once they see, there will be a request for change. This can almost be expected. It is human nature. The customer only knows what they know. The BA is there to ground and guide the customer through the product life cycle, to remind them of the original vision and recommend the path forward.

Take for example a group hike. The leader is there to guide the group through the hike following a previously mapped path. There is a time limit - only so much daylight. As the group walks, they will see many other possibilities to walk a different path - look over there at that butterfly. It is up to th guide to keep them on the pre-determined track, but on another hike, maybe they can take a look at that butterfly.

Really great comments from the group, and great discussion.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

Disbelief in magic can force a poor soul into believing in government and business.

- Tom Robbins

ADVERTISEMENT

Sponsors