Project Management Process for a Product Manager

Image Source: Unsplash

One of the most important competencies of a great product manager is project management. So what does a product manager need to do during the start of a project? Then, let me talk about what a product manager needs to do at each stage according to the process of the project:

First of all, let's understand the process of project management, the 1st internal test → the 2nd internal test → SIT internal test → UAT test → trial operation → online tracking. After understanding the process, I will sort out what the product manager needs to do in each process.

1. The 1st Internal Test

At this time, the R&D staff carries out product R&D, and the R&D staff makes a function or a module to test by themselves.

Of course, the project schedule is made by the R&D leader, who is responsible for making the time plan. At each stage, the product manager can ask the leader to make a time estimate to follow up on the project. After confirming that there are no bugs, the project schedule will be handed over to the tester for the second internal test.

2. The 2nd Internal Test

The R&D staff hand over the version after the first test to the tester. If the tester finds too many bugs, they will ask the R&D staff to conduct the first internal test again. When they solve the bug, they will hand it back to the tester.

Of course, the tester can move to the next stage after finding no bugs.

3. SIT Internal Test

SIT testing is also called system integration testing, perhaps two front-ends or two back-ends develop different modules separately, so there is a high probability that some problems will occur when they are aggregated together.

Therefore, the SIT test appears, which is also checked by testers.

The first three testing stages are also called company internal testing. The product manager does not play a role, but the product manager is also required to participate in, follow up and promote the project.

For example, if the R&D staff finds a problem, the product manager must follow up on the problem. If the problem is solved on that day, they can record it without reporting it to their superiors; If the problem is not solved on that day, you should summarize it and report it to your boss by email.

After the test is completed, the product manager will conduct the acceptance. At this time, the product manager only needs to test the core functions, and the testers will test other functions. After the test is completed and it is confirmed that there are no bugs, the product manager must report it to the boss. Remember to avoid making any mistakes in this process; there can be no mistakes in any domain name.

When you report in front of the boss, the domain name is wrong, and the boss denies your professionalism. Our treatment of users is also the same attitude, and any port error will cause users to eliminate your product.

4. UAT Test

UAT test means user acceptance test or user Acceptability test. The product manager dominates this stage. The user will not use the product at the beginning. At this time, the product manager must demonstrate in front of the user.

It would help if you were not alone when you go to the user's place to demonstrate. I once went to another company to demonstrate and found about 20 people on the opposite side. They did not call the customer demonstration but turned it into a criticism meeting. At the end of the criticism, There is a great chance that your product will fail.

Later we discussed with the business and technical staff so that we had five people together, and it was easy when there were only one or two people on the other side; the product manager was responsible for the demonstration, the customer asked questions, and the technical or product manager was responsible for answering the questions so that the process could be completed easily.

At this stage, the product manager mainly needs to get feedback. After feedback, there are two results - successful acceptance and failure. After failure, the product manager has to correct and optimize bugs and logic errors until the user is satisfied.

However, new functions cannot be added. Otherwise, it will be too late to go online, which will increase the workload of employees and lead to a loss of the project. Of course, after success, the project will directly enter the trial operation stage.

5. Trial Operation

The product manager is also involved in this link. After the product is launched, we will find one or two core personnel to use the product. If they think there is no problem, they will let small users use the product to ensure no problem. Then the current products gradually replace the original business.

The product manager must prepare an operation manual to train users to use it. The main task is to teach the person in charge to let them use it and understand the product by themselves.

6. Online Tracking

After the product goes online, you should prepare relevant materials and a real outsourcing project to earn money through after-sales service.

You should serve the other company at a later stage. They will look for you in the future for any small needs or small features, and they can find you if they have any after-sales problems with the software sold to them. The other company will directly pay after-sales fees, so this product makes money in terms of after-sales.

On the other hand, you can also make money by launching new functions of products, and updating products is also a way to make money.

------

Need more help? Check out the Zentao blog. They have more articles on project management tools, software management, building cross-functional teams, and so much more.