Question: Assume all but the first task are duration-driven, so their start dates depend upon the tasks relationships with preceding tasks and the finish dates depend
Assume all but the first task are duration-driven, so their start dates depend upon the tasks relationships with preceding tasks and the finish dates depend upon the task durations. The first task must have its start date identified so we know when the project actually begins. The finish date is not necessary to identify as the Gantt chart software calculates it based upon the tasks duration. Predecessors refers to a preceding task number on the list that the current task will start after or start with. It is assumed that when the identified preceding task finishes, the current task will start (identified as FS, such as 7FS, or when the seventh task finishes, start this task). However a task may need to start at the same time as the preceding task (SS, such as 12SS), or a lag of days or weeks may be necessary after the preceding task finishes and before the current task starts (such as 4FS+3d, which means that when task 4 finishes, the current task can start but only after waiting three days). The Start Date and Finish Date entries do not need to be identified for all but the beginning task as the Gantt chart software will automatically calculate them depending upon the relationships between tasks, the work schedule, and the task durations. Remember, time durations refer to working time. A work week is only five actual days if the work schedule is set up for five working days per calendar week (Monday through Friday). Identify the percentage of time devoted to the task by each resource, which is helpful when tracking costs. The first four rows in this template are only for demonstration and must be deleted prior to beginning your own actual project given to you by your instructor.
| Insert Project Title Here | ||||||
| Task Number | Task Name | Duration d for days w for weeks m for months | Start Date | Finish Date | Predecessors | Resources |
| 1 | Planning committee meeting | 1d | 11/1/2019 | - | - | Planning committee 100% IT Department Head 100% Project Manager 100% |
| 2 | Finalize property purchase | 4d | - | - | 1 | Larrys Legal PLC |
| 3 | Site Survey | 1w | - | - | 2FS+7d | Sam's Surveying 100% Project Manager 25% |
| 4 | Excavating | 8d | - | - | 3 | Eds Excavating 100% Project Manager 25% |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Scenario
AC-COS Pilot Implementation Plan
Requirement: Completion of design and prototyping
Implementation Start Date: February 4 2021.
Approximate Planned Finish Date: February 22, 2021
Resources
Project Manager
System Engineer
AC-COS Architect
Power Specialist
Mechanic
Logistics
Tasks
1. Begin project, 0 duration, no resources, 2/4/21
2. Truck Delivery, 1 day, 1FS no lag, Logistics 100%
3. Unpacking and staging, 1 day, 2FS no lag, Logistics 100%, Project Manager 100%, System Engineer 100%, AC-COS Architect 100%, Power Specialist 100%, Mechanic 100%
4. System inventory and inspection, 1 day, 3SS no lag, Logistics 100%, Project Manager 100%, System Engineer 100%, AC-COS Architect 100%, Power Specialist 100%, Mechanic 100%
5. Power and mechanical prep, 2 days, 4FS, Project Manager 100%, System Engineer 100%, AC-COS Architect 100%, Power Specialist 100%, Mechanic 100%
6. AC-COS installation, 3 days, 5FS no lag, Project Manager 100%, System Engineer 100%, AC-COS Architect 100%, Power Specialist 100%, Mechanic 100%
7. System test, 1 day, 6FS plus one day of lag, Project Manager 100%, System Engineer 100%, AC-COS Architect 100%, Power Specialist 100%, Mechanic 100%
8. System acceptance, 1 day, 7FS no lag, Project Manager 100%, System Engineer 100%, AC-COS Architect 100%
9. System training, 3 days, 8FS plus one day of lag, Project Manager 100%, System Engineer 100%
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
