I'm pretty new to the Scrum thing. I'm reading more and more of it. I'm very enchanted by the idea.
What is the "Physical Information Radiators" that he's referring to under the "Three Best Practices"?
Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up.Sign up to join this community
Physical information radiator is pretty much anything which:
A few examples of radiators:
To give you an example, here's a photo of one of our team's automated Information Radiators, which provides a continually present summary of metrics important to us. Each part of this screen is dedicated to monitoring a different aspect of our development pipeline or operational systems.
The bottom left quadrant contains the status of our CruiseControl.NET builds. If a developer commits code to the source code repository that fails to compile, fails the automated tests or cannot be automatically deployed, a segment will become red. Across the top are sections for each staging environment: internal test (alpha), UAT (beta-testing) and live (production). The display also contains sections for monitoring the performance of key services to provide early warning of application or infrastructure issues.
We've found this ability to visualise the system in real-time gives us a greater feel for the system's characteristics and as a team it's enabled us to become more proactive in preventing potential issues. Also, it's a great talking point that helps increase our project's exposure to other teams as they pass by.