Claudia Eggers November 30, 2020 Project Management
One of the tools you can use to get things structured and organized is the "Project Checklist". This checklist is a roadmap to setup and put a framework around the project before it gets started. Each PM has their own style and set of tools, but if you are working on building your own toolbox, the project checklist is an important item to have when defining the project itself.
To start we will be clear that we are not going to deal here with repetitive implementation / rollout projects where a template plan has been refined over a series of projects and becomes a standard checklist for project management (for example for COTS - commercial off-the-shelf software). This article is about those one off (or initial template try-out) projects. These projects may be within organisations small, medium and large.
Many of these products assume a knowledge of project management that many technical managers do not have. Without an understanding of the basic concepts of project management, managers may often find the software is confusing and hard to use. The first step in project management is to break the project down into measurable tasks and organize them into a hierarchy called the work breakdown structure (WBS). Different companies have different terms for the various levels in a work breakdown structure. Some levels include stages, steps, and tasks, or phases, activities, and tasks.
A project in general is divided into many phases depending on the life cycle model used for it. In general, the methodology deals with the genesis of a scheme, controlling it and termination of the plan! Where it all begins! An organization begins on a project, by getting down the objectives of the customer. The requirement gathering report should be as unambiguous as possible. You do not want to give a two-story house when the client had actually asked for two storerooms in the house! Get the deal straight! Then a mandate is provided to the client, which is an official document stating the needs of the customer, for their verification.
Projects tend to slip for two reasons. Either Project Managers do not account for derivative activities such as vacation days when planning the overall project schedule, or they simply succumb to the pressure from management to compress the schedule. Now, present this schedule to the management team, and 8 times out of 10, the feedback you will get is "that`s too late". Eight times out of ten, you will be asked to revise the schedule and shorten it.
One of the challenges of explaining project management to people who are unfamiliar with the approach, is that descriptions are often either so high-level as to be meaningless, or so detailed that they are overwhelming. Over the years, I have come to use a model as a framework for introducing and discussing project management tools and techniques. It can be used as the basis for a five-minute explanation of what is involved in project management, but also as an outline for more detailed discussions. The actual model can be found on the Key Consulting website under free templates and info.