In the previous newsletter, we discussed what a Scrum master does as per the scrum guide. Now it's the product owner's turn.

Did you know the Product owner is not a project manager. Yes, you read it right.

Let's start with the basics - what a Product owner does and what he/she does not.

What Does a Product Owner Do in a Scrum Project?

• Defining and Prioritizing the Product Backlog: A Product Owner's primary responsibility is to create and maintain the Product Backlog. This involves gathering requirements, user stories, and feedback from stakeholders, and then prioritizing them based on business value and user needs.

Here is the difference we need to understand- The product owner takes care of the requirement from the start not the Project manager nor the scrum master.

• Setting the Vision: The Product Owner communicates the product vision to the Scrum Team and ensures that all work aligns with this vision. They act as the bridge between stakeholders and the development team, keeping everyone focused on the end goal.

As per the Scrum guide, the Product Owner is the chief product visionary.

• Stakeholder Engagement: They engage with stakeholders to gather input and feedback, ensuring that the product meets their needs. However, they don't make promises or commitments on behalf of the team without consulting them.

It also includes a Sprint review. For better stakeholder engagement - apart from the daily scrum, the Product owner can set up weekly catchups and send weekly reports of the progress as well.

• Acceptance Criteria: The Product Owner defines acceptance criteria for user stories, providing clear guidelines on what constitutes a completed task. This helps maintain a shared understanding of what "done" means.
• Iterative Planning: They participate in Sprint Planning, helping the team select user stories from the Product Backlog for the upcoming Sprint. They also have the authority to accept or reject completed work during the Sprint Review.

Quick note: When there is a need to change the scope of the sprint - who decides? - Product owner and Developers

What a Product Owner Is Not Responsible For:

• Micromanaging the Team: The Product Owner should trust the Scrum Team's expertise and not dictate how tasks should be completed. Their role is about what needs to be done, not how it's done.

Did you know for multiple scrum teams for one product - there can not be multiple Product owners?

• Project Management: A Product Owner is not a project manager. They do not create Gantt charts, allocate resources, or manage timelines. Their focus is on product development and maximizing value.
• Technical Decision-making: While the Product Owner should have a good understanding of the technology being used, they are not responsible for making technical decisions. Technical choices are made by the Development Team with their expertise.
• Working in Isolation: A Product Owner should collaborate closely with the Scrum Team and stakeholders. They are not lone decision-makers but facilitators of communication and collaboration.
• Ignoring Feedback: Although a Product Owner has the authority to make decisions, they should not dismiss feedback from the team or stakeholders. Successful products often benefit from diverse perspectives.

Hope the above difference helps to manage your work and team well :)