Posted on 2008-03-13 18:23
speed.zheng 阅读(959)
评论(6) 编辑 收藏 所属分类:
IT thoughts
As conflict happens in a team, project managers always attribute the reason to member's bad personality and awful communication style, they hope their subordinates or team members to actively communicate with others and appreciate their overtime work, do they really know the problems in the team?
Ironically, members always think proejct manager's awful management result in the proejct failure, all the problems seem to have nothing to do with them.When you talk with every members in team about how to manage a proejct, they seem to be clear and logical about that, and make a lot of suggestions. but the truth is when a developer runs to the top hierarchy as a manager, the situation is even more worse than his predecessor.
Leaders and members go to the opposite standpoint, accordingly, the proejct is deteriorating at a rapid pace without control. What resulted was a dysfunctional team, there is no difference between the team and a random bunch of individuals.
Why team members’ actions are not always as effective as their project manager's expectation? Why the sound of smile dies away when project manager step into member's office?
That is a big problem we must solve before the next project kicks off.
In china, most of IT project team members are driven by impractical plan with over promises, and command-control management style. Developers are working under great tension to meet the deadline which is almost impossible.Most of them are not happy with their working environment, and their morale was very low with heavy assigned tasks.
Meanwhile, some managers always look down on technical members from the heart and tend to criticize their subordinates with personal attacks in public. Technical people are reluctant to contribute their creative ideas and work to project success when they do not get their deserved respect, some of them do not share knowledge they have even if it is crucial for the project. The things is getting worse when their hard work did not get a positive response from their leaders.
Some managers try to figure out what to do to motivate our people work more effectively, but nobody think of the even more important question " what makes people lose their motivation?" .
So, when members are unable to complete their missions timely, a strained relationship was established between members and their leaders quickly, and communication gap is loomed large between them as project goes on.
Whether project manager or team members, they could not get the response from the other side, what they particularly need feedback are on things that are difficult to give.
In most cases, project failures have nothing to do with the process you adopted, whether agile or waterfall, the cause of all relationship difficulties is rooted in conflict or ambiguous expectation around roles and goals.
Project management is a very complicated activity, no one has a packaged solution for issues varies from project to project. There is no one formula for every problem. whether agile or waterfall method, if you simply follow the learning from book without sufficient experience and truly understanding about the things underneath them, you will introduce more problems and make things get worse rather than solve the existing problems.
In my view, when proejct went wrong, everyone in the team should take the responsibility. when problem happens, the team should sovle the problem mutually at the first time.