Show
As described in the Scrum Guide, a Scrum Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. The Product Owner is also accountable for effective Product Backlog management, which includes: Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible and understood. The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable. For Product Owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review. The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner. Product Owner TrainingProduct Owner CertificationScrum.org provides 2 levels of Professional Scrum Product Owner certification.
Product Owner Learning PathAlready a Product Owner or ready to start your journey? Visit our Product Owner Learning Path to take a guided tour through suggested resources for continued learning for Product Owners or search all Product Owner related resources.
The Scrum product owner is typically a project's key stakeholder. Part of the product owner responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the scrum team. This is key to successfully starting any agile software development project. The agile product owner does this in part through the product backlog, which is a prioritized features list for the product. The product owner is commonly a lead user of the system or someone from marketing, product management or anyone with a solid understanding of users, the market place, the competition and of future trends for the domain or type of system being developed. This, of course, varies tremendously based on whether the team is developing commercial software, software for internal use, hardware or some other type of product. The key is that the person in the product owner role needs to have a vision for what is to be built. Although the agile PO prioritizes the product backlog during the sprint planning meeting, the team selects the amount of work they believe they can do during each sprint, and how many sprints will be required. The product owner does not get to say, "We have four sprints left, therefore you must do one-fourth of the product backlog this sprint." The Scrum product owner's job is to motivate the team with a clear, elevating goal. Team members know best what they are capable of, and so they select which user stories from the top of the product backlog they can commit to delivering during any sprint. In return for the Scrum team's commitment to completing the selected user stories from the top of the product backlog, the product owner makes a reciprocal commitment to not throw new requirements at the team during the sprint. Requirements are allowed to change (and change is encouraged) but only outside the sprint. Once the team starts on a sprint, it remains maniacally focused on the goal of that sprint. The product owner role requires an individual with certain skills and traits, including availability, business savvy and communication skills. First, the Scrum product owner needs to be available to his or her team. The best product owners show commitment by doing whatever is necessary to build the best product possible – and that means being actively engaged with their teams. Business savvy is important for the agile product owner because he or she is the decision maker regarding what features the product will have. That means, the agile PO should understand the market, the customer and the business in order to make sound decisions. Finally, communication is a large part of the product owner responsibilities. The product owner role requires working closely with key stakeholders throughout the organization and beyond, so he or she must be able to communicate different messages to different people about the project at any given time.
The primary goal of an Agile Product Owner is to represent the customer to the development team. Product Owner Responsibilities include:
The Product Owner Role is an essential member of any agile scrum team. The primary goal in a Product Owner role is to represent the customer to the development team. A key activity is to manage and make visible the product backlog, or the prioritized list of requirements for future product development. In fact, the Product Owner is the only person who can change the order of items in the product backlog. One unusual aspect of Product Owner responsibilities is that you must be available to the development team at all times to answer any questions team members have regarding the customer’s view of how they’re implementing a product feature. Business Analyst: While the role of Business Analyst varies widely from company to company, in the Product Management arena, it usually aligns most closely with the role of Product Owner. Watch out for the following ‘gotchas’ to in order to succeed in a Product Owner role.
Skills and Competencies Required in the Product Owner RoleThe scope of the Product Owner role is broken down into four parts:
Product Owner ResponsibilitiesHere are some bullet points you may find in your job description outlining a Product Owner’s responsibilities:
The Product Owner MAY be asked to work on some or all of the following tasks:
If you also have Product Management responsibilities, check the list above and look at the image to determine how your actual role lines up. Is there any task that isn’t currently assigned to someone? Product Owner Role vs. Product Manager RolesProduct Owner Key DeliverablesProduct Owners maximize value through careful selection of what developers work on next. Here is a list of the most comment documents or deliverables that you may be asked to create and manage. Be aware that each company has their own specific list and terminology.
While the list of deliverables is short, Product Owners create many, many user stories as part of their work. What’s the difference between Product Manager and the Product Owner roles?The key difference between a Product Manager and a Product Owner revolves around their mindset when approaching a problem to be solved. Given a task or funding, the Product Manager responds, “If you give me this resource, I will deliver you this business result.” The Product Owner, on the other hand says “If you are going to spend this money, I will make sure you get the most value from your development investment.” Look in the Agile section for further information on how Agile and Scrum work. Required Experience and Knowledge in the Product Owner RoleProduct Owners call on a range of influencing and technical skills. Here is a list of what managers look for when filling a Product Owner role.
Many Product Owners have a bachelor level degree in the industry that their product serves or in development. Some also have additional business training. What you are most likely to hear a Product Owner say.“My development team and I worked closely to make sure that each of the user stories was completely understood. I am confident that they will deliver what we agreed on at the next product review.” |