Provides an overview of how to build Agile / Scrum Task Boards that radiate information. Explains why physical boards are superior to electronic boards for being information radiators instead of information refrigerators.
Explains the core considerations for designing an effective Scrum Task Board. The importance of basic standards so the board is widely readable.
Discusses using board annotations to leverage the fact that humans are visual creatures. Also stresses the importance of making explicit policies of the team visible on the board, such as the definition of done.
A recommended supply list for building an effective, readable and reusable board is provided as well as steps for a team board building workshop / party.