Product Managers and other relevant stakeholders typically monitor and measure the progress of their projects using some form of project management software. This could include the different stages of the project lifecycle, track team performance, and assess the quality of the product.
This blog will introduce you to how you can embed this functionality directly into your own applications.
Bug Tracking Charts are used to monitor the number of bugs recorded and fixed during your iterations, showing in this way trends in bug confirmations, bug fixes, and bugs recorded in the backlog.
Below is shown an example of how you can create a chart of this kind on SpreadJS. Everything starts with the data source. Here is a table containing information for bugs reported and fixed during each sprint, the sprint duration, and the start and end dates.
To create a Bug Tracking Chart follow the instructions:
If you above issue when selecting your data and see that the series is not created as it should, SpreadJS offers a way of fixing it.
In our example is better to have Line With Markers for Bugs Fixed and Reported, and Area for bugs in Backlog.
Use the Format Chart Area method to do that.
In the Format Chart panel, you can change:
By making some adjustments you can manage to enhance the appearance of your chart and present your data in a more professional way.
The end result:
Analysis of the Bug Tracking Chart
When you have a big difference between the blue and the orange line, it is a sign that there might be some issues as the bugs reported keep mounting when you can't keep up with fixing the old ones. When that difference rises the green area rises as well.
The cumulative flow diagram highlights workflow bottlenecks, by charting the progress of stories through each stage of the sprint. The colored bands each represent one stage in the development workflow.
The table below shows the number of Tasks in different statuses.
To add a Cumulative Flow Chart (CFC) do as follow:
Analysis of the CFC
The graph can visualize bottlenecks in the process – a disproportionately large number of tasks in a certain status indicates a problem, so when we have a widening of any of these colored bands over time will indicate a bottleneck in the phase that follows it. In the provided example, So, when you have a big difference between the blue and the orange line, it is a sign that there might be delays as the bugs reported keep mounting when you can't keep up with fixing the old ones.
This chart is a graphical representation of the total effort against the amount of work for each iteration. It is mostly used to measure how quickly the team is working to resolve tasks or story points. Below there are the instructions for creating a Burn Down Chart.
You can do that by right-clicking on the chart, selecting Select Data, and Edit the series by selecting the first row of the dataset table as the range.
Understanding the Burndown Chart
By looking at the chart the management can track the total work remaining in the sprint or the possibility of achieving the sprint goal, and respond to trends accordingly.
A Burn-UP chart is used to track progress towards the completion of a project. This chart is a visual representation of a sprint's completed work compared with its total scope.
You can create a Burn-UP chart in SpreadJS by following these steps:
Understanding the Burn-UP Chart
The Velocity Chart shows the amount of value (hours, tasks, story-points, etc.) delivered in each sprint, enabling you to predict the amount of work you can feasibly commit to deliver in the next sprints.
Below is a list of planned and completed Story Points for the last seven sprints.
To create the chart follow these steps:
Analyzing the Velocity Chart
Velocity is calculated by taking the average of the total completed estimates over the last several sprints. So in the chart above, the team's velocity is:
(15+7+4+6+11+8+1) / 7 = 7.5
The management can use this to predict how much work can be completed by the team in a future sprint, in our case 7.5 story points, creating in this way more believable predictions.
The main goal of agile charts is to bring clarity to the development process. These charts deliver quantitative insight into different performance metrics and provide measurable goals for the group. For the success of your business combine the information that is given from these charts with your team's qualitative feedback. Only in this way, you will reach the needed level of adaptability that the agile methodology offers.
If you'd like to learn more about the amazing opportunities SpreadJS offers, get the free trial here.
To follow along, download the example file here.
Note: This is a .ssjson file. Please ensure your browser doesn't change the file extension on download. After downloading, import the file into the SpreadJS designer and discover all the amazing opportunities that SpreadJS offers.