This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In some sense, a project manager is a mediator between the needs of the customer, the needs of the developers and the needs of the development company. To fill that role, integrity and great listening and communication skills are vital.
Much of the rest will depend on the culture - managing a self-organizing team needs very different skills from managing a group of people in a command-and-control structure.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Oct 23, 2002
thanks for your feedback.
I agree with you, that the "Integrator" role is very important.. as as you mention, without trust you wont be able to manage anyone.
Furthermore - I think you have a good point when you say, that there's a big difference between managing self organizing teams (Agile) and teams in a command and control structure. I guess the former is the most common in todays world*.. atleast I hope that's the case
One of the posted this question was because I was thinking about the ability to "have the big overview". Something I think is a key factor when working as a project manager. However, I couldn't quite figure out what this meant. I.e. how do you see, if someone has this "big overvirw"