I've been having many conversations recently about how to set up the agile teams I'm coaching with the right Product Owner.  As we all know, the PO must be empowered to make decisions, yet must also be knowledgeable enough about what the software should do that she can make constant small decisions for the team so they don't have to wait.  The PO understands the big picture, understands the small picture, and can set priorities.

I blogged a few months back about how the "Team Room" must be considered a metaphor, not a literal prerequisite to trying agile for the first time.  I know I am treading on equally sacred ground (stepping into equally sacred cow pies), but I am going to posit along the same lines that in a complex corporate environment, the "Product Owner" should be considered as a small village, not a literal person.  (I hear the sounds of distant drums, or maybe bagpipes, preparing for war).  I believe if the village can reach consensus and speak with one voice in a timely way on a consistent basis, the whole agile development team will be in fine shape.  The trick is building the right village.

<more>