Formal project reviews
If you want to make sure your project actually delivers the benefits the organisation wants you should use periodic formal reviews.

Get someone independent!
When you need to know what's happening the grapevine and politics normally prevent internal staff giving a candid assessment .

Project Management and subject experience!
You need to pick the reviewer carefully - because depending on the skills of that person the answers you get will be different. In formal reviews of IT projects you should pick someone who is not only an experienced project manager but also understands the implications of the technologies involved. It is wise to include such considerations because you don't just need to know about proper management control of the project - you also want the project to produce the results hoped for.


Phone 0118 961 9467 for more details.

You shouldn't try to use the results of other reviews?
If you need overall business orientated answers then normal quality assurance and internal reviews won't produce the goods.

One also should not confuse formal reviews with the process of gaining commitment for a future project stage. Formal reviews are best conducted when there is substantial real activity occurring.

Do you try and use a public sector style gateway review?
This has been used in some organisations - but caution is needed as it is best suited to large procurements taking a viewpoint as an investor or purchaser rather than one more closely interested in the project.

Do you consider a formal review only if things are going wrong?
The length of the project, the rate of project spend and the rate at which the business is changing make it reasonable that a formal review should be conducted at least twice a year.

Required questions are marked with*