tag:blogger.com,1999:blog-13538254.post114441783652267121..comments2023-10-12T03:15:18.840-06:00Comments on PROJECTIZED: Project Reporting - 1Unknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13538254.post-1145022844977109702006-04-14T07:54:00.000-06:002006-04-14T07:54:00.000-06:00ok Yogi. Not only are your blogs really long but y...ok Yogi. Not only are your blogs really long but your comments too your blogs are really long too..:D <BR/><BR/>As a developer/designer i dont know much about PM but here's my 2 cents on what i gud project manager should be like.<BR/><BR/>1. get to know your team - their weaknesses and strengths. also get to kno them personally. however keep work out of friend ship. knowing their weaknesses and strengths wil allow u to kno when and where to use them during the project. <BR/><BR/>2. be tech savy - be familiar with the capabilities of the tools that your team is using. from sql server to visual studio. u dont have to learn to code. simple know what tool like visual studio can do. when PM gives unrealastic requirements to developers its really frustrating. also when PM isnt tech savy there's times when we can use that to our advantage. theehhee.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13538254.post-1144666465167459102006-04-10T04:54:00.000-06:002006-04-10T04:54:00.000-06:00Uhh.. Something is misunderstood here.. Any way Im...Uhh.. Something is misunderstood here.. Any way Im sorry if my explanation is not so good, You are obviously right in updating internal users about the communication problems etc. <BR/><BR/>What I meant was that …..Lets say project is 10 days behind the schedule; I have seen some PMs update the customer’s status report as the project is on target and internal report as project is 10 days behind the schedule and create a critical issue. They think they will not make the problem transparent to the customer as customer will have negative feelings, or the project owner will have negative feelings., and then they try to catch up the deadline with remaining days by Project crashing or some other way., Im saying that’s wrong. Information should be accurate.<BR/><BR/>Definitely its understood that different stakeholders have different information requirements of the project and you have to update them accordingly<BR/><BR/>Im sorry if my article mislead anybody.. Hope this will clear it<BR/><BR/>Thanks for visiting my blogThushhttps://www.blogger.com/profile/04455328122340531220noreply@blogger.comtag:blogger.com,1999:blog-13538254.post-1144595787116775532006-04-09T09:16:00.000-06:002006-04-09T09:16:00.000-06:00Thushara,One of the listeners of The Project Manag...Thushara,<BR/><BR/>One of the listeners of The Project Management Podcast has submitted a PM Status Report template, which I have made available for download at http://pmpodcast.blogspot.com (look for Show 27). It's about as simple as it gets.<BR/><BR/>However, I disagree with your statement, that you should not give different status reports for internal and external stakeholders. I have to do that at the moment. Both status reports contain the same information, but in the internal status report I also include additional information about the communication problems I am having with the external customer. This makes my management aware of any project issues that are caused by customer behaviour and that they can respond accordingly when the customer calls. To me, this is simply good communications management.Cornelius Fichtner, PMPhttps://www.blogger.com/profile/00926844407766963901noreply@blogger.com