General discussion

Locked

10 PM tripwires identified

By debate ·
Has Patrick accurately identified the 10 common tripwires you may encounter during a project, as featured in the Aug. 15 Project Management Blueprint newsletter? Which project pitfalls are missing from his list? Are there any that he discusses that you feel shouldn't be on the list?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Two extra points

by Andreas Dunker In reply to 10 PM tripwires identifie ...

11. Don't say always "yes"
Even a "premium customer" can live with a "no" if this "little new feature" delays the whole project.
12. Don't forget to ask for reasons of deadlines.
What sounds better: "This stuff has to be finished till 31.12." or "This stuff has to be finished till 31.12., 'cause the customer has announced the start of his new website" ;-)

Andreas

Collapse -

There's more...

by f-1086633 In reply to Two extra points

#13. Cost. This is #1. So many of the overseas customers I work with tell what they want done, which is usually reasonable, until they tell how much they have to do it!

#14. At the end....don't forget to get your team together over pizza and have a "Lesson's Learned" meeting. (and be prepared to take the notes yourself unless you've got a superstar that will take them down accurately! I'd suggest a tape recorder you can play back to yourself later.)

(and sometimes I wish I was 95% clear on the deliverables....sometimes it seems like we're trying to rope a wild stallion long enough to get the saddle on!)

Collapse -

10 Tripwires Feedback

by jonasson1 In reply to 10 PM tripwires identifie ...

11. You discover the requirements for the successful delivery of your project are incomplete

According to the "Chaos Report" by the Standish Group, the number 1 reason projects fail is a result of incomplete requirements. Identify and conduct interviews with all key individuals either impacted by the project or have input to the project deliverables.

To assist in this process you may want to do the following:
i) Develop interview guides that are tailored to your audience. The questions you ask the sponsor may be different than those directed to the client.
ii) Distribute the results to those who were interviewed. Ask for any changes, edits or additions.
iii) Document the findings for submission and sign off by the steering committee, stakeholders or appropriate parties.

12. You identify a component(s) to the project that are very high risk.
Communicate the identified risk component(s) to all appropriate parties. Ask for any feedback that would result in reducing the risk.Create an action plan to reduce the risk component when possible. Again, communicate your plan.

13. It's not meal time yet.
You achieve sign-off, it is now time to bring administrative closure to the project. This includes collecting and archiving all project records for future reference and re-use, analyzing project success, ensuring records reflect final specifications and documenting lessons learned. Now it's PARTY TIME!

Back to IT Employment Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums