a product owner is not the boss of the team a product owner is not the patron or the UGA of
the team [Music] hello everyone welcome back to my channel today let's talk about product ownership
we'll be focusing on who is and is not a product owner and this content is going to be in many
different parts so today is just part one we're going to be going into a series to cover who a
product owner is the responsibilities of a product owner a typical day in the life of a product owner
the tools that the typical product owner will use and the kind of value that the product owner
brings into a standard agile theme so let's kick it off with our very first part before we do so
just for those who don't know me my name is Karen from my phone your agile evangelist
and again thank you for joining our little agile Village here we talk about I just scrum
um product management the agile ways of working with only one reason to continuously enhance our
knowledge in the agile space so let's go into it who is a product owner I'm just gonna go buy
the scrum guide today and then I'm going to share my experiences on who a typical product owner is
I would like us to see a product owner as one of the core accountabilities of a scrum team we have
three accountabilities we have the accountability of a scrum Master we have the developers and then
we also have the product owner so who is really a product owner this is how I need you to see a
product owner a product owner is that voice of the customer your product owner is that person
that represents the customers a product owner is that person that brings the ask or call it
the requirement or the what that has to be done to the team and then the team um converts this
ask into cool working tested functionalities you know the the accountability of a product owner is
extremely critical because it really helps cut down on having So Many Cooks in the kitchen you
know which is a typical problem in a waterfall environment you see so um the product owner
will ensure that they are collaborating with the customers they are collaborating with leadership
and then they are collaborating with the team putting all this information together to make
sure that they're asked of the customer is clear enough for the team to be able to deliver the
right requirements and deliver the requirements right so that is who a product owner really is
in a nutshell I would like you to see a product owner as the single source of Truth a product
owner is that one person that is accountable to the product backlog all of the work that has to
be done has to go through one container which is what we call a product backlog so that product
owner is that person that is accountable so that product backlog that is anything that comes into
the product backlog or goes out of the product backlog has to be vetted by the product owner
so that is who a product owner is in addition to that a product owner is just one person which
means that you cannot have two product owners in one team you see so in a nutshell that is who a
product owner is a product owner again really represents the customers a product owner also
represents the business together synchronizing the theme the business and the customers on
the overall product goal the product owner is that person that the team members who run to if
they need to have a clear understanding of what the overall product goal is a product owner is
that person that ensures that there is a clear road map that fits into the product by a clock
so that is who a product owner is in a nutshell now let us address who a product owner is not
this is the most interesting part a product owner is not a committee it's not a board
of of directors or Board of or management board no a product owner is only one person
and that one person represents the voice of every other leadership in the organization you know that
is where this statement comes in we don't want to have so many cooks in the kitchen so the role
of a product owner or the accountability of a product owner ensures that we are not doing that
a product owner is not the boss of the team a product owner is not the patron or the ogre
of the team no a product owner is the same as every other team member which means that
just the same expectation we have of developers the same expectation we have of a scrum master
from the values of the team standpoint such as commitment courage Focus respect openness we
have the same expectation of the product owner so that together we are succeeding as the team
a product owner is not that person that tells the team how to do the work
therefore a problem not only ensures that the team has a clear understanding of what they have to
do and then it's all up to the team to figure out how they want to achieve the result that has been
requested by the product owner a product owner is not that person that assigns work to team members
that is a product owner is not that person that tells who to do what's in the team no the product
owner stays out of the box same as a scrum Master only communicate what should be done and then the
team collectively collaboratively figure out who should be doing what so that they're achieving
the result so that's what a product owner is and who a product owner is not now why I think
this topic is really important is because you know being an agile coach and a mentor to many people
scrum Masters will typically come up with concerns you know real life concerns you know
their product owners want them to do things that the product owner should be doing their
product owners is assigning work to team members they are product owners um is bossing the team
around their product owners wants to track every single minute that the team is spending you know
and all of these things their product owner expect them to um to clarify on acceptance
criteria answer questions around product goal and stuff like that you know so that's why I
think this topic is really really important so understanding this topic will help the product
owner themselves or those that are looking to to um go into the product ownership role it will also
help the scrum master so that they can clearly understand and be more confident on what they
are supposed to be doing and and how a product owner is supposed to be supporting the team again
if you have any thoughts to share please leverage the comment section otherwise
hope this content was helpful and hope to see you in part two part two part two
we will be covering the recipe of our product owner so thank you so much and stay tuned bye