Skip to main content

Tracking and Communicating Progress in Agile


Information radiators are meant to display information at a public place so that the information can be noticed by as many people as possible without making a conscious effort to do so. The idea of information radiator was invented by Alister Cockburn, who was a big believer in effective and timely communication. Information Radiators should display the current information about the project whatever is critical for the team to learn. It could include Schedule, tasks, issues, progress etc.
The Most common forms of Information Radiators are
·         TaskBoards or Kanban Boards
·         Big Visible Charts such as BurnDown Charts
·         Street Lights and Lava Lamps
Characteristics of Information Radiators which make the Information Radiators work
·         Simplicity : The information Radiators should be simple to read and understand
·         Stark : Should display the progress and expose problems. Errors should not be masked, instead, they should be used to improve performance.
·         Current : Information should always be current. The artifacts should be updated frequently.
·         Transient : The information should not be there on the chart for too long. Once the problem is rectified, it should be removed from the chart or board.
·         Influencial : The information displayed should help the team to take actions and decisions.
·         Visbile : the information should be easily visible. There should be no special effort to see the information.
·         Minimal Information : The information should be sufficient but minimalistic. There is no point in showing a truckload of information.
For Progress Tracking you can use below techniques:

Taskboards or Kanban Boards
Cumulative Flow Diagram
Burndown /up  chart
Risk Burndown Chart
Control Charts
Business Value Delivered Chart
Velocity Charts
Nico Nico Calendar
Parking Lot Diagram

For More Information Visit Our Blogs

Popular posts from this blog

What are Important Roles in Scrum-Agile Teams?

The Primary Team roles in scrum are named as • Product Owner  • Scrum Master • Development Team Scrum Master, Product Owner, and Team are considered as people who are committed to the project while customers and executive management are considered as involved but not committed to the project. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.  Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available. All the roles are based on the concept of “S...

Agile Administration in Tooling and Tool Integration

Tools are inherent to our jobs, inherent to how we solve the problems we face each day. Our comfort level with the set of tools that are available to us, and our ability to adapt to new tools as they evolve and shape our thoughts and ideas. The availability of collective knowledge within the palm of your hand combined with the collaboration across organization and company boundaries through open source software is dramatically disrupting the status quo of work. Companies mired in managing infrastructure configuration management by hand with unknown numbers of divergent systems, unable to quickly change and respond to market demands will struggle against their counterparts who have managed to contain their complexity on one axis through infrastructure automation. While it is possible to manage servers by hand, or even artisinally crafted shell scripts, a proper configuration management tool is invaluable especially as your environment and team changes. Even the best software developers ...