In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-21 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/03 Report--
1. Actively communicate with customers
(1) There must be a communication strategy in the project, and how do executives report work progress and obtain support? How do the middle and middle levels continuously confirm and gradually clarify business objectives? How do you agree with the grassroots on the project application operating model for continuous improvement? All of this needs to be done through communication feedback.
The role of communication for executives is to let them know that the project has been progressing according to the goals, whether the work is progressing smoothly at each stage, what is affecting the normal operation of the project, and what resources are needed to help them. And executives communicate more, then the first advantage is that executives often listen to reports to know the extent of project progress, you can arrange feedback checks to see if there is progress in the project, so that once the recognition of the various stages of the goal, the final request for executive signature confirmation is also logical. Reporting skills to executives are concise, objective, rational and well-founded analysis of the problem, put forward countermeasures and suggestions for their decision-making.
The middle level is often the main driving force and the actual executor of the project, and is often the most important requester of specific business needs. They are the most clear about the actual operation process of the enterprise, and the most specific requirements are put forward. Moreover, it is not easy to accept the project without the consent of the middle level. Often through preliminary business research can only have a large, macro understanding of enterprise project objectives, but how to refine and ultimately implement is not a one-step process. Therefore, in the whole project process, the project teams of both sides should constantly communicate, especially the middle level communication of the enterprise, in order to gradually understand more and more profound, and finally reach an agreement.
And grass-roots communication mainly reflects the care of the end user, regular initiative and end user communication, eliminate some grievances, so that users can stick to it, this time often found that many users are really very easy to get along with, although the software has a lot of room for improvement, but once they recognize the team, but will do their best to help promote the project.
(2) At present, each project manager is generally required to fill in a detailed project monthly report during the project, reflecting the progress of the project, deviations from the plan, completed project content, input manpower, problems existing in the current project, and the expected progress of the project next month. Submit monthly progress report to department head, project management center and general manager for review.
(3) Similarly, monthly or even weekly reports for customers should be developed, and relevant information should be reflected to the responsible person of the customer side and relevant senior management. You can send emails first, and then you have to call to receive and oral brief reports, especially at the senior management level. Don't think that sending is equivalent to others going to see it. Be sure to follow up orally and report once to ensure that all aspects of the customer are responsible for the progress of the project.
2. Write memos and problem tracking records
(1)In a long project cycle, a lot of work has been done, recognized and recognized, a long time has forgotten a lot of commitments and agreements, to the acceptance of the time to turn out to re-request, this kind of thing many people may have experienced, obviously said that can not do the content of the final acceptance has become a necessary condition. Therefore, in order to successfully accept a project, a memorandum must be written to record in detail the consensus reached by both parties at important stages in the normal project process for inquiry.
(2)The project team must write a memorandum every time they work on site. The memorandum must indicate the number of days of work on site, and clearly write the content, nature and length of work according to the time period.
For example, training work should clearly write the name of the trainer, training content, training hours, training master effect;
For example, the installation work should write clearly the details of installed software, installed number, whether it can be used normally, etc.
(3)Each memorandum should be orally communicated and approved before printing and signing to determine the phased work results. The next work shall continue according to the agreement of both parties in the previous memorandum, so as to ensure the continuous progress of the project on the basis of each work, and to bind the behavior of both parties with the memorandum.
(4)The standard writing of the memorandum is to briefly report the contents of the work at the stage first, and to give positive conclusions to the previous paragraph of work or some references with positive and affirmative words, so that everyone can have confidence after reading it.
(5)This work content is often the content agreed to be solved in the previous stage, and the content solved in this on-site work should be considered in response to the work content agreed in the previous memorandum. Many people write memos purely for the sake of memos. The three major functions of memos are: the first is memos, the second is contributions, and the third is to agree on follow-up work arrangements to push things forward. Therefore, when writing a memo, we should first talk about what work we agreed on last time, whether it was completed this time, how the quality was completed, what the reasons were for not completing it, and whether it was included in the content to be solved next time. Only in this way can such a document have a system and reflect the context of a person's whole project process. Otherwise, what is the use of writing so many memos?
(6)After the conclusion comes out, the memorandum should describe the details of the work done in detail, the more detailed the better, so that the project team can recognize each other's work content and quality, and there can be an objective evaluation of the service workload. And if you find yourself spending a lot of time not communicating effectively or pushing the project forward while writing the memo, it means that the project is already out of control and should be immediately alerted and taken measures to solve it.
(7)At the end of the memorandum, the two parties shall agree on the work arrangement of the next stage. In the follow-up work, they shall design their own work plan in strict accordance with the memorandum to understand the progress of the enterprise project team. If there is any problem in the cooperation of the enterprise project team, the responsible party shall be clearly pointed out in the next memorandum to form certain pressure on the users, so as to better promote the project to move forward. Some important project objectives or acceptance opinions can be written separately in a memorandum, which can be used as a basis for final acceptance. Such a memo pushes the project forward one step at a time. Each memo has a little progress on the previous stage of work, and the final project acceptance is a matter of course.
(8)In addition to the implementation memorandum, the implementer had better make detailed records for daily work. The implementation memorandum is only a general description of the work progress, and there may be moisture. Therefore, a detailed record of daily work is needed for himself or team members to accurately grasp the pulse of the project and discover problems in time. Individuals can also review the project at any time. The user's repetition can also be recorded at any time. If there is project delay, they can also be reasonable and reasonable.
3. Carefully prepare a successful report
(1)If the project is ready for acceptance, it is generally necessary to arrange an acceptance appraisal. This appraisal may require experts to look at it, may be an internal organization of the enterprise, or may be approved by several people. Therefore, if it is to be accepted, the final appraisal of this work quality should be high.
(2)To prepare a set of demonstration environment simulating the site environment, to have enough real data, to design a set of application characteristics introduction process, to prepare a set of detailed report materials and corresponding PPT.
(3)To ensure the smooth passage of the acceptance meeting, in fact, the relevant report work and on-site application situation have been reported to the enterprise leaders before the acceptance meeting, and have been fully recognized.
Reference: How to do a good job of software project acceptance http://www.studyofnet.com/news/955.html
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.