HKSM
Transparency
Transparency means every aspect of the Scrum process is visible and understandable to anyone who needs to see it. Openly sharing information builds a high-trust environment across the team and stakeholders.
Key Points
- Make work, progress, quality, and risks visible to all stakeholders.
- Use clear, shared definitions (e.g., Definition of Done) and simple metrics to reduce ambiguity.
- Leverage information radiators like boards, dashboards, and burn charts; keep events open and observable.
- Openness builds trust, speeds decisions, and exposes issues early for inspection and adaptation.
Example
A Scrum team maintains a live dashboard showing sprint goals, backlog, WIP limits, impediments, and test coverage. Stakeholders can view it anytime and are invited to Sprint Reviews. When a dependency blocks a story, it is flagged on the board the same day, enabling quick alignment with the dependent team.
PMP Example Question
During a sprint, a director asks the Scrum Master for a private status report. Which action best supports transparency?
- Prepare a tailored report for the director to avoid disturbing the team.
- Refer the director to the team's shared dashboard and invite them to the Sprint Review.
- Ask each developer to email daily progress updates to the director.
- Wait until the Retrospective to discuss how to provide private reports.
Correct Answer: B — Use shared, openly visible information and events
Explanation: Transparency is achieved by making the same information available to everyone via visible artifacts and open Scrum events; private reports undermine a single source of truth.
