I'm confused about the behavior of Start to Finish. Why does the "predecessor" task not shift forwards to begin on the end date of the "successor" task? What would be a real-world example of this kind of task relationship? Thanks
Hello Michael, you have wandered into a confusing part of project management methodology. FF, SS, FS all make intuitive sense. Start to Finish requires more thought..... the predecessor will not move out because by definition this is the predecessor Starts and based on that start there is a schedule of when the successor would finish. Example: in contracting laying concrete and putting up a basketball pole.... you don't want to finish setting the pole after the concrete has cured. You need to finish setting the basketball pole "X" hours after the concrete has started so you could assign a SF + 4h which means the setting of the pole (successor) needs to finish 4 hr after the start of laying concrete. It is not a common precendence relationship... hope that helps
Thank you for the message. That is a complex question and PM experts will have a variety of methods and tools. One would be to insert a 'dummy' task in each phase of the project and if on the critical path would extend each phase by the duration of the dummy task. When you execute the project and finish a phase or have more clarity on the schedule can adjust the duration or delete the dummy task.
@@ProjectLibreCloud Also, getting this error now "ProjectLibre Error | An error occured while saving." btw, LOVING the simplicity of the usage of the software. A novice like me desperately needs that. Loving it so far. Seriously.
Good explanation ❤
I'm confused about the behavior of Start to Finish. Why does the "predecessor" task not shift forwards to begin on the end date of the "successor" task? What would be a real-world example of this kind of task relationship? Thanks
Hello Michael, you have wandered into a confusing part of project management methodology. FF, SS, FS all make intuitive sense. Start to Finish requires more thought..... the predecessor will not move out because by definition this is the predecessor Starts and based on that start there is a schedule of when the successor would finish. Example: in contracting laying concrete and putting up a basketball pole.... you don't want to finish setting the pole after the concrete has cured. You need to finish setting the basketball pole "X" hours after the concrete has started so you could assign a SF + 4h which means the setting of the pole (successor) needs to finish 4 hr after the start of laying concrete.
It is not a common precendence relationship... hope that helps
@@ProjectLibreCloud Thank you! Makes more sense now.
very cool
Hi, How can you introduce contingency in a schedule?
Thank you for the message. That is a complex question and PM experts will have a variety of methods and tools. One would be to insert a 'dummy' task in each phase of the project and if on the critical path would extend each phase by the duration of the dummy task. When you execute the project and finish a phase or have more clarity on the schedule can adjust the duration or delete the dummy task.
nice ingpo gan👍
I'm on a Mac. How do I save the project so that I can come back to it later?
File menu and Save
@@ProjectLibreCloud is there a way to save it directly to the desktop instead of the system folders?
@@ProjectLibreCloud Also, getting this error now "ProjectLibre Error | An error occured while saving." btw, LOVING the simplicity of the usage of the software. A novice like me desperately needs that. Loving it so far. Seriously.