Scrum is founded on empirical process control, and transparency is one of the three pillars.

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders need transparency so there is a common understanding.

Transparency as such is way more than bringing “visibility”. It is about reaching ”a common understanding”.

PS. Remember from earlier posts: I will repeat the above few lines in the coming blog posts: repeating = learning. 😉

Today, we check the Sprint Retrospective. 

Common understanding about what? 

About how the Sprint went. What do we feel worked well? What do we want to improve?
About which actionable improvements the Scrum Team will take on in the next Sprint. What actions will we take for the things we want to improve?

When I am supporting teams I often see in the beginning that the team members stay at the surface of what has happened during the Sprint. Not wanting to hurt the feelings of the colleagues. Yet it is important to raise the understanding of what all team members have experienced and how to move forward together. The Scrum Values do help here – more on how these support transparency in later articles.

I have witnessed teams discussing for hours a minor detail in a procurement process step that was not in their hands to make a change – how much it delayed them. While there was a major conflict between three team members – a conflict obstructing collaboration.
Make this understood, transparent, so the entire team understands and can act together. 

Common understanding amongst who? 

Amongst the entire Scrum Team: the Product Owner, the Developers, and the Scrum Master. 


At the end of your Sprint Retrospective, does your Scrum Team have a common understanding about what they will improve and what actions they will take?


Together with your team have a conversation about

What does Transparency mean to you and your team?
And how do you and your team use the Sprint Retrospective to raise Transparency?


I hope you find value in these short posts and if you are looking for more clarifications, feel free to take contact.

If you want to take a deeper dive into the core concepts we are covering in this blog series, then surely check out our Professional Scrum MasterY workshop. We have some scheduled in the coming period.

Don’t want to miss any of these blog posts? Have the professional Scrum foundations series weekly in your mailbox.


Leave a Reply