This last week I had
the extraordinary privilege to speak at the Project Management Institute (PMI) Honolulu Chapter Professional Development Day (PDD)2014.
In speaking to a group of Project Managers about How to Effectively Work with a Business Analyst, a great question came up about how you deal with a PM and BA working together who's lines for roles and responsibilities begin to blur. Considering real world examples and how to address this, the answer that was so positively received was - "What, Why, and How".
In speaking to a group of Project Managers about How to Effectively Work with a Business Analyst, a great question came up about how you deal with a PM and BA working together who's lines for roles and responsibilities begin to blur. Considering real world examples and how to address this, the answer that was so positively received was - "What, Why, and How".
Whenever a PM and BA are having a conversation, a great thing to consider whenever roles and responsibilities begin to blur is that the PM should consider the WHAT and the BA to consider the WHY. Those are the swim lanes to stand in. What - the project, the schedule, the scope, the budget - these are all PM responsibilities. They have a specific answer and the PM ensures they move to completion. WHY - why is the project good for the business, why the requirement should be included, why the test cases are required - this is where the BA lives.
I took it a step further from personal experience that the BA (and also PM) needs to especially recognize when they delve into the HOW realm. The moment they start determining HOW something should be done, you're getting into Design. This is the swim lane for your SMEs, architects and designers. It keeps the roles and responsibilities clear. It's also extremely helpful when developing business requirements as you know you've gone far enough when you start to explain HOW the feature is supposed to look, act and feel.
