This "target" can be the date when the project passes the package test or the date when it is released online, but the whole team must reach an agreement. If it is online, colleagues in charge of the market may need to participate.
Step 2 make a plan-make a clear plan
According to the first point, the goal is defined, so the project members can start to make plans, or the product manager can make plans, which generally include several key checkpoints:
Demand document output time node
Interactive document output node
Visual manuscript output node
Dependent external interface provider node
Developing sending and measuring nodes
Functional test completion node
Total regression test completion node
These seven checkpoints can be increased or decreased according to time. Some people may ask, what is the purpose of defining this plan?
Assess risk
Then after making the plan, each member of the project will decide what to do, how to do it and when to finish it according to the plan. This step is particularly important in multi-person cross-team projects. It can be said that this step is good and the project process will be very smooth in the future.
Let's randomly list the pits we stepped on: Project A didn't have interactive documents at first, and the ERD/ test cases developed all relied on interactive documents;
It is really wrong to rely on the interface (other departments) to directly say that there is no timetable for the time being, or that it will be provided in 3-4 weeks;
Development time is too late to test, resulting in insufficient test time. After each member performs the plan evaluation, the project may light yellow. Is there anything the product manager can do?
4. Coordinate resources/modify plans
According to the urgency of the project and the importance of the superior, coordinate various resources in time, optimize the progress and modify the plan.
123 may be repeated at this time. There will be fewer problems, the process will become more transparent, and the progress will be visually controllable. Are you embarrassed?
connect
In dealing with people, you can't rely on emotional intelligence first, skill second, but on beauty ~ well, get to the point.
1 communication skills
Why do you need to master communication skills? When there are more than a dozen people in the team, you may meet "colleagues" of various personalities, so be prepared.
Step 1: Know yourself and yourself, and understand the personality and work habits of everyone in the team.
Step 2: Deal with a man as he deals with you. Deal with designers who are open-minded and active, with programmers who are quiet and focused on technology, with meticulous and rigorous tests, with colleagues who don't cooperate with other departments, and try to reach an agreement quickly in a way acceptable to each other. You did a good job.
2. Communication efficiency
What is efficiency is to reduce unnecessary communication. How come?
If you can face to face, don't call; If you can make a phone call, don't QQ/RTX/LYNC. Text communication will inevitably have different understandings, leading to digging holes; Briefly state my problems in person, the support I need, and when and when to get feedback in time.
Never trust verbal promises, never! After offline phone call or face-to-face communication, be sure to send an email to explain clearly and get confirmation from the other party. E-mail is really useful sometimes.
Someone must understand the pain of the meeting. Try to choose a fragmented time for the meeting, such as 9:30, 13:30, 5: 00, so as not to always feel "Oh, I have a meeting later" and always be in a working state affected by the meeting.
In order to avoid a large-scale discussion in the meeting, you can write down the questions and discuss them in detail after the meeting; Pay attention to control the progress of the meeting, of course, chat occasionally, but pay attention to control the duration and try to get it done within the planned time.
Implementation ability
The execution mentioned here can be understood as improving the execution of the team.
No matter how good the plan is, no matter how good the communication is, no matter how bad the execution is, it's all floating clouds ... As for the method, we can start from the following aspects:
1. Timely response in daily work;
2. Everything has a node to feed back the progress;
3. Efficient driving force, the things you are responsible for can promote solution and follow-up;
4. It is very important that the output should be of high quality, including various documents, delivery quality and test quality. Let's talk about it separately later ~
5. Keep forging ahead, not just one project, but one project after another, and the product experience can range from 0 to 1, so as to carry out effective project management.
Hongbo Chuangxin Product Manager Boutique Course
Content Source Hongbo Innovation Management Consulting
I hope we can bring useful knowledge and information to more people.