Transparency
The Scrum pillar requiring that significant aspects of the process be visible to those responsible for the outcome, using common language.
What it means
Transparency enables inspection. Without a shared, honest view of the Product Backlog, Sprint Backlog, and Increment, any inspection is based on flawed information and adaptation decisions will be wrong.
The Scrum artifacts exist to maximize transparency of key information, and each has a commitment (Product Goal, Sprint Goal, Definition of Done) to make progress measurable.
Common mistakes
Transparency also depends on people being willing to disclose problems honestly. A culture that punishes bad news undermines transparency even if the boards and dashboards look complete.
Example
A team removes vague ticket statuses like 'in progress' in favor of explicit columns so anyone can see real blockers at a glance.