On Nov 2, 2009, at 12:02 PM, Dan Rawsthorne wrote:
> Well, the PO is who the PO is - the team member who has the "last say"
> on the priorities of what the team does. If this person is technical,
> that's cool. But whoever it is must empowered to make decisions when
> team needs them to be made. Many teams have no such person, so they
> doing ScrumBut (I don't have a PO). If you have the luxury of choosing
> what type of person the Business will empower, then go ahead and
> a techie or a BO, or whatever makes sense to you. But it's the
> empowerment that counts, not the skillset.
> Dan Rawsthorne, PhD, CST
> Senior Coach, Danube Technologies
> jamesjhawkins wrote:
>> One of the principles of Agile as explained to me is Shared Knowledge
>> between team members. It seems to me that the PO must take part in
>> In my experience, the PO does have to make some technical decisions.
>> For example, they may have to set a relative priority on stories
>> there are technical dependencies. Even if they don't understand the
>> details, POs need at least enough technical knowledge to understand
>> the explanations given by engineers in the Scrum. Put simply, they
>> must be able to speak Geek.
>> In this, I see the PO as something like a requirements analyst. In
>> other words, they mediate between the technical and marketing people.
>> Cheers, Jim
>> P.S. Here's my blog post on Market vs Technology
>> http://unmethodical .posterous. com/market- led-vs-technolog y-led-an- interlude
>> In summary:
>> The Market knows what it wants, but not what it can have
>> Technology can innovate radically, but cannot place its innovations
>> within easy reach