Start a project
Learn how to start a built project, resolve a resource conflict at the launch date with the proposed sequencing, and read the result on the KPIs and the Gantt chart.
KairoProject
The walkthrough
In two minutes, the video shows how to start a built project and how to handle a resource conflict at launch. You see how to:
- choose the start date of the project and launch it;
- spot the resource conflict flagged at that date;
- review the proposed sequencing in the dialog window;
- pick the shift option: start the project 1 day and 3 hours later;
- read the result on the KPIs and on the Gantt chart.
A resource conflict at launch
When you start a project, KairoProject checks that its resources are available at the chosen date. Here, one of them is already committed: launching the project as is would create a conflict.
Rather than leaving you to arbitrate blindly, KairoProject opens a dialog window that proposes a sequencing. The option chosen in the tutorial is the simplest one: shift the project by 1 day and 3 hours so the resource is free when it is needed.
The result: KPIs and Gantt
Once the project has started, the video lands on the indicators and the Gantt chart:
- 15% of the buffer is consumed: the shift has a cost, but it stays modest;
- the project is shifted by 1 day and 3 hours, as planned;
- the last task of the critical chain is still ahead of the deadline, even though part of the buffer has been consumed.
Worth remembering
Resolving a resource conflict by shifting the start is not free: it consumes buffer. That is exactly what the buffer is for, absorbing this kind of disruption. As long as the last task of the critical chain stays ahead of the deadline, your deadline is protected.
What comes next
If you have not set your project deadline yet, watch how to set a project deadline. To build your plan end to end, see building a project manually. To understand how the buffer protects your deadline, watch the critical chain in action and read the guide What is CCPM?.
Frequently asked questions
Once the project is built, you choose the start date and launch the project. If a resource is already committed on that date, KairoProject opens a dialog window that proposes a sequencing.
A dialog window appears and proposes a sequencing for the project. In the tutorial, the option chosen is to shift the project by 1 day and 3 hours to avoid the conflict.
Not necessarily. In the tutorial example, the 1-day-and-3-hour shift consumes 15% of the buffer, but the last task of the critical chain is still ahead of the deadline.