The product owner *can* be a team
New Title here (not above, ‘cause that destroys the permalink): The Product Owner can be a whole team
In his new blog post Roman Pichler breaks with the supposed golden rule that a Product Owner must be a single person, not a committee an organized team.
As with so many things in Scrum - which I guess stem from the beginning, where neither large companies nor large projects were driven by Scrum - I could never believe that in every context only one Product Owner could deliver the whole product service a Scrum team would need.
I do like Occam’s Razor and I do like the approach of Scrum to keep things as simple as possible. But sometimes, I guess the world is not as simple as you’d like to have it and yes, there needs a structure of product owners to serve an organization.
Read on in Roman Pichlers posting. The way he puts it is much smoother than I could ever put it :-)
P.S.: During the course of discussion w/ @StefanRoock (see below) I came to belief that again this all is a very deep misunderstanding around wordings. It seems that a committee is regarded as something that is simply not sharing a common goal, whereas a team is following the same goal. So teams seem to be fine, committees are not, at least in the Scrum world. I’ll try to look that up somehow. Anyway, I changed this text so that there is no conflict with Roman’s posting and my discussion with Stefan.
