Information RadiatorsBrendon Page
Overview
What is an information
radiator?
Why are they useful?
What makes a good
information radiator?
Examples, examples, examples
Alistair Cockburn (2000)
What is an Information Radiator?
A display posted in a place where people can see it as they work or walk by. It shows readers information they care about without having to ask anyone a
question. This means more communication with fewer interruptions.
Why are they Useful?
More communication
with fewer interruptions
Better communication
Important information is
visible
You can’t yell at a board with stickies on it
Key to Project Success
What Makes a Good Information Radiator?
Big Simple
Maintained Location
Examples
Agile Board (Scrum, Kanban … etc.)
Displays current work to be done and the team’s progress through that work.
Agile Board (Scrum, Kanban … etc.)
Work to do Work in Progress
Completed Work
Project workflow
Multiple Columns
Multiple Columns
Multiple Columns
Agile Board (Scrum, Kanban … etc.)
Used at stand ups
Updated in real-time
Everyone knows status of
work
Evolve your board
Agile Board (Scrum, Kanban … etc)
Bugs Column
Descriptions
Velocity
More Done Columns
Column Limits
Working Agreement
Displays the important items that have been agreed upon for the project.
Working Agreement
Sprints
Code Reviews
ALM
Adding Work
Completing Work
Shared understanding
of working expectations
Working Agreement
Typically used at the start of a
project
Updated when working
expectations change
Offload burden of process from
the team’s minds
Can contain anything
Can stagnate but still useful
Project Health
Displays statistics that are most relevant to the projects health.
Project Health
Stats of areas that need work
or are important
Code Coverage
Rules Compliance
Code Coverage
Cyclomatic Complexity
Burn Down
New Internal Project
Old External Project
Specific Areas Mentioned
Project Health
Used at stand ups
Updated every stand up
Visibility Reminds and Motivates the
Team
Code coverage is a must!
Core Domain
Displays a diagram of the core domain.
Core Domain
Domain Model
Relationships
Knowledge
Brainstorming
Core DomainUsed during discussions about the domain
Updated when ever the domain changes
Updates immediately available to everyone
Helps team adoption of ubiquitous language
Critical to DDD Critical to DDD
Architecture
Displays the high level architecture of the project.
Architecture
The big picture
Free form diagram
Architecture
Typically used at the start of a
project
Updated when ever the
architecture changes
Everyone gets to see the big
picture
Tend to stagnate as
project matures
Red Bin
Displays technical issues which couldn’t be solved immediately and/or were a cause for concern.
Red Bin
Undiscussed Issue
Accepted Issue
Acceptance Indicators
Technical issues
Red Bin
Use at stand upUpdated every stand up and in
real-time
Issues are raised,
discussed and addressed
Borrowed from lean
manufactoring
Human
Displays a piece of information about a team member.
Human
Time since last smoke
Personal info
Human
Use organically, normally at
stand up
Updated by the person
Builds moral by supporting
team membersTeam maturity
Other Considerations
Digital Radiators
Radiator overload
Raw data VS information
Conclusion
More communication
Big, Simple, Maintained &
Location
Tonight's list is far from
comprehensive
The red bin is awesome try it!
Top Related