Based on our experience, we suggest to keep a couple of things in mind when being a manager on a project:



1. Know the scope: The scope of the project needs to be outlined clearly and without any ambiguity. It is of the utmost importance that requirements are stated on one master document that all stakeholders sign off on.

2. Underpromise, overdeliver: Skillful client management is all about managing expectiations. Don't promise miracles. Be as conservative and as careful as possible when making certain commitments towards the client. When you think something can be done within 1 month conservatively, tell the client it should be done within 2 months, then blow him away by delivering a thoroughly tested deliverable in 1.5 months.

3. No definite dates: Try to refrain from promising delivery on firm deadlines. Instead of "timeline", "...will be done by...", use terms like "preliminary timeline", "...should be done by...". the reason why 92% of all IT projects are late is because project managers lock themselves into unreasonable timeline.

4. First requirements, then timeline: Before you provide any timeline, the requirements need to be defined thoroughly. Don't be afraid to object timelines that have been pre-determined because some senior manager felt like he knew when the project could be completed before clarifying the scope.

5. Take the red pill: This is taken from the movie "Matrix". In other words, don't fall prey to the illusion that everything is running smoothly. Because this will never be the case. The good project manager identifies an upcoming problem and nips it in the bud as soon as possible. The longer you wait the more severe the problem will grow.

6. KISS (Keep It Simple Stupid): Don't make it unnecissarily hard on yourself. Keep the initial scope of projects as simple as possible. There will always be time for extensions and modifications later on.