Project Management Process

Some customers often ask, what does a project manager do? What does the product manager do? Project management process is an inevitable skill for product managers. A project often contains many complicated processes and specific details. So how should product managers do project management? Today, We disassembled the project process and specifically analyzed what the product manager should do at each stage.

One of the most important abilities of a qualified product manager is project management. So what does the product manager need to do during the start of a project? Here is what the product manager needs to do at each stage according to the process of the project:

First of all, understand the process of project management: the first closed beta→the second closed beta→SIT internal test→UAT test→trial operation→online tracking. After understanding the process, next I will sort out the things that the product manager needs to do in each process

1. The first closed beta

At this time, it is the R&D personnel who do the product development, and the R&D personnel make a function or a module to do the test by themselves.

Of course, the project schedule is made by the R&D boss, and the time plan is made, and the product manager can ask the boss to make a time estimate at each stage to follow up the project, and after confirming that there are no bugs, it will be handed over to the tester for the second internal test. .

2. The second closed beta

The R&D staff handed over the version after the first test to the testers. The testers felt that too many bugs would hit the first time. They asked the R&D staff to rework and hand it over to the testers after the bugs were resolved.

Of course, testers can move on to the next stage after they feel that there are no bugs

3. SIT test

SIT testing is also called system integration testing, because there may be two front-ends or two back-ends separately developing different modules. When they are put together, some problems are likely to occur.

So the SIT test appeared, and at this time it was also tested by testers.

The first three phases of testing are also called company internal testing. It seems that product managers are useless, but in fact, product managers also have to participate in it, follow up and promote the project.

For example, if the R&D personnel find a problem, the product manager has to follow up the problem. If the problem is solved on the same day, you can just record it without reporting it to your boss; if the problem is not solved on the day, then you have to summarize the problem and send an email to the boss to report it.

After the test is completed, the product manager performs the acceptance. At this time, only the core functions need to be tested, and the other functions are tested by the testers. After the test is completed and confirmed that there are no bugs, you have to report to your boss. In this process, remember not to make any mistakes, and there must be no mistakes in any domain name.

4. UAT test

UAT testing is also user acceptance testing, or user acceptance testing. This stage is basically dominated by the product manager. The user will not use the product when he first gets it. At this time, the product manager needs to demonstrate in front of the user.


Don’t be alone when you are going to demonstrate. When I went to the other company for a demonstration, I found that there were more than 20 people on the other side. They didn’t ask customers to demonstrate at all. It turned into a critique meeting. At the end of the critique, your product is very likely to be Will fail.

Later, we discussed business and technology, and gathered five people together, and one or two people on the other side would be relaxed; the product manager only took care of the presentation, the customer asked the question, the technical or product manager directly dissed the other party, and completed the process easily.

Product managers mainly get feedback at this stage. After the feedback, there are two results-acceptance success and failure. After failure, it must be changed to bring users satisfaction, optimization bugs and logic errors, etc.

However, new functions cannot be added, otherwise it will be too late to go online, which will increase the workload for employees and cause the project to lose money. Of course, it will directly enter the trial operation stage after success.

5. Trial operation

Product managers are also involved in this link. When the product is online, find one or two core personnel to use it. If there is no problem, a small area of ​​users can use it to ensure that there is no problem with the product. Slowly replace the original business and eliminate the original business and use the current products.

The product manager first has to make an operation manual and train users to use it, and mainly teach the opposite person in charge to let them use and understand the product themselves.

6. Online tracking

After the product goes online, it is necessary to prepare relevant information, track the status of the online, whether there are bugs, track the opinions of customers in the process of use, whether new features are needed, and so on

Feel free to contact 56Tech at any time. Call us: 400 186 0061(China), send an email to:

#app #application #appdevelopment #appdesign #software #softwaredeveloper #mobileapplications #webapplications #applicationseason #nowacceptingapplications #onlineapplications #commercialapplications