Information Radiator

Information Radiators (aka. visual controls) are highly visible displays of information that summarize project data and progress. They are located in the public spaces and are easily accessible.

What is Information Radiator

Information Radiators (aka. visual controls) are highly visible displays of information. Agile teams use information radiators to visualize progress in a very transparent way. Information radiators are in the public spaces and are easily accessible. Some of the information that can be found on an Information Radiator include:
  • Features delivered versus features remaining
  • Who is working on what
  • Retrospective outcomes
  • Current iteration stories/features to be developed
  • Velocity and defect assessments
  • Threats and issues for the project
  • Burn up and burndown chart
  • Story maps
  • Kanban board
  • Blocked work items
  • Release plans
  • Team rules

Top related courses to Information Radiator

Related methods and techniques to Information Radiator

  • Planned versus Actual Velocity

    1. Planned versus Actual Velocity

    Planned versus Actual Velocity is a forecasting tool based on the on the observed and actual performance. The team can tell the customer whether they will finish the backlog of user stories by the planned number of iterations or not.

    Planned vs. actual velocity is a predictive tool based on observations and actual performance. It enables the team to tell the customer if they will complete the backlog of user stories before the planned number of iterations.

    The planned velocity is the team's expectation of the story points to be delivered in each iteration. Actual velocity refers to actual sum of the story points that they delivered in each iteration.

  • Burndown and Burnup chart

    2. Burndown and Burnup chart

    Burndown or Burnup charts show how much work has been completed and how much work is remaining as the iteration progresses.

    Burndown and Burnup chart present the same data in a different way. Teams choose how they would like to see their data.

    Some teams combine burndown and burnup charts into one chart. The chart shows the remaining actual story points as well as the completed cumulative story points.

  • Quality – passed test cases

    3. Quality – passed test cases

    Acceptance tests are written before new products are developed (on the back of the story cards). They ensure that the code meets the requirements. For software, the initial tests will fail because the code is not yet fully developed. If the code is written correctly, it will pass the tests.
    The higher the success rate in the tests, the greater the probability that there will be no failure in production.

  • Escaped Defects rate

    4. Escaped Defects rate

    Escaped defects are the defects that slipped by the testing team. The defect rate measures how often defects are found. Escaped defects are the most expensive to fix. An increase in escaped defects signals that a process is flawed.

  • Kanban board

    5. Kanban board

    Kanban boards are sign boards. Kanban (Japanese – "cards you can see") is a pull system where resources prevent work from piling up in a constrained process so that the lead time to deliver value to the business is not compromised. Work in the Kanban board moves from left to right and only limited number of items can be in each stage of the project. Teams are disciplined and committed to working within their specified Work-in-Progress (WIP) limits to ensure optimal flow in the system.