About the Blog

  • Software is our business, and perfecting the art and science of delivering it is our mission. The contributors to this blog are passionate about the impact that great teams and good software can have on an organization’s bottom line. They bring decades of experience designing, developing and delivering great software, and each is playing a critical role in Borland’s own transformation.

Blogging Authors

« He's got a roadmap of Jupiter, a radar fix on the stars | Main | I was close, gettin' closer, just this far away; come to find out close only counts in horseshoes and hand grenades »

February 24, 2009


Feed You can follow this conversation by subscribing to the comment feed for this post.


Hi Dale,

I like your take on the product owner. Your article shows the delicate role that the product owner has.

I think the choice of Product Owner can greatly affect a project. The balance between the stakeholders and the development teams needs to be maintained, to ensure the deliverables are being met to the customer satisfaction, but without reduction in quality which can be caused by overkill from an overzealous Product Owner. As you say, a 'collective benefit' needs to occur.


Jim Dale

So where's Nick Hodges blog?

Laura Brandau

Nice article and I especially agree with the point that the product owner needs to be the final decision maker, but will be supported by a myriad of contributors. For most projects, the product owner role would be way to cumbersome if one person was required to actually do all that was necessary to meet the accountabilities.


The comments to this entry are closed.