Project delays often occur in project management. How to deal with the risks of project delays is the time to test the management level of each project manager. Many people have not summed up and thought about the delays even after working for many years.
@小竹 in our community has made a detailed and comprehensive summary of common project delays and solutions for your reference.
1. The monitoring process is not done well
1. Make a clear plan
2. Daily, weekly, monthly; irregular unannounced inspections
3. The heads of each functional group report regularly
4. Regularly arrange reasonable and effective meetings
5. Establish KPI assessment and regular review
2. Customer participants do not actively cooperate
1. Formal email notification to customers and relevant personnel, explaining the status and progress of the project, as well as possible problems
2. In order not to delay the progress of the project, list the interests and cooperation points of both parties, and prepare several alternatives for the other party to choose. Timely hold meetings and synchronize information
3. Check whether your work is in place
3. Risk prediction period is too short
1. Develop project risk response audits. When avoiding and transferring risks, risk auditors check and record the effectiveness of risk response measures. Therefore, risk audits will play a certain role in all stages of the entire life cycle of the project.
2. Periodic project assessment. The risk level and priority may change with the project life cycle, and new assessment or quantification of risks is required. Therefore, project risk assessment should be carried out regularly and should be the agenda of each project team meeting.
3. Earned value analysis, earned value analysis is an analysis tool to monitor the overall project according to the baseline plan cost. This method compares the planned work with the actual completed work to determine whether it meets the planned cost and schedule requirements. If the deviation is large , it is necessary to further identify, evaluate and quantify the risks of the project.
4. Measurement of technical factors, that is, the measurement of the difference between the technical completion during project execution and the original project plan schedule. If there is a certain degree of deviation, if the requirements specified in a certain stage are not met, it may mean that the completion of the project There are certain risks in the expected goal.
5. Additional risk response plan. If the risk is not expected, or its consequences are more severe than expected, the pre-planned response measures may not be sufficient, so it is necessary to re-examine the response measures.
6. Independent risk analysis, the risk management team outside the project office is more independent and impartial in evaluating project risks than the risk management team from the project organization.
4. Product demand changes
There are various reasons for the change of project requirements, whether it is initiated by the customer or caused by the internal reasons of the company/team, correctly understand the change, manage the expectations of relevant parties, standardize the change process, control the scope of change, and follow up the demand status and schedule impact scope after the change …all help reduce the risk of project delays and control the impact of delays.
1. Obtain real needs; communicate fully with customers. In order to facilitate customers to understand the design scheme intuitively, explanations with pictures and texts can be used. If possible, it is best to be in the customer's usage scenario, experience the pain points of the customer's use, and dig out the functions that the customer wants.
2. Replacing requirements; based on the existing logic and functions of the product, reasonably replace the requirements raised by customers and provide reasons and solutions.
3. Requirement castration; in order to achieve the best effect of the core requirements within a certain period of time, the requirements are prioritized and the requirements with lower priority are temporarily placed in the next version, using the existing resources of the system and adopting simple logic, It is easier to realize the solution, so that the cost is small and the effect is achieved. If the direction is correct, iterative optimization can be carried out in the later stage.
4. Unify the cognition of project goals ; on the premise of reaching an agreement on the overall project goals and priorities of important tasks, analyze the background and internal and external reasons of demand changes, and communicate rationally according to the established priorities and resource conditions
5. Standardize the requirements change process; combined with specific business scenarios, determine a strict and formal requirements change workflow to prevent progress delays caused by random and unnecessary requirements changes
6. Evaluate the impact of changes and update the progress; evaluate and record the impact of rework tasks and resource waste caused by demand changes, and update the schedule according to the latest demand planning
5. Preliminary evaluation deviation
1. Application for extension. After re-evaluation, submit the plan to project stakeholders for discussion, and implement it according to the new plan after reaching an agreement
2. Apply for additional resources. The customers who join this project are relatively demanding, and it is not enough to deliver within one day, so applying for additional resources is a feasible way
3. Project members work overtime. Due to the work mistakes of the project members, this method can only be implemented when other methods fail to ensure the project is delivered on time
4. Cut demand. If the project is urgent and must be put into use on time, in order to ensure on-time delivery, you can negotiate with the customer whether the xxx requirement will not be met in this period, and put it together in the next iteration
6. Insufficient team communication
Project communication runs through the entire process of information collection, management, circulation, execution, and final feedback. With the increase in project complexity and the expansion of team size, efficient communication can also use more tools and methods in addition to traditional systems such as centralized office, meetings, and weekly reports.
1. Visual tools: such as kanban boards, burndown charts, etc., help all team members to intuitively understand the project progress, task background status, responsible person, completed items and remaining working hours, etc. are clear and visible at a glance
2. Online team knowledge base: share project plans and documents, share document resources in time, and help different roles and functions quickly find answers and available experience
3. Project communication process specification and meeting system: especially the process and specification of cross-team communication, all team members implement in accordance with unified standards and specifications, reducing communication costs
4. Create a good atmosphere for teamwork: Promote daily communication between members and make them closer, making it easier to cooperate at work
7. Unreasonable progress plan
A perfect plan is meaningless if it is not tested in practice. Therefore, we need to fully consider the feasibility of the actual operation, fully mobilize the executive power of each employee, and ensure that the project schedule can be implemented well and quickly.
1. Closely monitor the progress of the project, find problems early and solve them early; use the Gantt chart tool to display the progress of certain time-related activities (tasks, stages, projects, etc.) over time, which is convenient for project managers to view intuitively Activity progress, control the overall situation: learn the situation through the Gantt chart, then check, analyze, and correct the project progress, and finally find out the cause and solution of the deviation.
2. Keep the division of tasks clear and follow up on specific matters; in the project planning stage, we must spend enough time to complete the project schedule, decompose the tasks as detailed as possible, and determine the completion time. Understand the working ability of each participating employee, and assign tasks in the progress cat Gantt chart according to the ability of project members.
3. Accurate project data analysis, real-time control of the latest situation; good project progress management is not only to ensure that the project is completed within the specified time, but also to ensure that various budgets and various consumptions are within a reasonable range, otherwise low quality and high cost There is no point in exchanging completion time.
