CAPM Practice: Explain when it is appropriate to use an adaptive approach

Transparency is one of Scrum's three pillars (with Inspection and Adaptation). It means that all aspects of the process, the work, and the progress must be visible to those responsible for outcomes. A Scrum board showing actual status, a burndown chart showing actual velocity, and a Definition of Done applied consistently are all transparency mechanisms that enable honest inspection.

**Why not A:** Publishing individual performance metrics is a surveillance and evaluation practice that actually undermines Scrum's transparency pillar by creating an environment of fear rather than collective team ownership. Scrum transparency is about making process, progress, and impediments visible — not about ranking or monitoring individuals. Such metrics can incentivize local optimization at the expense of team collaboration.

**Why not B:** Open-source licensing is a software distribution model with no direct relationship to Scrum's transparency principle. Scrum transparency is an internal operational principle about making work visible to those responsible for it, not a statement about intellectual property or public access to source code. A commercial team using Scrum with proprietary software is fully transparent in the Scrum sense.

**Why not C:** Sharing financial data broadly regardless of sensitivity would be inappropriate and is not what Scrum's transparency principle requires. Transparency in Scrum applies to the work, the process, and progress against the sprint goal — it does not mandate unrestricted disclosure of commercially or legally sensitive financial information. Transparency is purposeful visibility to those who need it, not indiscriminate disclosure.