Comments on: Thinking outside the project: implied responsibilities of an agile product owner http://www.bridging-the-gap.com/thinking-outside-the-project-implied-responsibilities-of-an-agile-product-owner/ Advance Your Business Analysis Career Thu, 09 Feb 2012 00:08:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Charleigh http://www.bridging-the-gap.com/thinking-outside-the-project-implied-responsibilities-of-an-agile-product-owner/comment-page-1/#comment-10832 Charleigh Wed, 05 Oct 2011 04:56:50 +0000 http://www.bridging-the-gap.com/?p=600#comment-10832 Surprisingly well-written and inofrmtavie for a free online article. Surprisingly well-written and inofrmtavie for a free online article.

]]> By: Links for April 12 2009 | Eric D. Brown - Technology, Strategy, People & Projects http://www.bridging-the-gap.com/thinking-outside-the-project-implied-responsibilities-of-an-agile-product-owner/comment-page-1/#comment-324 Links for April 12 2009 | Eric D. Brown - Technology, Strategy, People & Projects Sun, 12 Apr 2009 13:56:38 +0000 http://www.bridging-the-gap.com/?p=600#comment-324 [...] Thinking outside the project: implied responsibilities of an agile product owner by Laura Brandau on Bridging the Gap between Business and IT [...] [...] Thinking outside the project: implied responsibilities of an agile product owner by Laura Brandau on Bridging the Gap between Business and IT [...]

]]> By: Paul Evans http://www.bridging-the-gap.com/thinking-outside-the-project-implied-responsibilities-of-an-agile-product-owner/comment-page-1/#comment-314 Paul Evans Thu, 09 Apr 2009 10:23:11 +0000 http://www.bridging-the-gap.com/?p=600#comment-314 Bookmarked for future reference :-) Bookmarked for future reference :-)

]]> By: Laura Brandau http://www.bridging-the-gap.com/thinking-outside-the-project-implied-responsibilities-of-an-agile-product-owner/comment-page-1/#comment-307 Laura Brandau Mon, 06 Apr 2009 17:01:11 +0000 http://www.bridging-the-gap.com/?p=600#comment-307 I see the perspective now, Bob. I was definitely thinking about any activities to define specific stories and help the team elicit the detailed requirements/test conditions as falling inside the project. But given your point, this line might be just about as arbitrary as any. It does raise an interesting question, however, in terms of how teams set expectations for what can be done within a sprint and what needs to be a precursor....I'm still challenged to see how detailed requirements can effectively be defined within the same sprint they are being built...but maybe that's me clinging to a piece of my waterfall/RUP hat! :-) I see the perspective now, Bob. I was definitely thinking about any activities to define specific stories and help the team elicit the detailed requirements/test conditions as falling inside the project. But given your point, this line might be just about as arbitrary as any.

It does raise an interesting question, however, in terms of how teams set expectations for what can be done within a sprint and what needs to be a precursor….I’m still challenged to see how detailed requirements can effectively be defined within the same sprint they are being built…but maybe that’s me clinging to a piece of my waterfall/RUP hat! :-)

]]> By: Bob Hartman http://www.bridging-the-gap.com/thinking-outside-the-project-implied-responsibilities-of-an-agile-product-owner/comment-page-1/#comment-306 Bob Hartman Mon, 06 Apr 2009 16:24:39 +0000 http://www.bridging-the-gap.com/?p=600#comment-306 Laura, it's interesting because many teams think it isn't within the project because it isn't done "by the team" as they define it. Too often "team" is developers and testers and that is all. A Product Owner doing anything is considered "outside." It will also affect how the backlog is prioritized. Changes needing to be made based on what is and isn't accepted for example. Good post though. Glad to see your blog succeeding! Laura, it’s interesting because many teams think it isn’t within the project because it isn’t done “by the team” as they define it. Too often “team” is developers and testers and that is all. A Product Owner doing anything is considered “outside.”

It will also affect how the backlog is prioritized. Changes needing to be made based on what is and isn’t accepted for example.

Good post though. Glad to see your blog succeeding!

]]>