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
Labels:
Location: India

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...
1 comment
Read more

The Service Value System - Continual improvement | ITIL V4 Certification

Continual Improvement Continual improvement takes place in all areas of the organization and at all levels, from strategic to operational. When provisioning a service we should always keep continual improvement in mind, and should always be looking for opportunities to improve. To support continual improvement at all levels, the ITIL® SVS includes: ITIL® Continual Improvement Model provides organizations with a structured approach to implementing improvements Improve Service Value Chain Activity Continual Improvement Practice Continual Improvement Model Continual Improvement Model can be used as a high-level guide to support improvement initiatives.  The model supports an iterative approach to improvement, dividing work into manageable pieces with separate goals that can be achieved incrementally. The scope and details of each step of the model will vary significantly based on the subject and the type of improvement The steps of this model do not need to be carried out in a linear ...
Read more

What is Definition of Done?

Done Criteria are a set of rules that are applicable to all User Stories. A clear definition of done is critical because it removes ambiguity from requirements and helps the team adhere to mandatory quality norms. This clear definition is used to create the Done Criteria when a Prioritized Product Backlog is prepared. Definition of done is crucial to a highly functioning Scrum team. The following are characteristics that you should look for in your team’s definition of done. Verifying that your team’s DoD meets these criteria will ensure that you are delivering features that are truly done, not only in terms of functionality but in terms of quality as well. DoD is a checklist of valuable activities required to produce software. Definition of done is a simple list of activities (writing code, coding comments, unit testing, integration testing, release notes, design documents, etc.) that add verifiable/demonstrable value to the product. Focusing on value-added step...
Post a Comment
Read more