We must learn to learn from the project failure, as long as we can have a big mind to face it, then make mistakes are not a bad thing.
.
In fact, the factors affecting our project failure are mainly divided into
Technology failed:
1, the temptation of leading technology
2, imperfect technical design
3. Provide technical solutions for non-technical issues
4, dependent on the package to meet the needs
5. There is no best use in the development of life cycle.
6, development with technology-oriented
Artificial failure:
1. Lack of support for administrative staff
2, lack of leadership
3. Project team without dedication
4, project team with insufficient function
5. Management third party failed
6, missing a project elite
7, missing project ownership
8, related personnel conflict
9, refuse to change
10, hostile organizational culture
11, experience insufficient project manager
12, lack of business reasons
13, unclear or ambiguous business priority
14, missing user training
15. The relevant personnel are not consistent
Process failed:
1. Lack of project management method system
2, lack of system development method system
3, lack of income management method system
4, lack of quality management method system
5, failure to determine and transfer project risk
6, failure to manage demand
7, too long project schedule
8, insufficient testing
9. Computerized "explosion" method
Subsing the lesson from the project failure is an important part of the continuous improvement process. Now there are some main lessons lessons 1, manage users expect. That is, our project staff should understand what you need to deliver from the beginning and what you want to deliver. To determine the user's needs and establish as clear commercial ownership in the project. Even in the best case, the information previously received is limited. Normally, it is difficult to determine suitable users with feedback information. In the beginning of the project, you need to determine the main user needs and provide time for the primary user so that they determine the needs of the department, and they also have the responsibility to provide and verify information and put the corresponding resources. 2. Business requirements and user needs must be considered in the project specifications. First, we must clarify two concepts. First, the project is due to determinable and measurable business requirements. The clear goal determined in the initial period of the software project will gradually become blurred as the project progresses, which is the characteristics of the project with too long delivery. Therefore, before the project begins, it is necessary to determine the end user to fully consider their needs during the design and development of the software project, while the user is responsible and needs to take corresponding actions to help the project have succeeded. This is very important. Users need to form a crucial link in the analysis and design phase of the project. After the demand is determined, the baseline is determined for these needs, and they are introduced into the configuration management system, while the change control is managed. If these requirements have changed or add new demands, the project needs to be influenced and the project plan is corrected. And some organizations that use incremental and iterative methods development software, they also need to freeze the needs of each software version, and establish a corresponding mechanism (version control in the determined time points and function points, detail, for example, project Version control can specifically build a folder for version control, then sear with the update file of this folder every day, and make the full path to the full path to update the full path to the full path), so that The development baseline adds a new need for higher priority requirements (determined priority in user demand feedback). Second, the project specifications must focus on business needs rather than technical solutions. Therefore, even if there is a clear solution from technology, it is still necessary to focus on the business-related aspects when performing an item review. 3. Measure and evaluate the scale and complexity of the project before approved resources (pay attention to implementation). The development of technical strength has brought a unfortunate consequence to let us believe that many of the past it impossible now can not only be achieved, but it can be realized easily. Sometimes this idea is usually exaggerated in the early stages of the project to exaggerate the potential benefits of the project, too large project scope definitions and excessive optimism is quite dangerous and is not detailed enough. Therefore, we need to be clearly determined: a, the proposed project schedule is actively feasible; b, the commercial case of the project is feasible; C, the solution is technical in technology; the size and complexity of the software project is the success of the project A decisive factor. 4. The introduction of software projects will inevitably bring a wide variety of changes. The new technologies have a lot of influence on the role and responsibility of new technicians, and it is easy to lead to unclear procedures and responsibilities. Therefore, in the project plan, it is important to ensure that employees know how to use and maintain systems is critical. There is no reasonable training is the whole potential income that will never achieve software investment. More importantly, lack of training may bring business risks and operational risks, which may eventually threaten the long-term availability of the project. 5. Clearly visible project management structure is critical to the project. There must be clear roles, responsibilities, and obligations in the management structure.
The formal report structure and the channels of communicating with advanced management should be determined in the beginning of the project, while maintaining the entire process of the project. 6, first handling good people's problems, never forget, talent is the only most important factor in the success of the project. The staffing plan must be carried out simultaneously with the project management framework in the organization to provide training, performance evaluation, dispatch work and position promotion. (Haha, everyone hopes that the project team is a high degree of initiative and skilled skills. Risk treatments and changes are important forces to improve competitive advantages, but to a large extent, it is still in order to organize cultural encouragement and support. Of course, the project also responds to some functional modules that affect project progress and re-examine risk analysis work (and subsequent risk management work) to reassess and adjust the plan. 8. After the start of the feasibility project of the project, it is critical to monitor the success of the project. The impact of changes may result in the initial investment assessment. Therefore, the business case should be a continuous reference in the project process. If the project that is considered an investment cannot achieve the expected income, it should not hesitate to terminate the project. Once the decision to terminate the project is made, do not turn this process into a lengthy and trouble process. Abandon the project and continue to advance, make sure we can learn useful experience from this process. A key factor that leads to high costs that failure projects is often because the process of the termination project itself is too lengthy. 9. Management of external suppliers should pay more attention to the supplier's quality management system to ensure that these systems are valid and assessing in existing quality systems. Excessive relying on the guarantee of the contractor's delivery capacity, or ignores the participation of the contractor when the project encounters problems, will bring huge risks. The most important experience is that you must establish intimate relationship with suppliers, but don't dependence on them. Whenever, customers must retain their ownership of the project and its processes. That is, we must evaluate the capacity and financial position of external suppliers, regarding it as part of the acquisition and performance process. 10. It is not cheap to introduce quality systems for quality investment. But in the long run, the failure of quality investment will seriously affect the return on investment in the entire project. The lack of testing and defective preventive measures are still one of the main causes of project failure. 11. Always preparing an emergency plan risk management process is the basis of determining and managing the risks in the project. Therefore, business and IT related personnel must develop emergency programs to take measures when they do not deliver. 12. Ensure that senior management is involved in the entire project process for IT projects, should be considered commercial decisions rather than technical decisions, and fully support for advanced management. Advanced management must take responsibility and control and track the project. 13. The project must have a single and powerful owner that must have a successful responsible owner, especially when multi-party will be the same as a established income from project outcomes. In the entire project, many compromises have been made to meet the will of everyone, and the result is that no will have anyone's will. 14. Ensuring that the process used by all new software development projects is at least in accordance with the requirements of CMM level 2 as the minimum standard, the process used in the project must support the basic requirements of configuration management, demand management, software quality assurance, and project plan. Don't rely on the professionalism and expertise of the development of the delivery project, once they leave, your project will be affected. 15. The consequences of the review and release of the evaluation of the evaluation of the evaluation of the review have not been implemented: organization (more specifically, personal) Abandon the opportunity to learn from the wrong lesson. The purpose of the review is to determine the extent to which the project is satisfied with the business goals. Therefore, the scope of the review should cover all aspects of the project: business goals, users expect, user satisfaction, forecasting benefits, technical needs, supplier management, and quality assurance.
