Project Management

Please login or join to subscribe to this thread

Automatically incrementing start dates

linkedin twitter facebook  
avatar
Brendan T Malaysia
Hi guys,

I wanted to get your feedback on an item I was considering.
Many project tasks are not on the critical path and as such there is no consequence to starting the task later than planned - indeed this is often the case.
Therefore I was wondering if such common phenomenon cannot be represented. So, the idea would be to increment the start date for tasks that have not yet been started but whose start date had already reached todays date. This would have the effect of shifting the current(tasks due to start today), non active tasks to the following day. In reality this is essentially what is happening - tasks that are not being worked on will be shifted. Normally this task shifting would be manual so essentially this would automate this process.
The points I wanted to ask here,

1. Do you see any disadvantage in applying this automated approach?
2. Is there any software that can already do this?

thanks

Brendan
Sort By:
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Brendan, I personally somehow disagree with the statement: "No Consequences" ... What if something goes wrong ? There is always risk associated with such steps. Theoretically, you can't start later than the Late Start Date otherwise you might end up with a delay in the start of the successor activity. You can always use Leads & Lags within the allowable thresholds. I am not sure if this answers your concern, if not, then maybe you can ellaborate further on what exactly are you looking for here.
avatar
Brendan T Malaysia
Hi Rami, thanks for the reply.
By no consequences I mean does not endanger project schedule, with the disclaimer as you have highlighted as not being later than latest start date.
In terms of what I am considering, there are a couple of aspects to it.

1. Mirroring Reality: Many people do not start at the earliest opportunity and rather deliver for the latest possible date.
2. A more appropriate indicator for project delay. I have had project plans with activities starting at the earliest possible date and when the due date they flag as late, so I have a sea of red tasks. However, since they are not critical path they are not endangering the schedule - at least not yet! So, I wonder if a move towards task "slack", is a more appropriate way to focus on the tasks most relevant for project schedule instead of the "late", tasks that have no impact.
The other item I consider is the formation of new critical paths for tasks with no action taken and how an automatic approach can track that.
...
1 reply by Rami Kaibni
Dec 24, 2015 12:48 PM
Rami Kaibni
...
You are welcome. If I think or come across anything I will definitely let you know. For now, I still would stick to my feedback above. Happy Holidays !
avatar
LIH WANG PM I APM| Siemens Rail Automation Systems Ltd. Taiwan Office T'Ai-Pei, Taiwan
Usually you can put some "Float" tasks (or you can call Leads&Lags) as subtasks into the main task activities, so that the due days can be adjusted as wish.
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Dec 23, 2015 11:45 PM
Replying to Brendan T
...
Hi Rami, thanks for the reply.
By no consequences I mean does not endanger project schedule, with the disclaimer as you have highlighted as not being later than latest start date.
In terms of what I am considering, there are a couple of aspects to it.

1. Mirroring Reality: Many people do not start at the earliest opportunity and rather deliver for the latest possible date.
2. A more appropriate indicator for project delay. I have had project plans with activities starting at the earliest possible date and when the due date they flag as late, so I have a sea of red tasks. However, since they are not critical path they are not endangering the schedule - at least not yet! So, I wonder if a move towards task "slack", is a more appropriate way to focus on the tasks most relevant for project schedule instead of the "late", tasks that have no impact.
The other item I consider is the formation of new critical paths for tasks with no action taken and how an automatic approach can track that.
You are welcome. If I think or come across anything I will definitely let you know. For now, I still would stick to my feedback above. Happy Holidays !

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Two roads diverged in a wood, and I... took the one less traveled by, and that has made all the difference."

- Robert Frost

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters