Experience after learning the theory of project management
I have been engaged in software project design and development, and it has been 15 years. There are more than 20 software projects. However, in the true sense, it is almost no comprehensive control of the project management theory, from the beginning to the project, just part of the process adopts some management philosophy and methods.
What truly understands and understanding of project management, or this time to participate in the "Training of Computer Information System Integration Project Manager". Through the theoretical training of the system, the teacher combines the actual explanation, they will contact the previous actual project management work and feel a lot.
One. The project should be managed in whole management, and the good start is good.
The entire project is started to do a good job plan. In the entire process of the project, it is always necessary to implement according to the project plan. If the project is changed, the impact analysis is to be influenced, and the change plan is developed after approved, and the change plan is executed according to the change plan. The impact of changes, such as cost, time schedule, etc. To notify the relevant project interests, explain the causes and effects of changes.
The first tail of the project is also an important job in project management. The file data generated during the project will be organized and archive; audit and review of the cost and progress of the project, test and accept the quality of the project; summarize and communicate the pros and cons of the entire process of the project.
Change plans often encounter in software projects. Controlling the change of software projects, first requiring the determination of the start target base of the project, the user needs of the baseline is clear, and it can measure what is needed. Otherwise, the changed things and the required things are mixed together, and the change plan is not from the development, and the boundary of the change is not classified.
One project you have done started to occupy the market and get the contract as soon as possible, and sign the contract with the user in the user's demand, it is not only the contract, but will not only be limited, but the time is not enough, in the project process In the middle, the user is always changed the function and requirements of the software. Because there is no base point, we think it is a change in demand and new features, and the user believes that it is a contract, and it is not possible to increase costs and time. This project started to sign the contract, we strived, in fact, the demand is not clear, so that we have been passive in the process of subsequent projects.
Therefore, the project will work from the beginning, make a clear goal. Only the objectives of the project are clear, arrange time, fees, human and other resources, control the changes in projects, which are the basic conditions that guarantee the project smoothly.
two. Project scope management theory solves the problem of unclear demand for projects
Demand Management is a problem in project management because it is actually a prerequisite for all management principles in the development process. Software development can only be carried out in a planned ordered manner if the development of the development is clearly understood and understood. In fact, there is no demand for documentation, and it is very likely that the product and requirements are deviated before and after development work. Planning, Tracking, Configuration Management, and Software Quality Assurance These principles involved in other critical processes are starting from a stable basis, that is, the demand baseline of documentation.
What is the need? Demand refers to "system requirements allocated to the software", or more simply, "allocate demand". These requirements may be technical (such as: function and performance requirements), or may be non-technical (such as: release dates, expenditure limits). It is important to distinguish between demand management and software demand analysis. Once the distribution needs are filed, and the basic work of all affected departments (customers, system engineering, software engineering), the basic work of demand management is completed, and the remaining is management changes. There is no evidence that the distribution needs itself can be very clear as a whole foundation for software development. In fact, usually they are not. Optimize and accurately describe demand, fill the vulnerability, more clearly, and the meaning of software needs analysis, the results of the analysis are called "software demand." Thus, the allocation requirements of the output of the demand management actually become the input of software requirements analysis. Demand management is far from the technical action developed by software, and software demand analysis is the first step in key development technical behavior. From the description here, the activity of demand management is simply too simple, too basic, obviously no software development organization will carry out this activity. The problem often is afraid of the transparency of the company. Customers feel that maintaining demand is unclear, loose or no official files can give them more opportunities: "That is not what I want, that is not what I think." Document clear demand may force users to start change in the case where the system meets the needs of documentation but does not meet the actual needs. Similarly, developers feel that they can give them a bigger room for them to give them a bigger room, allowing them to be as close as possible to budget and progress, and then say: "This is what we think is the meaning of the needs. If you need anything else, you must pay an additional price. "Clear demand for documentation will force developers to assume obligations to meet these needs and make them exposed to spending, and evaluate inaccurate risk. In this way, although the customer's interests of the developers are relatively, they come together. Every party believes that they are protecting their own interests, consolidating their bangs, but in fact, everyone is going to future disappointment and quarrel, buried a bomb for the project.
three. Project Time Management Theory Guide us how to grasp the main contradiction in project management
In the past, the project management is based on the work characteristics of experience and everyone. The software project is basically based on demand analysis, summary design, detailed design, code programming, debugging and testing, user acceptance, etc. Come. However, it is more refined to divide the project, how much is the time estimation of each small process, how much time it can be used for the entire project, how to arrange personnel, how to grasp key links in the project, etc. These have not been quantified. Analysis and management.
The implementation of project management is the most intuitive to shorten project time. With project management theory, methods, there are many examples of shortening time. When the US Louisvian plant is maintained, the maintenance process is finely decomposed, and the control relationship is established according to the guide. They were surprised to find that there is different time when the maintenance process chooses different paths. By repeating the task on the longest path, the construction period is repeatedly optimized. Finally, only 78 hours will complete the maintenance of 125 hours to complete, saving time 38%. That is, the project management worker is still applying the famous time management technology CPM, ie "Key Path Law".
Therefore, in the project management of the software, we should also use the time control theory, combined with the reality of the software engineering, and make the task decomposition, and use the network map to build the entire work process, estimate the last stage, find A critical path, and shorten the duration of the critical path through a quick follow-up method to improve the efficiency. four. Quality management is the key to success or failure
In the process of software project, the function test of the software has always been considered to be more serious and strict. Each test must have a test plan and use case writing, and then can test; test must be recorded, and will be recorded into testing report.
But after this training, it feels that our test work and quality management is far from the distance. Quality control should go deep into each process related to the project. In every process of the project, from the beginning, we must establish the quality first concept, each process must perform quality control, not the most When testing, you think of quality, you will measure whether it meets the standard.
Standardization design, standardized management is the guarantee of project quality. Participating in quality system certification helps companies improve project management level, which is conducive to improving the quality of engineering projects. The CMM model has been widely recognized and accepted, and CMMI has 5 levels and 18 elements along its model. Through 5 certifications and strengthen management, companies' management of the project will have improved by 5 realms: from chaos, to milestones, to define the clear management system and standard, to the statistical process control quantitative management, to the end Optimization process, evaluation workflow, improvement of work processes.
I have participated in the design and programming of some functions for Japanese software. Japan's software companies are more meticulous to quality control of a project, using our conceptual measurement is not tolerable. To make a detailed design of a module, use the standard graphical language they provide to describe the standard design touch; Evaluate until it can be opened to design a code. After the code is written, it is not the result of seeing the result. It is necessary to print the code. Make the code assembly.
At that time, it was considered that the method of Japan was too wasteful, and the ability of the technical personnel's personal ability is too low, how can improve work efficiency. However, there is frequent software quality problems, which is our constant recognition that starts to waste some time and manpower, control the quality of each detail, which is to save new time and human expenditures for solving quality problems. . I save a lot of software in the later quality maintenance costs. Overall is the accounting. In order to improve the quality of the project, reduce costs, you must do quality control work from the beginning of the project.
Fives. The use of some strategies in communication management can make the project better completion
Doing a project requires contact with customers, there will be some formal and informal negotiations. Both sides will bargain for their own interests. Doing communication with customers, whether the project progresses smoothly. There are many strategies in communication in the actual work of us, and the purpose is not to pit, but in order to better complete the project, some of the art tools adopted by the two sides. Communication techniques include: the final deadline, use the surprise method, using a limited rights law, non-exposed person, fair and reasonable, strategic delay, two parties, and retreat, unreasonable, both true. I am a successful adoption of strategic delay, and a project quality of the client is timely promptly promptly. There are still a lot of experience, in short, through this study, I have a new understanding of the management of the project, I will use these theoretical knowledge to actual work. To improve the management level of the project, improve the quality of the project, reduce the cost of the project, reduce the risk of the project, and ultimately improve the efficiency of the company.
