Task 2 has a 5-day duration, is tied to Task 1 with a predecessor, and is expected to begin once Task 1 is completed. Due to a resource availability conflict, Task 1 was rescheduled to start 1 week later. Once Task 1 was rescheduled, the planned start date on Task 2 did not dynamically shift by 5 days as expected but instead remained the same planned start date that existed before the change to Task 1.
What may have caused the planned start date of Task 2 to remain the same?
In this scenario, the fact that Task 2's start date did not shift automatically despite its dependency on Task 1 suggests that a manual override was applied, resulting in a Task Constraint of 'Must Start On.' This type of constraint locks a task to a specific date, preventing it from dynamically adjusting based on changes to its predecessor. The other options either do not explain why the start date remained static or involve user-specific scheduling conflicts, which would not affect the system-driven date adjustment.
Bobbie
2 months agoLeonardo
2 months agoDominga
3 months agoMelissia
3 months agoChanel
3 months agoGlen
2 months agoHalina
2 months agoFelix
2 months agoCelia
2 months agoSon
2 months agoMira
2 months agoBobbie
3 months ago