How failing Project Managers can cause harm to team members
November 1, 2012 in General
In this post, I would like to mention a lesson. A lesson that can be useful for both project managers and software developers. Today, I know that a developer in India is died of a stroke because of the stress she has from her Project Manager. After hearing this piece of news, I felt very sad and started thinking about the environment that this pathetic developer was working in. How she was stressed from her project manager to a degree that causes her heart to stop working.
The funny thing that I know is that in the second day, the PM (Project Manager) makes the team members work until midnight and after that he told them “This is enough for today. I do not want to lose another team member”.
Looking at these words, you will find that this is an example of insanity in the software development world where such a failing PM look at team members as machines (NOT humans). He will be sorry if a team member dies before he delivers his/her work. Such PMs want to deliver the project even if all of the team members die in other words the project will be delivered on the dead bodies of the team.
What we can learn from here is, For project managers:
1. You have to plan reasonably. A developer cannot work for 16 hours daily for a month in order to deliver the project in time.
2. You have to understand the limits of the people. I know that your role is to push in order to deliver on time and with-in the budget but in the same time, you have to get the feedbacks from the team members in order to know their states. This will help you in avoiding killing people (indirectly) by PUSHING, PUSHING and PUSHING.
1. You have to discuss the plan with the project manager. Do not accept the plan as is unless it is a reasonable plan.
2. You have to push back if you find yourself flooded with the tasks. You have to discuss that all of these tasks are not possible to be done with-in the planned time, in this case, the project manager will have to re-plan in order to avoid the project slippage.
This is all what I have for this real sad story that I really wish it will never happen again in the future of the software development.