Best practice - predecessor tasks

[akhtar]

I have got some queries regarding tasks and predecessors. For an example, I am having the following tasks:

1. Buy ingredients
2. Bake cake
3. Eat cake
4. Cake project completed (milestone)

This tasks have each previous one as its predecessor. But for the last task, the milestone, each of the tasks 1-2 should be complete before it can be finished. So, should I make the predecessor tasks for task 4 as tasks 1,2,3? Or will it be fine to just put the task 3 as the predecessor for task 4, since task 3 will require task 2 that requires task 1, etc? Thanks.

[absolute55]

You need to first start by ensuring that every Task has atleast one FS Predecessor and one FS successor. That are the most proximate and obvious. That ensures a closed network with no open ends so that you can get a reliable result on the critical path. After that go through and look for the next most obviosu FS Predecessor for each Task. There are many tasks that will have more than one FS Predecessor, and you have to identify them all as predecessors, either directly or indirectly, or you might miss the CP.

[go83]

Can someone expand a little bit on the benefit of each task needing a predecessor and successor task? I understand the common sense benefits of using predecessors for a task that can't logically complete before another task finishes, but let's say 5 out of 10 project tasks can take place immediately. What's the benefit in Project of tying them to a "project start" Milestone? What are the risks of not doing so?

Thanks.

[aww91]

Some clarification please. Going back to the original example, how would you recommend tying a new task, that does not have a successor, to the project “end” milestone? For example:

1. Buy ingredients
2. Bake cake
3. Monitor oven temp.
4. Eat cake
5. Cake project completed (milestone)

Thanks in advance for your reply.