Views on project management within the team __ team

Within the company, basically a department responsible for a project, the project is over, the department will be reorganized. A project has a long cycle, and requires a number of departments to coordinate the completion of cooperation, such as development into application development and platform development, testing is divided into platform testing and application testing, the implementation of the engineering staff, a number of departments to work together to complete a project. Platform is a number of projects can be reused, the application of things can be partially reused, engineering data basic can not be reused. I am in the platform development, to this kind of tread project really is to experience quite deeply. Plus the current 3 projects at the same time using the platform, but also to the big head.

From the point of view of platform development, management is really a lot of problems.

Each small team has an external interface and a person who is responsible for tracking progress. Each front-end problem is communicated by the interface person to the progress follow-up person, and then to the developer. Developers have to go back to find a test, to find the project to confirm the problem exactly what happened, because platform development does not understand front-end applications, testing and engineering can not identify specific problems, but also to find application development to explain clearly, a problem to find out, it is not easy, the ease of communication too much.

The tools to record the problem are too primitive---excel, can you imagine an Excel that lists countless questions, weekly or partition time, that everyone has a problem with? Basically a day in vain, to identify the problem needs who to solve, do not have to analyze and analyze the reasons, let a person is very frustrating. After a long time, maybe the problem has been solved, you will see these problems again in TFS, let you fill in the reason .... After a few days, who will remember what was identified at that time. Even vaguely conscious that this may be a new problem.

Do not know since when, the project team to work less and fewer people, have become interface people. Are beginning to take charge of the relay. Before the development of the bad people, have become interface people, to work assignment. It would be better to say it than to do it. Too many people to me as a nanny, can feel the consciousness of team members decreased, the problem will not be as active as before, unless the nanny found someone, only to check the problem.

There are problems, are beginning to evade each other, said not their own problem, as the front-end I am very painful, basically all the problems I have to participate in the investigation, found that the last May find 80% is not my problem.

If I have the opportunity to be a project manager, I hope to avoid all the above problems.

1, flat management.

A group of managers is enough, responsible for external interface and progress follow-up. No messenger.

2, the use of unified tools to manage problems, needs

Let everyone be clear about their problems and requirements. Managers can clearly see the progress of problems and requirements.

3, does not leave the redundant position, does not leave the nanny

Multiple management leads to a decline in team motivation. Technical interface people must be able to understand the technology, otherwise there is no ability to work, and not to convince everyone.