[PM]-organizer role

Note: This article from http://www.cnblogs.com/Sabre/

Standing on the role of "organizer"

On the "organizer" role, what you want to consider now may be:

1. Establish a plan for each stage of the project, Gradually refine the Plan content, and establish the priority and complexity of each stage and each planning stage in the project process;

2. Establish the project or product stage objectives, accurately describe and locate the results, as well as the quality objectives of the entire project and their assessment methods;

3. Train different roles in the team to guide and coordinate their work, so as to eliminate the impact of different work habits;

4. prepare the resources required by each person. This not only changes a set of firmware into the official version or M memory into 2 GB, but also accurately evaluates his workload, and decide whether to add a Deputy (working collaboratively) to him;

5. Determine the links for review and review, and adopt a loose approach to speed up the process;

6. Get used to meetings, organize shorter and effective meetings, and establish incentive mechanisms. Of course, do not forget to make every member aware of the risks of this project;

7. Don't be optimistic.

A good project manager is not the one who does not make mistakes, but succeeds with as few failures as possible.

Whether you are a member of your team or your boss, you will not be tolerant of repeated errors and unexpected errors. --- In a team, losing the trust of the team members is more terrible than losing the trust of the boss.

It is your daily work to review every project, every stage of the project, and the details of communication with every team member.

Taken from: Thoughts of the greatest truths to simplicity-Software Engineering practitioners

On the "organizer" role, what you want to consider now may be:

1. Establish a plan for each stage of the project, Gradually refine the Plan content, and establish the priority and complexity of each stage and each planning stage in the project process;

2. Establish the project or product stage objectives, accurately describe and locate the results, as well as the quality objectives of the entire project and their assessment methods;

3. Train different roles in the team to guide and coordinate their work, so as to eliminate the impact of different work habits;

4. prepare the resources required by each person. This not only changes a set of firmware into the official version or M memory into 2 GB, but also accurately evaluates his workload, and decide whether to add a Deputy (working collaboratively) to him;

5. Determine the links for review and review, and adopt a loose approach to speed up the process;

6. Get used to meetings, organize shorter and effective meetings, and establish incentive mechanisms. Of course, do not forget to make every member aware of the risks of this project;

7. Don't be optimistic.

A good project manager is not the one who does not make mistakes, but succeeds with as few failures as possible.

Whether you are a member of your team or your boss, you will not be tolerant of repeated errors and unexpected errors. --- In a team, losing the trust of the team members is more terrible than losing the trust of the boss.

It is your daily work to review every project, every stage of the project, and the details of communication with every team member.

Taken from: Thoughts of the greatest truths to simplicity-Software Engineering practitioners