How effective the end of the project

  How effective the end of the project - a tax on the MIS system project summary of the experiences of 

  ????? "The Mythical Man-Month" at the beginning of the author Frederick P. Brooks Jr. Wrote: Prehistory, no other scene than the behemoth in the tar pits were dying and struggling even more shocking scenes .    God witnessed the dinosaurs, mammoths, saber-toothed tiger struggling in the tar.    They struggle more violent, more tight tangle of tar, there is no beast strong enough, or with sufficient skills to break free of restraints, they eventually sink to the bottom. 

  None Frederick P. Brooks Jr. Wrote the above text, we used an analogy of software projects, once started, similar to the kinds of animals struggling in the tar pits.    Excited at the beginning of the project, the excitement of the project for the rapid changes in the foreseeable future the end of the curse and despair. 
  None of the current domestic many software projects, this seems to have become a law, no matter how you do struggle, the project is not the end, and users can rely on competition patience, expected six-month project, so 18 months are common.    I also experienced the nightmare of as many projects, about how effective the end of a project to study the PMBOK, I would like to combine a recently completed tax MIS project to talk about his own views. 
  None in the PMBOK, for the stage of the project, divided into the following five sections: 
?

  None I will basically follow this five-part, described in this project is how to turn the end of the project. 
  ?????? 1, launched 
  None of the project company, we are long-time customers, customers and sales manager of a very close relationship, customers need to develop the software, we found a company directly, I, as technical director and sales manager with and , the exchange of software.    In the first contact, I feel for their own customers to be the needs of the software development is not very clear, but the client, project manager, is the director of the Center for the Inland Revenue Department's information for software development has a relatively rich experience, have taken part in the Golden Tax Project, and other large-scale software development.    This makes me feel so customers more easily exchange.    Indeed, this is also the actual situation, and after several exchanges, the project basically decided, I was appointed the company's project manager of the project for the development of the project. 
  None in this process, I would like to as a project manager, one must be clear thinking, which is the goal of the project management is to realize the objectives of the project, the end of the project.    This concept should always run through project management, therefore, in the initial exchanges and users, we will have to consider how to end the project, it needs to achieve the goal of what users can only recognition of the project's overall cost of the company for the project Is there any limitation on the development cycle, the risks of the project as a project team can withstand such. 
  None specific to this project, at the beginning, I found that the biggest risk in the project with the users feel that this project is very simple, but the demand is still rather vague, of course, this is the most common item, I admit that The project compared with the Golden Tax Project is very simple (a Golden Tax Project complex projects do not:), but if you take this kind of attitude will inevitably arise when the mad rush project development period, the late Bug everywhere, needs to change Instead, many users complain, a company sales incentives, with a research and development staff of the surgery.    Therefore, I would like to how to find a suitable opportunity to project development, as well as the difficulty of the concept of project management and communication between users. 
  ?????? I was distressed when users of the technical information they hope to conduct a staff training to keep abreast of the projects in the Java technology.    I know that the opportunity has come, and during the 10-day technical courses arrangements, I managed to find some time on a one-day project management, curriculum arrangements to users, the user, I found a little secret: specifically made a phone call to ask me on the day of project management whether it is necessary to seize this opportunity, I先给Information Center Director speakers stressing the importance of project management, as well as the difficulty of this software, the risk cycle, so that the user agreed to the request.    At the beginning of the project, access to the client, project manager of the recognition is very necessary, if your ideas and practices so that customers at the beginning of the project managers recognized that it is difficult, I think, to do with the difficulty of the project will be very large. 
  None followed by the signing of the contract and a 10-day training in, I will PMBOK concepts of project management throughout the entire training, in particular is the last item on the management of, basically achieve the expected effect, allows customers recognize that software development is not in the preparation process, which involves all aspects of the project was not a success, with the participation and it is very difficult to succeed.    The end of the project, I also made a director of the Center for Information and repeated communications, the two sides basic mutual understanding of each other's needs and ideas.    This was the smooth progress of the project has laid a good foundation. 
  None of the project through the start, I discovered that, if conditions at the time of the customer to conduct a training very conducive to the smooth progress of the project.    In the training process, and customers become friends, and their project team and the development of methods for customers seriously exchanges to allow customers recognized development team, and the training time buffer, on the one hand, can organize other technical staff for the project possible technical difficulties breakthroughs, on the other hand, can exchange programs and private demand, the demand for this kind of informal exchange often than formal exchange more easily demand that the original intention of the project initiated by a customer and client to achieve. 

  None 2, plans 
  None in the planning phase, at the beginning of the start-up phase should demand to know the general outline of the plan, with clearly defined project completion date, the plan to be submitted to the users on the one hand, on the other hand, informed the project Group members and project management company or company leaders.    Of course, here the clear end date of the general project under all circumstances and projects a far cry from the real end date (so far I have not encountered before exceptional circumstances), this does not matter, because the demand after the end of investigation, and an additional refinement project, redefined the end of the project period.    But no matter how clear, then the end of the project on schedule often from customers, companies, the pressure to make the plan always an ideal situation in accordance with the arrangements, for example, the following is my demand after the project plan: 

  ??????? This project is to the client, and the leadership of the company made under the dual pressure of that time, project managers must remain sober-minded, regardless of the plan is how much time the end of the project, and my heart must be clear actually completed and the approximate timing of the planned time gap, and that gap client whether they can bear.    Thus, in the course of the project, in accordance with the plan to gradually adjust gradually to customers and the company reported adjusted reasons, the easier to achieve both customers and companies basically satisfied with the outcome.    If the gap is too wide, the plan will argue, of course, this is a more difficult, but compared to the ultimate customer and the company was double censure, it is quite worthwhile. 
  The above plan is submitted, I estimate that the final time around the end of five weeks later than planned around major repair of the system is missing, that is, after the commencement of trial operation, users will put forward many views, two weeks time should be completed or not, However, if directly in the plan put forward seven weeks time, users absolutely unacceptable, the company also can not accept, the project may be a standstill, under pressure, I did two weeks of repair missing, then how should we do when the time comes ?    I usually practice is in the best repair for a long time after missing, first of all, the basic guarantee of trial operation on schedule, which, I believe most project teams can guarantee, and then take more in the development of on-line version of the way, as far as possible allows users to propose amendments as soon as possible, so as to secure as soon as possible revision, third, after the commencement of trial operation, user comments, timely adjustment project and to notify users, allowing users to understand when his views were adopted after the end of the project time What was postponed, to the user a certain degree of pressure can reduce the views of the early closure of projects.    Also, is possible, as far as possible, the actual estimate of the time and their own leaders in charge of communication, access to his support to ensure worry-free (this is an important point, but it depends on the relationship between you and the leadership of the:). 
  None after that, I originally estimated basic right, the end of the project some time later than the planned four weeks time around, because of the development of software for users familiar with and, if encountered relatively trouble customers, dating to the time late, but as long as there are adequate prior estimates, it would not rush. 

  None 3, the Executive 
  None relatively smooth implementation process, and customers have maintained a good relationship, the customer received the strong support of刁钻basically no problem.    In this process, a part of the beginning, we have developed in this process, we have developed some modules, as version 0.1, to the scene to carry out the installation to the user. 
  To do so, I think there are several advantages, first of all, allows users to feel the project has been ongoing, and users and does not undermine the relationship of trust and, secondly, as to understand the actual situation at the scene, if found, timely adjustment to the development direction or User adjustments site.    Again, can be part of the module allows users to propose amendments as soon as possible, in the development of the remaining modules, can be part of this revision, and the views through to other modules to reduce the time behind the revision. 
  None developed largely after the end, we have entered the scene to users for installation debugging, and then for system modifications, this is the most difficult time, at this point in time, users, companies, and project teams can easily tired, tired, anger, despair, and to all sins Doudui project manager to the head.    Therefore, at this time as a project manager in order to maintain a high degree of vigilance, we must have integrity of the project log, recording the daily progress of the users must be maintained and good communication with the project manager, to keep the problems and progress reports, and companies, to help them understand The project team every day in what to do and why the end of time would be a push再推; project team members must observe the situation, to prevent fatigue and loss of a staff; must always remind ourselves that the goal of the project is the end of the project, all of on the end of the project must be carried out. 
  None in this process, we project team has basically boil over, in my end of the expected time of the project, although there are still many areas not satisfactory, but, after all, as the project ended, everyone reduce pressure can be better sum up experience. 

  ?????? 4, control 
  None of the items in the process, there will be a wide range did not expect the problem encountered such contingencies, project managers need timely resolved. 
  None in this item in the process of development entered the most crucial moment, the technical backbone of the project team made a sudden departure, which I had not thought is prepared, if he really leave, it will be of project causing great trouble.    This time, and I had a lengthy communication to understand the reasons for his departure, and if we can retain, as far as possible to retain. 
  None After the exchange, he found to resign was based on three reasons are: First, the company's long-term dissatisfaction with the company in a longer will be a variety of dissatisfaction with the company, this is for them, despite my increase salaries and improve jobs, but it is very difficult for the company to his dissatisfaction been fundamentally resolved, and the second is the pressure of specific lives, in our treatment of the salaries of two cities very difficult to solve, such as marriage purchases of specific pressure, and he hopes to to Beijing this treatment relatively good salary, which is what we are now facing the loss of a major challenge, but this problem in the short term I am afraid that no better way, and the third is the longing for the outside world, in a two cities spent time long, so close to Beijing for the National Information Center will have longing, hope, technology, ideology, and other areas in Beijing can be raised. 
  None of these problems are widespread problem, I can not solve them altogether for him, but consider for the project, through persuasion, because we usually very good relations, he agreed to stay about a month's time, he was responsible for solving part of the technical issues, while making handover work.    This project, on the lifting of the crisis, because there are a month's time, can make good arrangements for all. 
  None for a crisis like this, I think, as a project manager, first, and usually it is necessary to pay attention to the relationship between the team members, when a variety of situations, even with out, and can help themselves to tide over the crisis; 2 For many problems, we must understand that in peacetime team members on the need, we can help resolve, to resolve, and will not wait until the time in question, it can not be resolved, and let you know the difficulties and specific environmental constraints, Do not let you guys take the company; Third, we need to bear in mind is the core of team-building team members of the personal development, to give each member of the growth of space, including technical, salaries, jobs, and so on, otherwise, once members of the team reached the pinnacle of development, it will see no future, I am afraid that separation is inevitable choice. 
??????

  None 5, ending 
  None the most difficult stage of completion?    Progress!    This time, facing the end of the project, all of the progress will be very concerned about.    How to try to persuade users to the end of the endless changes, the smooth conclusion of the project, each project manager must face. 
  None in this project, because a great deal of work early, in the run-ending, we have prepared a comprehensive document, the solution of the current Bug, and a commitment to the future, the two sides are relatively satisfied with the and smoothly signed a preliminary post-mortem report, users are made to pay the project, the end of the item. 
  None So, I think, does not depend on the successful completion stage of completion of work, but to work through completion of the project has always been, if fully prepared early, ending when the biggest conflict, progress on the project will not become Manager biggest problem, on the contrary, if the completion stage began to consider how to end the project, I am afraid that the end of the project will be put off indefinitely. 

  None of this project is in addition to routine maintenance and simple modifications, a lot of work has not, although the successful conclusion of the project, there are many incidental factors, such as the user's active support (which is rare in other projects to the general user-Baibandiaonan), but I think he still has some common characteristics of small and medium-sized projects, as a project manager, I propose to share with you our objective is to sum up experience, and can jump out of the tar pit project, smooth to the end of each item. 

  Posted on 2006-11-24 18:04 GuanHui Reading (77) Comments (0) edit their collections quoted Category: Other 

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Facebook
  • DotNetKicks
  • DZone
  • Netvouz
  • Propeller

Recommend Articles

Comments

Leave a Reply