scheduling
Time constraints
The schedule (calendar schedule) created by the program may not suit you. Some tasks cannot be started on the day determined by the program because the room for this task will be rented only a week later. For some tasks, the deadlines are already defined by the contract with the contractor, and they cannot be changed. For another, the performer can participate in the work only until a certain date.
Time constraints can be used to adjust the schedule.
By default, each task already has a time constraint - As soon as possible when planning from the beginning, or As late as possible when planning from the end. These constraints are considered flexible, with their help you can build a flexible dynamic schedule, which will be automatically recalculated when changing the conditions of the project.
In fact, many users of the program unconsciously set time constraints when they manually fill in the start and end dates of each task (Start and Finish columns). When manually filling in the Start column, the task applies the constraint Start no earlier (specified date), when filling in the Finish column - Finish no earlier (specified date). These constraints can lead to unjustified delays in the project. For example, MS Project calculated the start date of the task - June 1, and you set the start date - June 15. As a result, we get a “hole in the project” lasting two weeks. Also, medium time constraints interfere with the flexibility of the calendar schedule and its automatic recalculation.
All time constraints can be conditionally divided into 3 groups: flexible, semi-flexible and inflexible. It is recommended to freely use flexible ones, and semi-flexible and inflexible ones - only if the dates are conditioned by the external environment of the project. Not us personally wanted to finish the task by June 10, but this is required by the terms of the contract, for example.
Semi-flexible constraints can lead to delays in the project, and inflexible ones - to a scheduling conflict. For example, we believe that the task must be completed by June 10, and the program calculated the completion date - June 15, taking into account durations and links. As a result - a conflict.
What to do if we still ran into a scheduling conflict? Review the deadlines for work BEFORE the conflict date. Apply methods of reducing deadlines to tasks preceding the conflict, such as fast track or compression. If it is impossible to avoid the conflict - it is necessary to escalate the issue to a higher level - the sponsor of the project or the management of the company, arguing the impossibility of observing a certain date.
See also the articles Classification of time constraints, How to set a time constraint
Time constraints can be used to adjust the schedule.
By default, each task already has a time constraint - As soon as possible when planning from the beginning, or As late as possible when planning from the end. These constraints are considered flexible, with their help you can build a flexible dynamic schedule, which will be automatically recalculated when changing the conditions of the project.
In fact, many users of the program unconsciously set time constraints when they manually fill in the start and end dates of each task (Start and Finish columns). When manually filling in the Start column, the task applies the constraint Start no earlier (specified date), when filling in the Finish column - Finish no earlier (specified date). These constraints can lead to unjustified delays in the project. For example, MS Project calculated the start date of the task - June 1, and you set the start date - June 15. As a result, we get a “hole in the project” lasting two weeks. Also, medium time constraints interfere with the flexibility of the calendar schedule and its automatic recalculation.
All time constraints can be conditionally divided into 3 groups: flexible, semi-flexible and inflexible. It is recommended to freely use flexible ones, and semi-flexible and inflexible ones - only if the dates are conditioned by the external environment of the project. Not us personally wanted to finish the task by June 10, but this is required by the terms of the contract, for example.
Semi-flexible constraints can lead to delays in the project, and inflexible ones - to a scheduling conflict. For example, we believe that the task must be completed by June 10, and the program calculated the completion date - June 15, taking into account durations and links. As a result - a conflict.
What to do if we still ran into a scheduling conflict? Review the deadlines for work BEFORE the conflict date. Apply methods of reducing deadlines to tasks preceding the conflict, such as fast track or compression. If it is impossible to avoid the conflict - it is necessary to escalate the issue to a higher level - the sponsor of the project or the management of the company, arguing the impossibility of observing a certain date.
See also the articles Classification of time constraints, How to set a time constraint
#ProjectProfessional #ProjectOnlineProfessional #Tasks #Scheduling
