Skip to content

Why Scrum Product Owner is a Hard Job

December 28, 2007 by Artem Marchenko

Scrum teams as well as the teams applying another agile software development processes build software iteratively. Sprint by sprint they release increments of software that is DONE. Planning in Scrum is also done iteratively. Low priority coarse grained backlog items are refined when they come close to the top of the backlog. The purpose of such an iterative planning and releasing is not to maintain the original project coarse, but to continuously adapt to the changing business requirements and to the increased understanding of the technology and the subject area.

Frequent Decision Making

Therefore Product Owner has to continuously care about the project direction, refine its goals, make sure that the product backlog is reasonably detailed, still conforms to the product vision and that the vision itself is still valid. When possible Product Owner almost like XP's customer on site during the sprint continuously interacts with the team not only clarifying the product backlog items (ideally - user stories), but often also deciding which solution exactly is good enough for him.

This is quite different from what a traditional project manager might have used to. In Scrum the traditional planning phase is dispersed over the course of the project. It requires much heavier involvement during the development and calls for making business decisions frequently. Sprint by print Product Owner has to be actively involved in evaluating the team deliveries, accepting the challenges and in refining the project direction.

Customer Involvement is Vital for the Project Success

Not all the customers are ready for such a workload. However, the direct and frequent involvement of a customer or his proxy (product owner) is what it takes to build a software that is actually useful for the customer.

About the Author: As the Editor-in-Chief for AgileSoftwareDevelopment.com, Artem is charged with overseeing the direction for content, advertising, and the overall management of the site. Nowadays in his day life, Artem is a product manager in a global telecommunication company where he leads the development of a product developed in extremely distributed environment. Artem has been applying Agile and researching Agile since 2005. Contact Artem

Comments

Why Scrum Product Owner is a Hard Job

February 28, 2012 by Mark (not verified), 1 year 12 weeks ago
Comment id: 21070

I think that this will certainly be a good thing and they will obtain some good results from this.
Oferte Asigurare

I read that Post and got it

July 19, 2012 by Anonymous (not verified), 44 weeks 1 day ago
Comment id: 23417

I read that Post and got it fine and informative. Please share more like that...
slideshow mac

JOB

October 4, 2012 by jimmy88 (not verified), 33 weeks 1 day ago
Comment id: 24200

When you agreement your solutions then you will have a little more independence as to when you select to perform on a given job.Recruitment Careers Dubai

Scrum team always doing the

November 12, 2012 by EstonEtchingham (not verified), 27 weeks 4 days ago
Comment id: 24601

Scrum team always doing the hard thing simply because they the root of the companies success. It's like having a agent hypothécaire who's very good in every aspect especially in canada mortgage calculator then for sure everybody depends on him/her.

I just required some

February 18, 2013 by aisin (not verified), 13 weeks 4 days ago
Comment id: 26311

I just required some information and was searching on Google for it. I visited each page that came on first page and didn’t got any relevant result then I thought to check out the second one and got your blog. This is what I wanted!Celine bag 2013\\Rolex Watches

000-037 || 000-121 || 000-129

May 2, 2013 by shonteat (not verified), 3 weeks 1 day ago
Comment id: 27343

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.

Best of AgileSoftwareDevelopment.com