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

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 ...

What is ITIL?

The term ITIL means "Information Technology Infrastructure Library". ITIL is the most popular and widely accepted approach to manage IT Service(ITSM). ITIL has been adopted by many organizations as the framework to manage their IT service. There are millions of practitioners worldwide with ITIL skills and capabilities. IT is important to keep in mind that ITIL is a set of best practices and not a standard, so organizations are free to adopt ITIL framework as is applicable or valuable to them. Advantages of adopting ITIL for your organization are immense. Therefore, all scale and size (Small , medium, Large) organizations all over the world use ITIL to help them improve the value of their services. The few important benefits of adopting ITIL are: ITIL creates stronger alignment between IT and the business Improves service delivery and customer satisfaction Reduces costs with improved use of resources Provides Greater visibility of IT costs and assets A Brief History of ITIL: ...

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...

World Of Agile

Search This Blog