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

PRINCE2's Project Organisation

PRINCE2's organisation theme defines the Project Team or organisation. It establishes the project's structure of accountability and responsibilities. As PRINCE2 is based on a customer/supplier environment, it assumes that there will be a customer who will specify the desired result and probably pay for the project, and a supplier who will provide the resources and skills to deliver that result. A successful project management team should have business, user and supplier stakeholder representation. Business The products of the project should meet a business need which will justify the investment in the project. Should also provide value for money. The Executive looks after business interests User The user viewpoint should represent those individuals or groups for whom some or all of the following will apply: They will use the outputs of the project to realize the benefits after the project is complete They will operate, maintain or support the project’s outputs The outputs of t
Read more

Scrum Timebox

Scrum relies heavily on the concept of Timebox. Timebox is setting a fixed time limit to any activity and letting other characteristics such as Scope vary. A time box could be ·           A Meeting ·           A Sprint ·           A Test activity ·           Development Activity ·           Or Practically anything such as you chatting with your friend on social networking site. The fact about timebox is that the time is limited. You can adjust other parameters such as ·           How much you can get done ·           Which item you must prioritize ·           However, deadlines cannot be moved. In Scrum, all the project iterations, meetings must be timeboxed and time limits be respected. This is very important and non-negotiable aspect of Scrum. Lets look at how a timebox actually works. ·           Timebox can be of any duration  - hours, months, years ·           It is essentially a control mechanism to ensure how much time you wish to devote
Post a 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 fash
Read more