I looked for an appropriate place to post this question, but nothing really jumped out. Any advice as to a better place to post would be appreciated.
I am about to take a role as a BI Product Owner, but there is some debate as to how to structure the team. Some of the articles and white papers discuss a BI 'team' but this causes me a few conceptual concerns. If I read people like Craig Larman (Large Scale Scrum) he advises creating a 'feature team' that works across the stack to create a coherent customer-centric product. That might include embedded BI to the extent that the customer wanted it and found it valuable. If so, the feature team might need BI skills, as well as their other cross functional skills to deliver, but at least they would understand the data since it would be part of their app.
However, BI is also a valuable internal product...using customer/app data to deliver customer insights, but also a whole range of internal operational issues that the customer might have no interest in. If you create a BI team centred on that 'product' then you have diverged from the customer-centric view (at least from a revenue generation point of view) but also you have a team that is not working right across the stack and doesn't work directly with the data.
Does anyone see that as a tension? Any thoughts/ideas/observations/resources?
All input gratefully received.
Ged
