It's really difficult for a Project Manager-Role Orientation of POBO Kan Project

[Editor's note] This article is a series of "bobo Kan Project" Article The second article aims to give a brief summary of my work over the past year based on what I have seen and thought as a project leader for more than a year, I also want to share the happiness or unhappiness with you. I hope you will not be able to give me any comments on new ideas.

What do I feel when I become a project manager for the first time? It seems that the prawns who have been through the sandground have long been forgotten, but I still remember the dishes that have just brought a project. It was an afternoon without rain. In Maitreya, there were no ceremonies (haha, there were generally no ceremonies), and there was not much encouragement, only the department manager said, "The HR system is handed over to you." First, I was excited, and finally I had to undertake a project independently, a "my" project, from an early age, Confucius was influenced by the idea of "coming out and getting ready", and he had no disguise ability for his vanity. He was so proud to accept the task. In addition to excitement, the depth of the heart also passes through a trace of sorrow.

Young people have never been procrastinating in their work. Over the past few years, they have started planning the project right away. Maybe the project is too busy, maybe it is the vanity of the invitation, after three days, I tried to implement the design in a hurry. Fortunately, the manager did not allow me to design rashly and rework several times, the outline design task was barely completed. I have written a good document. I never deny this (at least in terms of format, I am not afraid of making bricks, huh, huh), but it seems that all developers prefer to use it early. Code To express my thoughts, of course, I am no exception. After a simple idea, the code was quickly started. When writing and thinking, mistakes are inevitable. I remember that sometimes I found out that the design was wrong after I finished writing the project, and then I tried it again. After several times, I finally got it done. I looked up the table and slept for two hours at a.m, I went on to work and woke up watching the code I wrote yesterday. It was wrong again.

Think twice, reflect on it, and understand the first principle: the project manager should be calm.

I adjusted myself a little, but now I am about to go to deadline at this stage of the project. I am working overtime and working on it. I am very happy to see everything I need. Program The answer is "We don't want this ". Although there were preparations for demand changes in the past, big changes still seem a bit unacceptable to the heart. Re-research, re-development, and plunged into how to implement the user-provided reports. The results were originally set to the first stage of the end of May, which was dragged to September, when the boss asked about the project progress and the causes of project lag, he suddenly discovered that some reports were originally unnecessary for computers, but he simply accepted users' needs, but I haven't sat down with the user for a long time and talked face to face.

After the incident, I understood the second principle: the project manager should communicate with each other.

After the salary system was basically stable, the system barely entered the second stage of human resources system development-performance appraisal stage, drawing on the failure experience of the first stage, and determined that the design of the project team should be stable, it took up to one month to implement business learning and business design. I submitted a request review with joy, but the results were approved by the user. The object was unclear and the purpose was unclear. I did not consider the demand from the user's perspective. After many thoughts and reflections, the second review barely passed.

After the review, I took out my own project manager's note and wrote a few big words: the project manager needs to think and think more than others.

In November March, the performance appraisal module was developed, tested, and reviewed. He once again came to Honghe with confidence, seeing the customer's leadership, we are planning to "show off" the flexibility and configurability of our performance appraisal. If we haven't spoken, we will be rejected, in the past, the Performance Appraisal they wanted was far less complex than ours, but why was the 360-level and three-dimensional appraisal required by the first time? The customer information center Director's statement broke the mystery: "performance appraisal is a topic that everyone is still discussing. Everyone may have a set of performance appraisal implementation solutions, when no specific business process is supported, you should first develop other modules according to the contract." I don't know why the company gave priority to the performance appraisal module to the second stage. However, I did not ask and negotiate the development plan as a project manager.

The fourth principle is to coordinate the project manager.

We are about to enter the third stage of the human resources system, including some functions, training, examinations, recruitment, and learning. for development, it can be bigger, smaller, and the development cost will be different, in particular, when a partner is transferred to the cigarette group, the new employee's infamiliarity will directly affect the project progress. What to do, what to do, what to focus on, and what to weaken are all things that the project manager needs to pay attention to and consider. I remember Wu Chengjun joked that he was a "perfect man". It may be feasible for technology. However, for me, a project manager is indeed a "perfect" route.

fifth principle: project managers must weigh the cost.

after sharing so many experiences, let's go back to theory. What is a project manager? Let's review the definition of the project in the first project, which was so simple: "A Project is a one-time task associated with each other for a certain purpose under the constraints of established resources and requirements." The Project Manager can reasonably arrange "established resources", understand project constraints, and target people who meet task requirements, it is sufficient to understand and carry forward the "Five Principles" I have learned.

after positioning, what details need to be managed in the project? Please refer to the third article "one inch of time and one inch of money-time management of project management" of Bobo Kan project.