Information Technology Reference
In-Depth Information
If all these agencies are to be brought on to the same page, nothing is more simpler
and cost effective than a document. A format helps documenting the plan compre-
hensively than placing an overhead on the project manager. It reminds the project
manager of any aspects of the project that are either missed or forgotten.
Another pitfall that I had occasion to witness is to treat project schedule prepared
using MS-Project or such other tool as the entire plan for the project. Nothing can be
more misleading. It is simply a schedule. Such schedules do not contain the selected
methodology, standards, guidelines, formats, templates and checklist for the project
and tools and techniques proposed for use on the project. A schedule also does not
contain the methodology of carrying out quality control activities, defect reporting
and resolution methodology, an escalation mechanism, nor does it document the
configuration and change management procedures. So, preparing a schedule and
treating it as the comprehensive project plan is not very wise.
A less common pitfall is to overdo the documentation part. Use of a very
comprehensive template even for a short duration project is a pitfall. The plan
ought to be commensurate with the size and duration of the project. Using the
same comprehensive template for all projects without considering the project size
and duration is not very wise.
Search WWH ::




Custom Search