Project scheduling is the process of deciding how the work in a project will be organised as separate tasks, and when and how these tasks will be executed.

Estimate the time you think it will take with no mess ups, then ad time for seen mess ups, then add 50% extra time for unseen mess ups.

How to present it

Project schedules may simply be documented in a table or spreadsheet showing the tasks, estimated effort, duration, and task dependencies.

Presentation styles include:

1. Calendar-based Gantt/bar charts show who is responsible for each activity, the expected elapsed time, and when the activity is scheduled to begin and end.

2. Activity networks show the dependencies between the different activities making up a project. These networks are described in an associated web section.

Each activity has:

• duration: in calendar days or months;

• effort estimate: which shows the number of person-days or person-week or person-months to complete the work

• deadline: by which the activity should be complete

• defined endpoint: which might be a document, the holding of a review meeting, the successful execution of all tests, or the like