Analytics in Kendis provides an overview of all the activities that are being done on the board. This information is summarized into graphical and tabulated formats that dispense all the necessary information one needs to know in just a glance. One of the key graphs under summary tab of analytics is PI Burndown chart.
What is PI burndown chart?
It is a graphical representation of effort remaining over a period of time. The PI burndown chart is an essential part of any scaling agile program and is a way for the teams to clearly see what is happening and how progress is being made during each sprint for the whole program increment.
How to read the chart?
The horizontal x-axis of the burndown chart shows the sprints; the vertical y-axis shows the amount of work remaining at the start of each sprint. Work remaining is shown in story points.
The graph shows two lines; Planned and Actual.
- "Planned" line is sum of story points from all the teams and sprints
- "Actual" line is sum of done story points by all the teams.
According to © Scaled Agile, Inc., "The Innovation and Planning (IP) Iteration occurs every Program Increment (PI) and serves multiple purposes. It acts as an estimating buffer for meeting PI Objectives and provides dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt (I&A) events".
To mark a sprint as an IP sprint at Kendis board, go to "Setting" and choose "Edit Board Settings"
Important: If a sprint is marked as IP, it will be shown as grey area at the chart and story points will be excluded from the chart.
Benefits of PI burndown chart
The PI burndown chart is an invaluable asset to planning and tracking. If used to its full potential, the Burndown Chart assists the organization or program in gaining insights with a more focused view of the work carried out by multiple teams. Research will become easier as would an ability to identify possible gaps or omissions. This would in turn, lend itself to further exchanges of ideas, conceptual thinking and reflecting regularly on how to become a more effective Team of Teams thus fulfilling another important principle of Agile
- A means of communication for stakeholders and the customers to provide feedback
- Visualizing the effort required for the completion of a Release Train
Enhancing accuracy in estimation
- Predictability of the PI’s
- Displaying the remaining effort at a glance
- Discussing the points for the Inspect and Adapt session
- Observing the variation in points during the PI
- Minimizing risk
- Presenting a glance of the entire PI allowing improved Scope Management.