The document discusses the roles in Scrum and which role is key to ensuring product success and value. It argues that the Product Owner role is the most important because they are responsible for understanding stakeholders, determining what provides the most value, and ensuring the product earns money for the business. While the Scrum Master and Development Team have important roles, only the Product Owner focuses on business needs and the biggest value. If there are problems with the product, finding a better Product Owner who provides truthful guidance about the product is the solution.

1. What is a key
to solution?
We have a little problem in our
product developed by the Scrum...
Client (this person who is paying) says:
I see no value! I see some
velocity chars, your events
are awesome, like Review,
but my product don’t earn
money!

2. Scrum Master is not a key! WHY?
● No unique knowledge
● Managing only the process,
● No business power, only Scrum Flow
● Hard to work on the flow level
● If its a position -> not bring an any clear
value (as a definition it’s a role)
● No influence for a team structure
● Has to work with this team and have to
improve velocity
● Not bring money, just manage what we
have
Not enough to
say that this is a
key!

3. Dev Team - only doing job!
● Check what next to do
● Making “sweet farting” during the
retrospective
● Has to work better and better
● Can cut a wrong forest during a full sprint
● They are for just implementing ideas in a
best possible way
● Doing these funny Scrum meetings
● Making impediments ;)
Only
implementing

4. PO is a key! YES! PO!
● Check who is a stakeholder
● What has to be done next
● Check a biggest value for now
● Look for a business of all stakeholders
● Cooperate with CEO/PM/PMO
● Understand everything! Everything!
● Looking for a good forest to make a cut
● Fixing a bad understanding of
everybody
Good PO
=
Good product

5. What if there is a problem...
Scrum Master - making retrospective, looking for impediments, talking with a team
participants, collecting a feedback, preparing a coaching, etc
Dev Team - blamestorming, following a Scrum Master or a Product Owner, no
power to provide a real change
Product Owner - working with a business to adjust plan, to not waste money,
looking for a most efficiency solution/value in this moment,

6. Who will bring you money?
Scrum Master with a “hokus pokus” with
a Scrum Framework?
Dev Team with a best possible way to fix
a problem?
Product Owner who will say what is a
biggest value to do now?

7. Problem with a Scrum?
FIND A BETTER PO,
who tell you a true
about your Product!