Agile Glossary

Information Radiators

What is Information Radiators?

“Information radiator” is the generic term for any of a number of handwritten, drawn, printed, or electronic displays that a team places in a highly visible location, so that all team members, as well as passers-by, can see the latest information at a glance: count of automated tests, velocity, incident reports, continuous integration status, and so on.

Also Known As

  • a related term, nearly synonymous, is “Big Visible Chart”
  • more generally, one speaks of “informative workspaces

Expected Benefits

Intensive use of information radiators conveys two messages in addition to the information itself:

  • the team has nothing to hide from its visitors (customers, stakeholders…)
  • the team has nothing to hide from itself: it acknowledges and confronts problems

The main benefit of the practice is therefore to promote responsibility among the team members. A secondary benefit is that information radiators tend to provoke conversation when outsiders visit, which can yield useful ideas.

Origins

  • 1980s: the notion of “visual control” originating in the Toyota Production System is in anticipation of “information radiators”
  • 1999: the term “Big Visible Chart” is coined by Kent Beck in “Extreme Programming Explained”, though later attributed by Beck to Martin Fowler
  • 2001: the term “information radiator” is coined by Alistair Cockburn, part of an extended metaphor that equates the movement of information with the dispersion of heat and gas

Join us today!

Agile Alliance offers many online and in-person events and workshops for our members. If you’re not currently a member, you can join now to take advantage of our many members-only resources and programs. LEARN MORE >

Get the latest Agile news!

  • This field is for validation purposes and should be left unchanged.

By subscribing, you acknowledge the Agile Alliance Privacy Policy, and agree to receive our emails.

Additional Agile Glossary Terms

Definition of Ready involves creating clear criteria that a user story must meet before being accepted into an upcoming iteration. This is typically based on the INVEST matrix.
In software development, an "estimate" is the evaluation of the effort necessary to carry out a given development task; this is most often expressed in terms of duration.
A product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver in order to achieve a specific outcome.
Sprint planning is an event that occurs at the beginning of a sprint where the team determines the product backlog items they will work on during that sprint and discusses their initial plan for completing those product backlog items.
A high-level summary of the project's key success factors displayed on one wall of the team room as a flipchart-sized sheet of paper.
Refactoring consists of improving the internal structure of an existing program's source code, while preserving its external behavior.

Help us keep the definitions updated

Ready to join Agile Alliance?

Unlock members-only access to online learning sessions, Agile resources, annual conference discounts, and more! And when you join, you’ll be supporting our member initiatives, regional events, and global community groups.

Privacy Preference Center

IMPORTANT: We have transitioned to a new membership platform. If you have not already done so, you will need to SET UP AN ACCOUNT on the new platform to establish your user profile. Your previous login credentials will not work until you do this set up.

When you see the login screen, choose “Set up Account” and follow the prompts to create your new account. You can choose to log in using your social credentials for either Google or Linkedin (recommended), or you can set up your account using an email address.