Forum Discussion
Finish-to-Finish constraint not allowing representation of early start.
That's better, or at least it now makes more sense.
As set up the predecessors for 'Task A' effectively determine when 'Task A' can start. The driving dependency is the finish-to-finish with 'Task D'. A finish-to-finish dependency means that 'Task A' CANNOT be completed until, in this case, 'Task D' is complete. There is no conflict with the finish-to-start relationship with 'Task B' since that dependency means that 'Task A' cannot start until 'Task B' is complete. It does NOT mean that 'Task A' will start immediately after 'Task B' finishes.
I note that tasks 'C' and 'D' have start-no-earlier than constraints but the start of 'Task B' is apparently defined by the Project Start date. If there is some flexibility in when 'Task B' starts then this dependency configuration will get what you want.
If that doesn't work in your situation, then the only way to have 'Task A' start immediately after 'Task B' finishes is to remove the finish-to-finish relationships.
John
Right off the bat the second paragraph about 'Task A' having a predecessor of 'Task B' with a finish-to-finish relationship is contradictory. It can't then also start as soon as 'Task B' is complete.
This is how I read your scenario
If you can clarify what you mean, perhaps we can help.
John
Thanks for the Prompt Reply, Apologies my description was wrong. I should have stated:
I have a task 'Task A' which has a predecessor 'Task B' with a finish-to-start relationship
In the below example I want to show it is possible to start Task A on the 07/07/2022.
That's better, or at least it now makes more sense.
As set up the predecessors for 'Task A' effectively determine when 'Task A' can start. The driving dependency is the finish-to-finish with 'Task D'. A finish-to-finish dependency means that 'Task A' CANNOT be completed until, in this case, 'Task D' is complete. There is no conflict with the finish-to-start relationship with 'Task B' since that dependency means that 'Task A' cannot start until 'Task B' is complete. It does NOT mean that 'Task A' will start immediately after 'Task B' finishes.
I note that tasks 'C' and 'D' have start-no-earlier than constraints but the start of 'Task B' is apparently defined by the Project Start date. If there is some flexibility in when 'Task B' starts then this dependency configuration will get what you want.
If that doesn't work in your situation, then the only way to have 'Task A' start immediately after 'Task B' finishes is to remove the finish-to-finish relationships.
John
I have a similar question, searching brought me here.
Task A must complete then Task B starts.
Task C must begin (and continue) with Task A and must continue until Task B is complete.
B linked FS with A, FF with C
A linked as SS with C ( I tried reversing this, C links SS with A - same result)
If I set durations for A, B, = 1 and C =2, it makes sense, But if durations for A or B change, C duration must change, as it is supporting these. Can this be represented in Project?
J_Tebbens,
Note: if this is a duplicate reply, ignore it. I posted a reply a minute ago but it's not showing up so I'm trying again.
What you want is known as a Hammock task. This archived Wiki article will explain how it works and how to set it up:
https://web.archive.org/web/20200723171939/https://social.technet.microsoft.com/wiki/contents/articles/32040.ms-project-hammock-tasks.aspx
John