As project leader , How can we keep abreast of the latest progress and problems of the current project , Understand the overall situation of the project ？
As a project manager , How can we follow up and promote the normal progress of the project ？
With these two questions , Let's move on to the agile project measurement scenario , Talk about how to use cloud efficiency to gain insight into the platform Insight, Help project managers find problems and deviations in time , Promote the progress of the project 、 Ensure project iteration and high-quality delivery .
notes ： The following content is divided into video version and text version , Readers can choose to learn .
Viewing address ：https://v.qq.com/x/page/i3324...
stay Cloud efficiency insight Insight in , We can 3 Follow up the operation of the project in three dimensions ：
- Look at the overall situation of the project ： Understand the project （ Or delivery team ） The overall operation of ;
- Look at project delivery trends ： Understand the rate of iterative delivery of the project 、 Quality and progress ;
- Look at the input of resources ： Understand the work distribution of team members , Ensure the input and delivery of key items in the project .
Look at the overall situation of the project
In the cloud Insight In the report of agile project measurement , adopt 「 Project progress 」 and 「 demand / Overview of defect status 」 Indicator card , We can ：
- , Such as progress 、 deviation 、 risk 、 problem 、 demand / Defect progress, etc ;
- Quickly know the demand in the selected time period 、 Defective throughput and overdue status .
picture source ： Cloud efficiency insight Insight
We can use these data , Timely follow up and solve risks and problems , If an exception is found , Can act quickly . for example , When we see too many defects in the project 、 Stock risk and overdue events , Need to quickly promote the person in charge of the project to urge , Quickly remove defects 、 Risks and overdue matters shall be solved , So as not to become a checkpoint for the final delivery of the project .
Look at project delivery trends
In the cloud Insight In the report of agile project measurement , adopt 「 Demand trends 」 and 「 Defect trends 」 Indicator card , We can ：
- Understand the needs of the project 、 Addition and completion of defects , Master the delivery mode of the team , Identify problems and risks in advance ;
- Understand the needs of the project 、 Development trend of defective stock .
picture source ： Cloud efficiency insight Insight
In observation demand 、 The trend of defects , We need to focus on ：
1. Look at the stock trend
Through the needs of the project 、 Stock trend of defects , When the stock curve goes up , It can quickly promote the timely completion of key requirements and key defects ; When the stock demand curve goes down , You need to check the demand planning , Whether the demand will be cut off . When the stock defect decreases gradually or suddenly , You need to check the quality of the demand measurement , Whether the quality is really better , It was caused by inadequate testing ;
2. Look at the delivery model of the team
If no defect is found for a long time , In a certain period of time, a large number of defects will be added , It can reflect the waterfall delivery mode , Timely intervention is needed , Avoid centralized and batch Integration , Reduce the time of problem exposure , Establish a rapid feedback mechanism .
secondly , We can observe 「 Demand delivery rate 」 and 「 Defect repair rate 」 Indicator card , Through these two indicator cards , We can ：
- See the demand delivery in every unit of time 、 Number of defects repaired , And the average unit time demand and defect delivery in the selected time period ;
- See the trend of demand delivery rate , Reasonably arrange the delivery rhythm and external commitment of the team in the future according to the recent delivery volume .
picture source ： Cloud efficiency insight Insight
among ：
Demand delivery efficiency ： The abscissa is time , In weeks , The ordinate is the number of requirements （ individual ）, The height of the column represents the quantity of delivery demand in a week , The color distribution of the column corresponds to the length distribution of the delivery cycle ;
notes ： According to the number of needs , There will be some statistical deviation due to the inconsistency of demand size , Therefore, it is expected that the demand granularity can be split relatively small and uniform when making demand delivery statistics .
Defect repair efficiency ： The abscissa is time , In weeks , The ordinate is the number of defects （ individual ）, 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 observing the demand delivery rate and defect repair rate , We need to focus on ：
1. Trends in demand delivery rates
Check the number of requirements delivered this week , And compare it with the historical rate , Gaps can be found , And timely promote the demand that is planned to be delivered but has not been delivered ;
2. Understand the delivery relationship by combining requirements and defects
The delivery rate of requirements is combined with the repair rate of defects , It can help us judge the relationship between defect repair rate and demand delivery rate . In general , The larger the number of defects and the lower the repair speed , The delivery rate of demand will also be relatively low . conversely , The number of defects is small and the repair speed is fast , The delivery rate of requirements will be faster .
Last , We need to observe 「 Demand ignition diagram 」 and 「 Defect ignition diagram 」 Indicator card , Through the ignition diagram, we can ：
- See the project （ The team ） Work results over a period of time , Understand the rate of delivery and remaining requirements / Defect quantity ;
- Through the gap and future intersection of the two curves , The project is predictable （ demand 、 defects ） The completion time of , It is convenient to make commitments to the outside world .
picture source ： Cloud efficiency insight Insight
among ：
Demand ignition diagram ： The abscissa is time , The ordinate is the number of requirements （ individual ）,“ Completion curve ” The project （ The team ） Changes in the number of requirements completed ,“ All curves ” The project （ The team ） The total number of requirements to be completed changes ;
Defect ignition diagram ： The abscissa is time , The ordinate is the number of defects （ individual ）,“ Completion curve ” The project （ The team ） Change in the number of defects repaired ,“ All curves ” The project （ The team ） The total number of defects that need to be repaired changes ;
Curve intersection ： According to the delivery rate in the selected time period , Estimated completion time of stock demand or defects in the project .
When observing the demand and defect ignition diagram , We need to focus on ：
- Finish the slope of the curve ： The slope of the completion curve represents the team's demand delivery rate and defect repair rate , When the slope of the curve rises or falls steeply , Need timely attention and follow-up , Find out if there is a situation of centralized delivery requirements or defect repair ;
- The distance between two curves ： The distance between the two curves represents the number of requirements and defects to be completed , It is also the remaining workload of the project , When the distance basically changes little, it means that the demand is completed or the defect repair is balanced with its new increment , In the mode of continuous delivery , The distance should be as short as possible and the two lines grow gently .
- The intersection of two curves ： The intersection of the two curves represents the project （ The team ） If at the current delivery rate , Estimated completion time of all requirements or defects in the project , When we know this time , We can make it easier for us to make commitments .
Look at the input of resources
In the cloud Insight In the report of agile project measurement , adopt 「 Member workload ranking 」 and 「 Stock defects are ranked by member 」 Indicator card , We can ：
- See the demand 、 Defects and tasks are distributed according to personnel ;
- Look at the defects that the project team members are responsible for , And the distribution of different types of defects ;
picture source ： Cloud efficiency insight Insight
When observing the distribution of project personnel , We need to focus on ：
- The workload ranks in the top three ： The workload of members ranks in the top , We need to know if members are overworked 、 Whether there are too many parallel requirements, etc , If so , The work arrangement of members needs to be adjusted in time ;
- The workload ranks the last three ： The workload of members ranks in the bottom , We need to know if members have too little workload , Or not responsible for the work in the current project , If so , The work arrangement of members needs to be adjusted ;
- The top three defects ： The top few people in the number of defects , It needs to be promoted to repair defects in time , At the same time, it is necessary to analyze the causes of defects , Avoid similar problems from reintroducing .
A general review
We can look at the overall situation 、 Delivery trends and human investment 3 Observe the status of the project from three aspects , Key observation 5 Amplitude map ：
- Project progress ： Reflect the overall progress of the project , You can view the progress and risks of the project ;
- Demand delivery rate ： Demand delivery throughput that reflects the history of the project , The future delivery capacity can be predicted ;
- Defect trend chart ： Reflect the process quality of the team's history , Analyze the delivery mode and quality status of the team ;
- Demand ignition diagram ： Reflect project delivery rate , It can predict the completion time of the project plan ;
- Member workload ranking ： Reflect the distribution of project workload .
At the same time, we can have more data analysis , such as ： Demand trends 、 Defect repair rate 、 Defect ignition diagram 、 Defects are ranked by member 、 Overview of iteration progress, etc , We didn't share in this article , But it can also be in the cloud effect Insight see .
Last , When following up on Agile Projects , We can also track detailed metrics of iteration progress . About the measurement content of iteration , We will share in the next article , Coming soon .
If you want to experience cloud effect Insight Agile project measurement scenario report , Click on the link below , Go to cloud effect Insight that will do 「 Free trial 」.
https://www.aliyun.com/product/yunxiao/insight?channel=yy_yc
