Sixteen Words of IT Project Management

Goal-driven, system thinking, risk awareness, data quantification

Everything should be done before it is done. If you do not know where to go? It is useless to give you a map. Target drivers must first have the most basic planning and time management capabilities. For a project, all the work we do in the process is to achieve the project goal. Therefore, all activities in each stage of the project need to consider the impact on achieving the goal, rectify deviations in time. The goal-driven model enables us to change from an untargeted emergency response to a planned and purposeful advance prediction. The goal-driven process is not to discard the process. The success of the project involves the process, people, and methods and tools. In order to achieve the project goal, we should take a series of best practices that have been summarized in the past to form a set of processes based on the actual situation of the project, efficient processes and people with positive attitudes are the key to ensuring project goals are achieved. As a project manager, you must always ask yourself what is the project's goal? What is the gap between the current project status and my goal? How can I solve the problem and respond to it.

Project success is affected by many factors, and there is still a positive reaction between each factor. System thinking is to let us clearly understand the elements that affect project goals and success, and the relationships between them. A dynamic system model suitable for the project is formed. This dynamic model balances the interests of stakeholders of the project, balances the relationship between the four elements of the project, and balances the short-term and long-term interests of the project. An important capability of the project manager is to balance the project. If there is no optimal solution, there is only a satisfactory solution. If you understand the balance, you will know how to better cope with project changes and adjustments. From the optimal one-way thinking of a single element to the global thinking model of the entire system.

In short, risk awareness refers to the various problems that may occur during project implementation. I have foreseen and adopted appropriate mitigation measures, in this way, the project can be implemented according to the preset plan and objectives. Simply put, the project should not fail if the risk management is well done. The gentleman does not forget the danger, but the memory does not forget the death, the governance does not forget the chaos. The focus of risk management lies in the formation of risk awareness and the identification of key project risks through the accumulation of historical experience, enable the project to work in the fire to advance defense, so that the project can be easily followed by tension.

To talk about quantitative management, we should first train the analytical thinking of using data to speak. In software project management, the purpose of measurement is to collect and analyze various historical data, and to know the real efficiency of the project through data analysis, at the same time, it provides various estimation parameter data for subsequent projects. Speaking with data enables us to transform from subjective experience to objective data analysis on things. Only when data can be collected and analyzed can we continuously improve it. With data awareness, we need to be aware of statistics and quantitative management. Using statistical thinking and quantitative management means not only makes our process stable and controllable, able to detect fluctuations caused by special causes during project execution, analyze the root cause of special fluctuations, and take corrective actions; it also allows us to more accurately predict the degree and probability of Project achievement based on the prediction model.