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

Thank you to our Annual Partners​

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

The Given-When-Then formula is a template intended to guide the writing of acceptance tests for a User Story: (Given) some context, (When) some action is carried out, (Then) a particular set of observable consequences should obtain.
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.
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities for improvement.
An Agile team frequently releases its product into the hands of end users, listening to feedback, whether critical or appreciative.
An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios.
Antipatterns are common solutions to common problems where the solution is ineffective and may result in undesired consequences.

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.