Re: Multiple Customers in Different Localities
- Unfortunately, this may be a case when you have to take a step back
from an "ideal" agile structure and depend on a sort of contractual
arrangement between the stakeholders and the team. When you have more
than one product owner, you don't have a Product Owner. They will vie
with one another to have the features each feels is important for
his/her own area, quite possibly at the expense of the overall benefit
of the project.
Would it be practical to have a "customer proxy" role on the project
(filled by a customer liaison rather than by one of the actual heads
of operations, since no one of them can act objectively in the best
interest of the whole organization), and to insulate the development
team from these ten-odd product owners so they won't cause morale
problems when they fight over story definitions or story priorities?
Not a very fun role, but possibly a helpful one.
--- In firstname.lastname@example.org, Graeme Matthew <scrum@...> wrote:
> Instead of trying to re-invent the wheel I thought I would post this
> get some feedback.
> Any recommendations on handling a group of customers that are
> different states (i.e a national software product). Each has a
> significant say ( head of operations) and there are about 10 of them in
> This poses a problem when trying to identify high level requirements
> (workshops, stories) as the company operational standard differs across
> We need a single product owner to interface with and to own the product
> I was thinking of creating a customer board and having the board decide
> on 1 representative who could act as product owner. In the event of say
> that product owner going on annual leave he / she in conjunction with
> the group can appoint a fellow board member to act on their behalf.
> Many thanks
> Graeme Matthew