Back to the Foundations of the Scrum Framework (9) - How the Product Owner helps raising Transparency
Scrum is founded on empirical process control, and transparency is one of the three pillars.
Each of the Scrum Roles exist to also raise transparency to the other Scrum Team members and the stakeholders. If you feel that there is a lack of transparency for any aspect of your initiative, check who is best placed to bring clarity.
Note: transparency is way more than bringing “visibility”. It is about reaching ”a common understanding”.
Let’s take the Product Owner.
Bring common understanding about what?
- What is the current state of the product? What value does it bring today? What capabilities does it have?
- What is the user feedback? How is the product used? What is our market share?
- What is still needed in the product? What is expected to reach a specific goal? What is work remaining for this goal? What is the likelihood of achieving this goal?
As these questions are all Product related, I expect the Product Owner to be able to answer this type of questions. Answering or orally, or having this information readily available even if he/she isn’t available.
Not necessarily alone. Teamwork remember. So for details he/she could forward the requestor to other people who can be part of the Scrum Team, or maybe even outside the Scrum Team.
Anyway your Product Owner knows where to go for an answer.
Bring common understanding to whom?
To the entire Scrum Team and the stakeholders
Prompt: With your entire team, have a conversation about what additional transparency would help you to improve. And see where the Product Owner can support this.
I hope you find value in these short articles and if you are looking for some clarifications, or if this raises a number of questions, feel free to take contact at steven @ boostyourscrum . com
PS. Next week we'll look at the Developers and Transparency.
Don't want to miss any of these? Have the professional Scrum foundations series weekly in your mailbox.