The Product Backlog and Transparency - Back to the foundations of the Scrum framework (06)
Scrum is founded on empirical process control, and transparency is one of the three pillars.
Each of the Scrum Artifacts exist to bring transparency to the Scrum Team and the stakeholders. If you feel that there is a lack of transparency for any aspect of your initiative, have a good look with your team at your Artifacts.
Note: transparency is way more than bringing “visibility”. It is about reaching ”a common understanding”.
Let’s take the Product Backlog.
Common understanding about what?
About what is still needed in the product? A forecast.
About what is expected to reach a specific goal?
About what is work remaining for this goal?
Do you still have a separate “release plan”...? Why? Check how you can show this information in the Product Backlog.
Show trends of remaining work Sprint after Sprint. This brings transparency in the likelihood of achieving this product goal by a desired moment in time.
What else do you want to understand at the product level? Evaluate with your team how you can bring this information available through the Product Backlog.
Common understanding amongst who?
Amongst the entire Scrum Team and the stakeholders.
Summary: Does your Product Backlog bring a common understanding about the future of your product?
Prompt: What does Transparency mean to you and your team? And how do you and your team raise Transparency using the Product Backlog? How can you improve on this?
I hope you will find value in these short articles and if you are looking for more clarifications, feel free to take contact.
Don't want to miss any of these? Have the professional Scrum foundations series weekly in your mailbox.