Page 66 -
P. 66

Time


                                           Task A

                                                                         Task B
                                        Task C




                                                      Task D





                                                                       Task E

                          FIGURE 4-2. Gantt chart
                          • Task A is a Start-to-Start (SS) predecessor of Task C. Both tasks start at the same time. If
                            the start time for Task A were delayed, then the start time for Task C would move forward
                            to match it. For example, a team of software testers might all be expected to start their test
                            executions at the same time. One tester’s task would depend on the build being delivered;
                            that task would be a Start-to-Start predecessor for the other testers’ tasks.

                          • Task C is a Finish-to-Start (FS) predecessor of Task D. Task D is a Finish-to-Start (FS)
                            predecessor of a milestone, which in turn is a Finish-to-Start predecessor of Task E.
                          • Task E is a Finish-to-Finish (FF) predecessor of Task B. Note the delay before Task B
                            starts—it does not start until its planned completion time will match up with Task E.
                            This allows the resources required for Task B to be allocated to another task in the
                            meantime. For example, a test plan can be started as soon as the requirements are com-
                            plete, but it cannot be completed until after the design is done. So the test plan task
                            would have the requirements task as a Finish-to-Start predecessor and the design task
                            as a Finish-to-Finish predecessor.

                          Reconcile the Schedule with the Organization’s Needs
                          Once all of the task durations and predecessors have been determined, the project man-
                          agement software can calculate an expected due date for the project. If this date does not
                          fit with the needs of the organization or the project stakeholders, the project manager
                          should first go back to the resource list to see if the tasks can be reallocated more effi-
                          ciently. One way to do this is to look for large gaps in the schedule; sometimes a small shift
                          or swap in resources can close those gaps.

                          Another way to deal with a schedule that runs past a non-negotiable due date is to add or
                          rearrange resources (if available). This is one reason it is important to set up different
                          kinds of predecessors. By making a longer task a Finish-to-Start predecessor of a shorter
                          task, for example, a gap in the allocation level for resources might emerge in front of the
                          shorter one. That gap could be moved or filled with another task.
                   58  CHAPTER FOUR
   61   62   63   64   65   66   67   68   69   70   71