Needs to change the form of many, such as temporary boss to change mind, the project budget increase or decrease in customer demand for features and changes. In IT projects, change may come from program service providers, customers or suppliers, etc., may also come from within the project team. Although the demand for change forms vary, but nothing more than study the underlying causes of the following:
1. Needs to change because of
(1), there is no delineation began thinning
Detailed work is done by the staff requirement analysis, generally based on user submitted descriptive summary of just a few words to refine, and extract a functional, and gives descriptions (normal execution time description and a description of the accident). When refined to a certain degree and begin system design, the scope will change, that details of the use case description may have a lot to change. If the original data is manually add people to change calculated based information systems, and the original description of a property to become an entity so described.
(2) do not specify the baseline demand
The baseline demand is the demand for change is to allow the line. As the project progressed, the baseline demand is also changing. Whether to allow the change is based on contracts and the impact on costs, such as the overall structure of the software has been designed out of the scope of needs is Bu permit amendment, the Yin Wei overall structure Kuaiduizhengge project schedule and costs are the initial budget. As the project progressed, the baseline will be higher the more (the change will allow the less), the process is as follows: Comparison of baseline change requests à à change to achieve.
(3) without a good software architecture to adapt to change
Component-based software architecture is to provide a rapid adaptation to changes in demand architecture, the data layer encapsulates the data logic between visits, business layer encapsulates the business logic, presentation logic layer show the user. However, adaptation must follow some principles of loose coupling, or some contact between the layers, the design of interfaces to minimize the entrance of parameters will be changed. Well, if the business logic package, then the interface layer arrangement or reduce some of the information requested is very easy to adapt. If the interface definition was reasonable, even if there are changes in business processes, and can quickly adapt to change. Therefore, the cost impact to the extent permitted baseline can reduce demand, improve customer satisfaction.
2. How to control the demand for change
According to the modern project management concepts into the life cycle of a project started, implementation, ending three processes. Requirements change control implementation of the project should not only consider the matter, but to spread throughout the whole process of project life cycle. In order to change the project to minimize the impact on the need for an integrated change control. Integrated change control to identify the main contents of the factors that affect the project changes, determine whether the scope of the project changes have occurred so.
Comprehensive change control based primarily on the project plan, change requests and provide information about the status of project implementation performance reporting. To ensure the project specifications and the effective implementation of change, usually there will be a project organization
(1) Project start-up phase of the change to prevent
For any project, changes are inevitable, and no escape, can only be a positive response, this response should be to start from the needs analysis phase of the project began. Doing very well on a needs analysis project, the base document defines the scope of the more detailed and clear, the user with the project manager, the less the guise of passing the buck. If demand did not do a good job, reference documents in the scope of ambiguity, be customer seize the loopholes, often have to pay a lot of unnecessary expense. If the demand well, the document signed by clear and there are customers, then later changes made by the customer beyond the scope of the contract would require additional fees. This time must not be soft, this is not to deliberately make our customers money, but can not allow customers to develop the habit of frequent changes, or no end of trouble. Relative to demand, what WBS, risk management, progress of the project are minor, as long as the demand will make a smooth.
(2) the needs of the project implementation phase change
Successful projects and unsuccessful projects lies in the difference between whether the whole process of the project is manageable. Project manager should establish a concept - "the demand change is inevitable, controllable and useful." Project implementation phase of change control needs to do is to analyze the change request, assess the potential risk to change and modify the base file. Gradient control needs to note the following:
Requirements must be associated with the input, if the demand side to change the cost borne by the developer, the project has become an inevitable demand for a change. Therefore, in the beginning of the project, both funded the development of party or parties must be clear about this one: Requirements change, software development inputs have changed.
Changes in demand for recognition of donors to go through, so will demand changes to the concept of cost can be prudent to deal with demand changes.
The demand for small change is also subject to formal requirements management process, otherwise it will add up. In practice, people often do not want the demand for small change to the implementation of formal demand management process that reduces the efficiency of development and a waste of time. But precisely because of this concept needs only to gradually become uncontrollable, leading to project failure.
Precise definition of the needs and scope of change will not stop the demand. The definition of needs is not the more detailed, more needs to avoid gradient, which is two dimensions. Requirements definition is too thin gradient have no effect on demand. Because the demand for change is eternal, not requirement was dropped, it will not be changed.
Attention to communication skills. The actual situation is that users, developers aware of the problems between the points above, but as demand for change may come from client side, it may come from the development side, so as demand Guan Lizhe, project managers need to adopt a variety of communication skills parties get what they want to make the project.
(3) a summary of the project closeout phase
Capabilities are often not come from successful experience, but from failures in the past. Many project managers do not pay attention to lessons learned and accumulated, even in the course of the project ending up badly beaten, he can just complain about luck, the environment and the teamwork is not good, very little systematic analysis of the sum, or do not know how to analyze and summarize, so the same problem recurring.
In fact, the project should be concluded as the existing continuous improvement project or future projects an important part of the work, but also as the project contract, design the content and target identification and validation. Project summary work includes projects in the pre-identified risks and did not anticipate the changes that occurred in response to measures such as risk analysis and summary, including projects and project changes that occurred in the analysis of problems in the statistical summary.
3. Demand change processes
Requirements change as inevitable, then it must be a standard process flow. To demand change processes should be divided into the following steps: assessment of proposed changes to change à à implement change. The following diagram briefly describes the general demand for change processes:
Requirements change processes
Because the real world software system may have different rigor and complexity, so all relevant demand predicted in advance is impossible. System was to change the operating environment, user needs will change, and even the role of the system may also change. Implement and test the system behavior may result in problems being a new understanding and insight, this new understanding of the demand is likely to lead to change. CMM that "the demand distribution changes were reviewed, and added to the software projects to", the key yes 在 demand occurring changes, no need to immediately put in Ba Zhexie change into software development. In fact, adhere to the requirements change into development efforts, the business will create a chaotic and unstable atmosphere, which would seriously undermine the control and management of the project. Requirements Management key process of trying to change the distribution of demand for hoarding to a manageable group, until the development work to allow time to re-introduce the appropriate way to avoid this confusion in the atmosphere. A result, demand management has created a separation development work with all real, potential disorder, the change from customers. This buffer allows the real changes are noted, recorded, tracked, and development work it will not be disturbed. Development projects should be updated periodically to absorb the demand for suspension of accumulated changes, this time, all the planning, design, behavior changes according to the needs of just absorbing the impact to be updated.
Demand for change of control of course and scope of project management is closely related to other than purely technical factors, such as object-oriented analysis, object-oriented design, object-oriented coding and so on. However, all technology of Fazhan trends are is always the same in order to make Biangeng for easy management and, therefore, whether in the project change Kongzhi the action taken strategy, the project itself, the Bianhua insight must always, everywhere Liu Yi, Zhiyouzheyang can we truly be well on the project change control.