Components of a Project Plan
This article details the high level project plan and the components of the same. A project is a success if it meets the objectives of time, cost, technical and business. Project objectives are defined in the preliminary project scope statement. As mentioned above, a project is deemed complete if the project objectives have been met. The objectives should be clear and achievable.
The objectives for this project have been summarized as:
The project plan must contain the time taken to complete the project end-end from requirements to implementation. A detailed analysis of each stage and the time taken for the same must be outlined upfront and milestones for each stage defined.
The cost for completion of the project as defined by the time taken to complete and the technical and business objectives being met is to be defined. All the project objectives are linked to each other and any change in one variable affects the others as well. For e.g. a change in the technical requirements would mean that more time would be required to complete the project and this in turn affects the cost. Thus there are cascading affects on each of the variables.
The business objectives have to be clearly spelt out by your company in terms of the sales generated, the cost benefit analysis of building a website and consequent revenue generation etc.
The technical requirements can be stated in terms of the quality of the deliverables and the number of defects found during each of the testing phases and the turnaround time for implementation etc.
Work Breakdown Structure
The above chart is a representation of the Work Breakdown Structure (WBS) for the project. It represents a high to medium level summary and it can be refined further. The WBS has been summarized in the organization chart keeping in mind some factors like:
- The WBS is a high level overview that can be broken down into smaller and smaller package of work until the Project Manager achieves the level of granularity that he/she wants. This granularity is to be obtained keeping in mind the realistic scenarios. For e.g. the first level of the WBS described above is the same as the project life cycle, Requirements, Design etc.
- The next levels of the WBS are broken down based on the work packages that are to be assigned to the team members. The packages must be designed in such a way that the deliverables are met.
- In a way, the WBS is the foundation of the project. The time and cost of the project are defined in terms of the work packages and estimated accordingly.
|Team member 1||Team member 2||Team member 3|
P - Primary responsibility
S - Secondary responsibility
This chart cross references the WBS created for the project. Each of the work packages created in the WBS is allocated to each of the team members with primary and secondary responsibilities assigned accordingly.
The project plan consists of the above details as well as the WBS and the responsibility matrix. A detailed project plan needs more elaboration and is a separate activity altogether.
Learn management concepts & skills rapidly with easy to understand, richly illustrated self-paced learning modules & downloadable powerpoint presentations.
Click below to view DEMO on Project Management Skills
|❮ Previous Article||Next Article ❯|
About the Author(s)
MSG team comprises experienced faculty and professionals who develop the content for the portal. We collectively refer to our team as - MSG Experts. To Know more, click on About Us.
- Project Management - Introduction
- What is a Project ?
- What is Project Management ?
- Project Management - Rational Approach
- Open Systems Approach
- Importance of Project Management
- Components of Project Management
- Team Management during a Project
- Behavioural Models for Project Managers
- Role of Project Managers
- Soft Skills for Project Managers
- Costs in Project Management
- Components of a Project Plan
- Software Project Management
- Tips for Delivering Large IT Projects
- Rework and Scope Management
- Procurement of Materials & Resources
- Communications Management
- Project Integration
- Procurement and Quality Processes
- Quality Management and Quality Control
- Quality Frameworks - ISO, Six Sigma
- Time/Material Billing & Fixed Cost Billing
- Why Project Managers Should Not Overpromise and Underestimate at the Same Time
- The Need for Person Independence in Software Project Management