Brief Introduction: As the project leader, how can we keep abreast of the latest progress and problems of the current project and understand the overall status of the project? As a project manager, how do we follow up and promote the normal progress of the project? How to use the cloud performance Insight platform to help project managers find problems and deviations in a timely manner, advance project progress, ensure project iteration and high-quality delivery.
As a project leader, how can we keep abreast of the latest progress and problems of the current project and understand the overall status of the project?
As a project manager, how do we follow up and promote the normal progress of the project?
With these two questions in mind, we move into the agile project metrics scenario and talk about how the cloud performance Insight platform, Insight, can help project managers spot issues and deviations in a timely manner, advance projects, and ensure project iteration and quality delivery.
In Cloud Performance Insight, we can track project performance in three dimensions:
- Look at the overall status of the project: understand the overall operation of the project (or delivery team);
- Look at project delivery trends: understand the rate, quality, and progress of project iterations;
- See resource investment status: understand the work distribution of team members and ensure the investment and delivery of key items in the project.
Look at the overall status of the project
Within cloud Insight’s agile project metrics report, by ** Project Progress and Requirements/Defect Status Overview ** indicator cards, we can:
- Quick insight into the overall project performance, such as progress, deviations, risks, issues, requirements/defect progress, etc.
- Fast access to requirements, defect throughput, and overdue status for selected time periods.
Based on these data, we can follow up and solve risks and problems in a timely manner. If we find anomalies, we can take quick action. For example, when we see too many defects, stock risks and overdue items in a project, we need to quickly push the project leader to expedite the completion of the project and quickly solve the defects, risks and overdue items, so as not to become the final delivery point of the project.
Look at project delivery trends
In cloud Insight’s agile project metrics report, using ** “Demand trends” and ** “Defect Trends” metrics cards, we can:
- Understand the requirements of the project, the addition and completion of defects, master the delivery mode of the team, and identify problems and risks in advance;
- Understand the development trend of project requirements and inventory of defects.
When observing the trend of requirements and defects, we need to focus on:
1. Look at stock trends
Through the inventory trend of demand and defect of the project, when the inventory curve is high, the timely completion of key demand and defect can be quickly promoted; When the stock demand curve is low, it is necessary to check the demand planning to see whether there will be demand interruption. When stock defects gradually or suddenly go down, it is necessary to check the quality of demand testing, whether it is really good quality or inadequate testing;
2. Look at the team’s delivery model
If defects are not found for a long time and a large number of defects are added in a certain period of time, it can reflect the waterfall delivery mode. Timely intervention is required to avoid centralized and batch integration, shorten the time of problem exposure, and establish a fast feedback mechanism.
Secondly, we can observe ** “demand delivery rate” and “Defect Repair rate” ** indicator cards. With these two indicator cards, we can:
- See the number of requirements delivered, defect fixes per unit time, and the average number of requirements and defect deliveries per unit time in the selected time period;
- See the trend of requirement delivery rate and arrange the team’s future delivery pace and commitments based on recent deliveries.
Among them:
Demand delivery efficiency: the abscissa is time and the unit is week; the ordinate is the quantity (number) of demand; the height of the column represents the quantity of demand delivered in a week; the color distribution of the column corresponds to the length distribution of delivery cycle.
Note: According to the statistical method of demand number, there will be some statistical deviation due to the inconsistency of demand size. Therefore, it is expected to split the demand granularity relatively small and even when making demand delivery statistics.
Defect repair efficiency: the abscissa is time and the unit is week; the ordinate is the number of defects; the height of the column represents the number of defects repaired in a week; the color distribution of the column corresponds to the length distribution of the repair cycle.
When looking at the rate of requirement delivery and defect repair, we need to focus on:
1. Trends in the rate of demand delivery
Check the quantity of requirements delivered within this week and compare with the historical rate to find the gap and timely advance the planned delivery but not yet delivered requirements;
2. Understand delivery relationships in conjunction with requirements and defects
The combination of requirement delivery rate and defect repair rate can help us judge the relationship between defect repair rate and requirement delivery rate. In general, the higher the number of defects and the lower the repair speed, the lower the delivery rate of requirements. Conversely, with fewer defects and faster repair, the delivery rate of requirements will be faster.
Finally, we need to look at ** “requirements burn chart” and “defect burn chart” ** indicator cards, through which we can:
- To see the work of the project (team) over a period of time, understand the rate of delivery and the number of remaining requirements/defects;
- The completion time of the project (requirements, defects) can be predicted by the gap between the two curves and the future intersection points, which facilitates external commitment.
Among them:
Demand burning chart: the abscissa is time, and the ordinate is the quantity (number) of requirements, “Completion curve” is the change of the quantity of requirements completed by the project (team), and “Total curve” is the change of the total quantity of requirements to be completed by the project (team).
Defect igniting chart: the abscissa is time, the ordinate is the number of defects, the “Completion curve” is the change of the number of defects repaired by the project (team), and the “Total curve” is the change of the total number of defects to be repaired by the project (team);
Curve crossover: The time at which inventory requirements or defects in the project are expected to be completed at the rate of delivery over the selected time period.
When looking at the requirements and defects burning diagram, we need to focus on:
- The slope of the completed curve: The slope of the completed curve represents the team’s demand delivery rate and defect repair rate. When the slope of the curve sharply rises or drops, timely attention and follow-up should be paid to know whether the centralized delivery of requirements or defect repair occurs.
- Distance between the two curves: The distance between the two curves represents the number of pending requirements and defects, as well as the remaining workload of the project. When the distance basically changes little, it means that the completed requirements or defect repair and its new increment keep a balance. In the mode of continuous delivery, the distance should be as short as possible and the two lines increase gently.
- Intersection of the two curves: The intersection of the two curves represents the expected completion time of all requirements or defects in the project (team) at the current delivery rate. When we know this time, we can make commitments more easily.
Look at resource investment
In cloud Insight’s agile project metrics report, using the “Member Workload Ranking” and “Stock Defect Ranking by Member” indicator cards, we can:
- Look at the distribution of requirements, defects, and tasks by people;
- Look at the defects that project team members are responsible for, and the distribution of different types of defects;
When observing the distribution of project personnel, we need to focus on:
- The top three members in workload ranking: the top three members in workload ranking, we need to know whether the workload of the members is too high, whether the parallel demand is too much, etc. If there are such cases, we need to timely adjust the work arrangement of the members;
- Workload ranking of the bottom three: the workload ranking of the members is in the bottom three. We need to know whether the members have too little workload arrangement or are not responsible for the work of the current project. If this is the case, we need to adjust the work arrangement of the members.
- Top three of defects: the top three of the number of defects should be promoted to repair defects in time, and the reasons for the introduction of defects should be analyzed to avoid the recurrence of similar problems.
Overall review
We can observe the status of the project from three aspects: overall status, delivery trend and human input, focusing on five graphs:
- Project progress: reflect the overall progress of the project, and check the progress and risks of the project;
- Demand delivery rate: reflects the project’s historical demand delivery throughput and can predict future delivery capacity;
- Defect trend chart: reflects the process quality status of the team history, can analyze the team’s delivery pattern and quality status;
- Demand burning diagram: reflects the delivery rate of the project and can predict the completion time of the project plan;
- Member workload ranking: Reflects the distribution of project workload.
More data analysis is also available, such as demand trends, defect repair rates, defect burning charts, defect ranking by member, and an overview of iteration progress, which we didn’t share in this article, but can also be seen in Cloud Insight.
The original link
This article is the original content of Aliyun and shall not be reproduced without permission.