Project Management Framework
Initiation - Schedule

Definition

The project schedule defines the start and completion of the project, and notes milestones or phases for completion or implementation of key functionality.

Why is this important?

Identifying the start date, end date, and important milestones of a project supports resource planning, strategic planning, IT Portfolio updates, and/or funding requests/budget preparation.

Instruction

Identify the start date and completion dates of the project. Also identify the target completion date of the milestones, phases, or deliverables.

Time estimates should range broadly enough to complete all necessary work including all deliverables. Develop and/or review estimates with appropriate experts. Always project a completion date. If there is uncertainty about completion dates then consider using broader periodicity terms such as month, season, year, or biennium.

How to scale

Break down milestones and phases into their component parts if there is a need for more scheduling detail. Since the charter document is developed in the project's initiation phase, consider a higher level of detail for scheduling events that occur in the near future and be more general in specifying the timeframes for events that happen in later phases.

Related Links:
Schedule Examples

Checklists

SCHEDULE
Is there a project start and end date? Is it consistent with Objective Statements' start and end dates?
If there are known barriers/issues to completing the project within defined constraints, have they been documented and communicated?
Have major phases, milestones, and deliverable dates been noted?

 

 

 

| Home | Privacy | Site Map | Copyright © 2008 by DIS