One of the mistakes that many product managers make is that they disappears after the project starts. For example, the product manager just explained the requirements to team members in the planning meeting, and then disappeared after the project started. In fact, this can cause a lot of problems, such as:

1. It is impossible to ensure that all team members understand the tasks correctly only by mere textual descriptions and planning meetings. So the product manager should track the progress of the project and solve problems in time.
2. If the product manager wasn't involved in the project process, it is easy to create a confrontation between the product manager and the development team, which is bad for the project delivery.

Therefore, the product managers should keep track of the project progress after the project starts: participate in daily stand-up meeting, understand the task progress through the project view in ZenTao, view the defects through bugs, check and confirm the requirements in time, etc.

After the development completed, the product managers should confirm the requirements in this sprint to ensure that it is what they want. They should also actively participate in the demo sessions (sprint review meeting) held by the team, listen to everyone's comments and feedback, and and record them in ZenTao.

Product managers should also actively participate in retrospective meetings to summarize experience and lessons learned in this project.