a generic term for the set of project control methods, including work breakdown structure, resource assignments and schedules.
a defined plan for executing a project. A Project Plan should specify: 1. The methodology for the project, including the phases, activities, and steps required to execute the project, along with their sequencing, and; 2. The human and machine resources required to perform the work, including both internal and external resources.
A list of tasks with individual responsibility and target dates assigned.
a collection of tasks and related information that document in detail how a project's deliverables will be produced
a formal, approved document used to manage and control the execution of the project
an eRoom item that lets you create a simple, structured project schedule containing tasks that describe the lifetime of your project
an estimate, a schedule, a set of milestones for marking progress, and an assignment of your team or your own time to each task on the estimate
an important output of the planning process
a timeline of tasks and events that will take place during the project
In ASAP, an overall plan with three components: the Budget Plan, the Resource Plan, and the Work Plan.
The Project Plan is the Microsoft Project document that tracks the schedule, tasks, baseline, and milestones of a project. Compare with Preliminary Project Plan.
Schedules, budgets, assignments, and status evaluations for the management of an Application Engineering project.
The project plan defines the dates, milestones, tasks and deliverables that will drive the project. It defines who is responsible for doing what, and by when. The project plan enables the EPRI project manager to monitor and control progress as the work proceeds. This plan is developed and agreed upon by the software developer and the EPRI project manager.
A formal written plan defining a projects aims and objectives, and explaining how they will be achieved, what the project will deliver, how the project will be managed, and how success will be measured. Project plans and any subsequent changes must be agreed with the JISC Executive. JISC provides a template for project plans.
Is produced at the beginning of a project and defines the products required, the activities, time, budget, resources and responsibilities which are required to produce the defined products. At the beginning of a project the project plan is typically high level, but as the project progresses, more details can be added and the plan becomes more accurate in its estimates of the time, cost, resources and activities required to complete the products.
A deliverable of the planning stage which identifies the staff involved in the project, estimated time, approaches and techniques which will be used.
A high-level plan showing the major products of the project, when they will be delivered and at what cost. An initial Project Plan is presented as part of the Project Initiation Document. This is revised as information on actual progress appears. It is a major control document for the Project Board to measure actual progress against expectations.
Popular tool used to plan and schedule the time relationships among project activities, usually recorded by the project leader. 14.5
Defines all work in a project and who will do it. A typical project plan consists of: a statement of work, a resource list, work breakdown structure, a project schedule and a risk plan
Integrated view of all functional and technical work required to complete a project as defined by its scope. The plan details the tasks, schedule, cost, resources, milestones and deliverables needed to complete the project. Progress is tracked against the plan and measured by work complete, by reaching milestones and completing deliverables. Reports can be produced at different levels of detail about any component of the plan, for any level of management use.
A description of the project that divides it into sub-projects, including start and completion times, responsible parties, interdependence of work steps, and resources needed.
A management document describing the approach taken for a project. The plan typically describes work to be done, resources required, methods to be used, the configuration management and quality assurance procedures to be followed, the schedules to be met, the project organization, etc. Project in this context is a generic term. Some projects may also need integration plans, security plans, test plans, quality assurance plans, etc.
a document for management purposes that gives the basics of a project in terms of its objectives, justification, and how the objectives are to be achieved. This document is used as a record of decisions and a means of communication among stakeholders. It gives the supporting detail to the project definition which details the schedule, resource and costs for the project.
A management document describing the approach that will be taken for a project. The plan typically describes the work to be done, the resources required, the methods to be used, the configuration management and quality assurance procedures to be followed, the schedules to be met, the project organization, etc.
Document identifying key matters of a project.
A formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communications among stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be summarized or detailed.
A document that lists the Work Breakdown Structure, timeframes and resources required to undertake a project.
Refer to Project Schedule Project Portfolio Management The management of prioritised projects within the organisation, Business Unit, Agency or across government. It is a dynamic process requiring re-prioritisation, as necessary, to meet changing business requirements or emerging opportunities.
A formal, approved document used to guide both project execution and project control. Documents the scope, cost, schedule, assumptions, and constraints of the project.
See software project management plan.