This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
Is the Product Owner on the Scrum Team?
There’s still some confusion out there about whether the Product Owner is a member of the Scrum Team. Rather than pile on the confusion, please stick to Ken Schwaber’s terms: “Scrum Development Team” for the subset of the team that excludes the Product Owner, and “Scrum Team” for the dev team + Scrum Master + Product Owner. These are defined by _The Enterprise and Scrum_ (Schwaber 2007).
More on this here: http://blogs.collab.net/agile/who-is-on-the-scrum-team
We can debate if/whether/when we need this distinction, but I’d need to hear a pretty convincing reason to make up new terms rather than stick with Ken’s terms.
- Should your Product Owner attend your Daily Scrum and the entire Retrospective? Possibly, but I’ve seen cases it impeded self-organization. A Product Owner seeking higher performance through greater self-organization in the long run will ask the development team’s opinion on this. During Sprint execution, team members report to each other rather than any externally designated leader. This leaves a clearing for leadership to emerge by merit and consent. The Sprint Review meeting is our chance to see how well they kept the promises they made at the Sprint Planning Meeting. Sometimes — rarely for you, I hope — urgent short-term concerns require a command-and-control intervention. This creates another kind of debt which may or may not be easy to pay off.
- Should the Product Owner be highly technical? Usually not, but depends on skills and vision, doesn’t it? Modern software engineering practices tend to reduce technical dependencies, allowing business people to prioritize by business value and simpler effort estimates without deep technical knowledge. Of course, one reason we’re doing Scrum is to get business people and technical people to learn from each other. A legacy product steeped in technical debt, where technical dependencies dominate prioritization, will demand a Product Owner with a deeper understanding of the technology (and a technical debt repayment plan). A “rocket science” project may require a rocket scientist Product Owner.
- Should we have multiple delegate (or proxy) POs for multiple teams? Maybe sometimes, but we’ll regret not tying them to one uber PO. I saw a delegate PO get UNappointed by his chief PO who didn’t get the vision — doing Scrum helped uncover the problem in two weeks.Another time I saw it working fine because the delegate POs were completely in sync with the uber PO. Another very large Scrum implementation had local proxies on teams who were domain requirements experts with an extremely busy uber PO prioritizing for all of them. One way or another we need to increase the bandwidth (and reduce latency) between developers and customers.