November 5, 2020, 8:30 a.m. to 6 p.m. EDT | November 6, 2020 – February 7, 2021, On-Demand | Online Conference
Please login or join to subscribe to this thread
When it is good, it is very good. When it is bad, it is horrible.
As usual, it comes down to the people involved, their understanding of their respective roles, and how well work flows between those roles.
Came across a BA that said that the requirements specifications they created were always "perfect" and there was no need / room to change.
BI’s mostly gather information, determine operational objectives, evaluate outputs, and make reports/charts to be used by management to make decisions. The PM ensures the project collect and provide all the necessary information the BI needs to do his job. For sure, the BI do not plan and execute projects.
Business Analysis when performed 'right' is an amazing asset to the organization. I don't have any stories, and have fortunately had good experiences, including when I was the BA :), but could definitely see some chaos from a poor BA.
In our company, as consultants, we do both BA / PM work so my experience with myself has been good so far :D
I'm both so I'm probably my own worse nightmare :)
I believe what Kiron said is true but for most things. I have always believed that the link between PM and BA is very clear and there should be a role that encompasses both. I have performed both roles at the same time but also separately and to be honest, I have never come across a love/hate situation. Some conflict like we get in any project team, yes, but nothing that is not manageable.
I agree with Kiron that it's all about the people. I've had the fortune of working with some exceptional BAs who seem to just "get" what we're trying to achieve and what the impact/bigger picture is.
Please login or join to reply