tags: apache   archive   business   charity   climbing   comic   communication   database   email   exchange   family   fm2008   gk   hack   hardware   humour   linux   liverpool   microsoft   money   music   mysql   network   oes   opensource   outlook   photo   php   pictures   process   project   quote   real_life   review   rss   science   security   software   thought   tsm   updates   video   webdev   website   windows  

Project Management

Wed, 05 Nov 2008 07:10:55

Recently read an article about project managers, and here’s an example of someone who thinks he’s done his job right.

Developer says “we can do it this way to meet the timeline, but this feature won’t be available” and the project manager says “we need that feature and the deadline is immovable.” Therefore, something in the middle occurs. The product is released on schedule, but fizzles. $xx million is not realized and the project is a failure. The project manager did his job. It was released on time and within budget, so where’s the problem?

What should have happened: If something is more difficult than anticipated, the project manager should speak with the business manager and fully explain the benefits of a delay or the impact of adding the feature or function in a follow-up release.

It's easy to be an asshole and demand deadlines, but realise anyone can do this. Your true value comes from understanding the situation from everyone's perspective and the true impact on the business. Don't take the easy option, and remember the end game. There's no point finishing something on target and on budget if it means compromising the overall objective.

Read the full article here