Main rules of the project manager

I want to share my experience and observations, which should be adopted and the project-manager should not retreat to them every samurai . After all, it is known that the project-manager is a key figure in any project. He must interact with both the customer and the development team.

Improve your knowledge

It is impossible to know absolutely everything! There are projects for which you just need to learn from various sources. Spend more than one day at the literature and view more than one hour of interactivity, which would understand in the end what the Customer wants from you and how to convey these requirements in an understandable language to the developers.
Remember! If you only have a general idea of ​​the work of your subordinates, they will end up with either (at best) a “warden” who will always rely only on their honesty, or (at worst) a “parasite” who will be “hung noodles on the ears "the whole team and the project will, to put it mildly, be behind schedule.

Your team

Find the strengths of your team, give them the job that suits them best. Motivate your team. Help them work together. If the coder does not know AJAX technology, do not download it with this work. If the designer does not know how to make videos in flash, do not set such a task before him.

Know how to plan

Only by planning the project, you will not be knocked out of the schedule, do not overload your team with work and hand over the project on time.
')

Learn the details of all customer requirements

Without details on the terms of reference, your project may be out of date. If the Customer in the technical assignment indicates that he needs a flash-player, then find out all the details: which one, how many streams, what should he lose, and so on.

Learn from past mistakes

"Only the one who does nothing is not mistaken." We are all human and we are all wrong. Remember your mistakes, analyze them, and try not to repeat.

Radiate confidence

Believe that you are capable of more. Be sure what you are doing and what you are going to do. The confident project-manager is the one who is sure that in the remaining 2 days before the deadline he will have time to do and pass the project.

Learn to say no

You must be able to say "no" to the customer, if he demands the impossible, not according to the profile of your team, or who gets out of schedule and cost estimates.

Do not touch projects if you are not sure that you will complete them.

Delve into what the Customer wants from you and your team. If you are not sure that you will meet the deadlines with the requirements of the Customer, do not touch the project.

Do not deliberately make useless projects.

Any product (website, mobile app, interactive) will be used by the final audience. You do all the projects for her, not for the customer. If the Customer demands to make the mobile application overloaded with functionality, with no usability, hellish scary icons that his 8-year-old son drew, explain to him that this application will not be used by anyone. Thus, you will save yourself and your team from unnecessary, unclaimed long-term work and save the Client his budget.

In conclusion, I want to say that the project-manager is a key figure in most projects. Removing it from a project or replacing it will be disastrous and can put an end to many projects. During the implementation of the project, his manager should constantly be engaged in specifying the work schedule, monitoring the implementation of tasks and serve as an additional “reference tool” to the system specification, which is implemented by members of his team.