In 30 seconds
- Transparency means nothing important is hidden: progress, risks or problems.
- It's the first of Scrum's three empirical pillars.
- You can't inspect and adapt what you can't see.
Why it matters
Teams make decisions based on what they can see. If the board says "in progress" but the work is stuck, every decision built on it is wrong. Transparency is the first pillar of empirical process control.
What should be visible
- The Product Backlog and its order
- Sprint progress on a board or burndown
- The Definition of Done
- Impediments and risks, including uncomfortable ones
What blocks it
- Fear of blame for bad news
- Metrics used to judge individuals
- Work tracked in private lists or side channels
Information radiators help, but only psychological safety makes people use them honestly.
Myth vs reality
Myth · Transparency means more reports.
Reality · It means visible, real work, not status documents.
Myth · Being transparent means sharing everything with everyone.
Reality · It means the right people can see what they need.
Myth · Tools create transparency.
Reality · Honest behaviour does; tools only display it.
FAQ
How do we make bad news safe to share?
Respond to problems with help, not blame, every time.
Is transparency only for Scrum?
No; it underpins Kanban and lean as well.
What's the simplest start?
A visible board that everyone updates and talks over daily.