Managing the TBT project
morning after the night before
THE CLOSING PHASES of projects tend to be the most frantic and the most tiring. When the product has gone out to the client and all is quiet on the Western front, its nice to enjoy a period of relative calm, with no more problems to solve and no more adjustments to the project plan. There is, however, one more task to be completed before the project team disbands the end of project review.
Is this really necessary? After all, the project is all too fresh in your mind. You and everyone else on the team know all there is to know about the project. The answer is that the review is necessary, for these reasons:
Heres how to conduct the review:
And thats that. Youre happy because youve got a big rise. The clients happy and is going to give you more work. The trainees are happy because they got the training they needed when they needed it. All is happy in the garden.
Some chance - this is a software project after all. If you wanted a quiet life, you chose the wrong job. But you may start to have more successes than failures, and where you do have failures, at least youll be learning from them. At last, some feeling of control.
Clive Shepherd is running a series of two-day TBT project Management workshops in 1999 for the Institute of IT Training. For further information, contact the Institute on +44 (0)1203-418128 or by e-mail at firstname.lastname@example.org.
© Fastrak Consulting Ltd, 1999. All rights reserved. Last revised 21/2/99