Project Controls Scheduler – Preventing Blowout

Project Controls Scheduler – Preventing Blowout 

Creating a project schedule

For a project schedule to have value it must be detailed and dynamic enough for you to be able to re-forecast requirements when you identify potential problems or risks are realized. A good schedule tells you what you need to know, not what you want to hear. To get good information out of a schedule then it needs detailed information input into the system, such as:

• Risks to the project. After conducting a project risk analysis input the results into the schedule. It is important to identify potential risks to plan in any extra time or resource requirements.
• Project scope description. The project description outlines start and end dates for activities. It will include any assumptions built into the project plan, and list major limitations and restraints. Create milestones from stakeholder requirements.
• Resource demands and project tasks. Consider what constraints you have when creating a schedule. Factor in staff capabilities and experience, resource and staff availability, and staff holidays. Everything can affect meeting the schedule.