tag:blogger.com,1999:blog-28351195.post8376437032130376419..comments2008-04-13T11:07:22.610+02:00Comments on Pawel Brodzinski on Software Project Management: 10 Qualities of Good Project ManagerPawel Brodzinskihttp://www.blogger.com/profile/04369257211504152485noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-28351195.post-47790481966776689762008-04-13T11:07:00.000+02:002008-04-13T11:07:00.000+02:002008-04-13T11:07:00.000+02:00The goal PM is trying to achieve to to complete th...The goal PM is trying to achieve to to complete the project possibly with in given constraints. As far as there's no other messages from the top of the organization he should exploit all those paths which are available and reasonable. Including those which aren't easy.<BR/><BR/>Escalation is on the list. This by the way forces people up there to make up their minds - the project is either a high-priority one or you don't get help and you know there are others more important ones.Pawel Brodzinskihttp://www.blogger.com/profile/04369257211504152485noreply@blogger.comtag:blogger.com,1999:blog-28351195.post-67539831761028360352008-04-12T21:59:00.000+02:002008-04-12T21:59:00.000+02:002008-04-12T21:59:00.000+02:00I like your point about not hesitating to escalate...I like your point about not hesitating to escalate or deliver unsavory communications. A good PM can always stay out of the line of fire if a strategic system of accountability is set up and communicated upstream and downstream throughout the organization.<BR/><BR/>Good thoughts!<BR/><BR/>Cne' BreauxJ. Cne'http://www.blogger.com/profile/16539507439160768208noreply@blogger.com