Hi Mike,
We know the business analysis is key to the scrum team. The Scrum Guide outlines some great points on the development team – especially with the titles Product Owner & Scrum Master but while these are ‘role titles’ it is important to consider the activity, tasks, deliverables, techniques and competencies. So in this case what value does Business Analysis play in this team (or stage for your scenario), then whether the team has the adequate capability to effectively deliver this value and the BA can play multiple roles if they have the capability. Scrum Guide 2017
So if you extract the BA from the Dev Team during Development, are you confident that Business Analysis will be used to ensure the developed item meets the desired outcomes? What about defects? What about decisions made re acceptance criteria that may not be met due to time/complexity? Who is tracing this back to the sprint goal and product outcomes?
One factor to consider here is the option for the BA to fulfill the function of Product Owner in support of the Product Manager. So the Product Owner being more detail oriented, aligning the backlog to the product vision, providing input into the backlog items, and ensuring the developed product and the product going through development aligns to the goal of the iteration. See Abi’s & Tim’s presentation regarding the Product Owner
This then leaves the Product Manager to manage the overall product vision, roadmaps, marketing, revenue etc which will be reported (I imagine) at the board level.
For the BA it is about looking at our capability as a service – Business Analysis – rather than looking at our capability as a Role Title – Business Analyst. Remember the IIBA states, you don’t need to be titled a Business Analyst to be performing business analysis activities, therefore business analysis can be performed by various roles – so long as the individual possesses the capability.