Chris Croft
Tips of the Month Archive

Project Management Tip 14


Blow your own trumpet

Be assertive at the start

What is a Gantt Chart?

Avoiding people problems

Listing all the tasks

Internal projects

How to discover the key project driver

Three methods of project costing

Why I love Gantt charts

Three ways to handle uncertainty

Overspend or underspend?

Why PM is difficult

My instant guide

Why review?

Some eccentric PM abbreviations

What exactly is a PID?

Its never too late to plan

Why PM is good

Good questions to ask a project manager

Just a reminder to review all your projects when they finish, regardless of whether they went well or not.

Reasons to not review a good project:

"It went well so we don't need to"

"We'll be able to remember it when we do it again next time"

"Why should we give away our hard-won information to other people?"

I think you can see the flaws in all of these....!

Four good reasons to review a project that went well:

1. To be able to repeat it next time.
2. So that others can do the same.
3. To think about how we could do it even better next time (hindsight is a wonderful thing, so why not use it).
4. To celebrate and thank the team. Go on, have a pizza!

Onwards and upwards


visit and have tips like this one sent to you free by email once a month - they never repeat!