Thanks, John. Glad you’ve found the post helpful.
]]>Thanks for sharing, Paul.
]]>we work with the second way as we are an agency and our teams work for different clients in a year’s time. They mostly are not able to provide a full time product owner. The big advantage of the second way is that we have skilled Product Owners that work very close with the team throughout the year. They build a real Scrum team and don’t have to restart the team building process with every new project. Like you said a big challenge is the empowerment of the Product Owner.
Cheers
Paul
Good way to point out the two models!
]]>Hi Stefan, I don’t like the term customer-proxy either but I’ve used it for the lack of a better one. Is there a synonym with a more positive connotation? I completely agree that the product owner needs to have a vision of the future product – which should be validated by gathering customer and user feedback on early product increments / working software.
]]>I like the way you are exploring the role of the product owner, and explaining who can embody the role…
I would like to republish your post on PM Hut ( http://www.pmhut.com ), where a lot of project managers will benefit from it. Please either email me or contact me through the “Contact Us” form on the PM Hut website in case you’re OK with this.
]]>Great point, Vin. I couldn’t agree more that early and frequent customer feedback is essential to develop the right product. I would add though that the product owner should have a vision that acts as the shared, overarching goal and that allows to evaluate the feedback received.
]]>For these reasons, it is essential to deliver early and often so that the real users and stakeholders can see for themselves and offer feedback. If they are not available to do so, at least you made a good faith attempt to involve them.
]]>