12711Re: Background and Skills for PO (was: RE: [scrumdevelopment] Re: So, what would you do in this situation?)
- Apr 2, 2006
When I was speaking of an "effective" PO, that qualifier wasn't meant to be limited to the context of the product team. Within the context of the team, the main criteria is that the PO be able to champion the fight for the customers' interests.
Since ultimately Scrum is about maximizing competitive advantage, the team ought to be generating maximal value for the customers at each iteration. In order to do that consistently, it takes more than just passion. It also takes high developed communication and critical thinking skills and access to domain expertise (it is beneficial if the PO has domain expertise, but access to it will suffice) so that the Sprint backlog is always allocated with the items of highest value. It also takes someone who is willing to take risks and sees the value of betting on his team.However, the reality is that most POs are middle managers who, as Mike said, are looking out for themselves, are not effective communicators, don't care about the customers, don't like taking risks, and don't want to do too well on something at the risk of getting pigeonholed for that position over the long-term (they want to do well enough to get promoted out of their current positions, but not so well that the higher ups see more value in keeping them in their current positions). In my experience, most people who fall into the role of PO don't want to be there, for whatever reasons, and that hurts the team's ability to succeed. Even worse, many of these middle managers got to where they are by being clever liars, by taking advantage of the trust of others, or by knowing the right people -- none of which translate to an ability to be an effective PO.
On 4/2/06, Ken Schwaber <ken.schwaber@...> wrote:
As a minimum, be the person who has the vision for what they want done and the funding to do so,
- << Previous post in topic