Scrum
Tasks of the product owner- Maintaining the product backlogs.
- represents the professional client side and
thus all stakeholders. - prioritizes product backlog items, so that
the business value of the product is
maximized and there is the possibility of
early releases of core functionality in order
to achieve a quick return on investment. - if possible, attends the daily scrums to
inform themselves (passive). - is available to answer questions from the
team.
I am the contracting authority, who
represents the professional point of view,
sets requirements and assesses the
subsequent implementation with regard
to functionality, usability, performance
and quality.What the product owner DOES NOT do- Assuming the role of the boss for the team.
- Moderate daily scrums or speak there
without being asked. - Influence the sprint backlog during the sprint
(additional requirements, deletion of tasks,
etc.). - Participate in the project as a team member
(e. g. developer, software architect) (conflict
of interest). - try to simulate the scrum master at the same
time (conflict of interest). - perform his task only at the beginning and
end of the sprints.
SometimestheproductownerisjokinglycalledSCN(singlechokableneck)inthejargon.To
makeitclear(andnotjokingatall):theproductownersisresponsibleforensuringthatthecorrect
requirementsareintheproductbacklogandthattheyareprocessedinasensibleorder.Inthis
way,theproductownerhasadecisiveinfluenceontheresultofhisworkand,inthisway,isreally
theonepersonwhose"throatischoked“whentheteamproduces-accordingtospecifications-
manure.Roles
Product Owner
Scrum