Requirement vs. Project Manager

A lot of times especially in Malaysia, BA and PM work can somehow overlaped, a BA is responsible for analyzing the business needs of clients to help identify business problems and propose solutions; a PM is responsible of the planning, execution, and closing of any project. Let's put this into another angle, what does project means here? In a SDLC, a proper objectives and scopes need to be identified, in which these scopes and objectives draw the content of a project, therefore BA should be handling the requirement phase and PM should be handling and monitoring all activities of all stages until the the closure of the project. However, a lot of times, BA has more knowledge of an organization and the business needs and the system requirements, with this a lot of times, the BA will normally has the whole plan on who the system will work, integrate and to be UAT, and most of all, the BA also dealing with the business users most of the times and knowing the needs and expectations are no doubts much better and i would say they will see a bigger picture in this manner.

It always come to frustration on this matter and worst when miscommunications happen between PM and BA and not to mention when the ambiguous messages delivered to the technical team later. A lot of times an argument raise "DO we need a PM? ", or "When will we need a PM?" and this could be an interesting topic to talk about again.