Technology Operations
Technology Operations
Project: A set of interrelated activities (or TASKS) that are directed at achieving a particular
good or objective.
Project Management: The process of planning & controlling key resources of the project and
their critical TASKS to meet the specified time, cost and functional objectives of a project.
-DELAYS in major projects=Costly; As timeline of project extends, so to does the budget (ie
inflation, interest, salary, plan changes)
PM Terms:
Statement of Work (SOW): a written description of the objectives to be achieved (typically
organized by Program)
Project Workplan:
-Defines all activities (or TASKS) required to complete a project
-Outlines the activities sequence and all dependencies
-Defines the resources needed to complete the project
-Provides time estimates to complete each activity and overall project
Work Breakdown Structure (WBS):
-Refers to the hierarchy of project tasks, activities, and work packages
-Break down the work plan into or sub-tasks to small components
Project Chart (R): Charts are useful because their visual presentation is easily
understood. Software is available to create the charts.
Gantt Chart: A bar chart showing both the amount of time involved, the
sequence in which activities can be performed, and the relationship among the activities.
Tracking Progress:
Actual Progress vs planned Progress: Monitored & Graphed
Tracking Gantt Chart superimposes the current schedule onto a baseline, so
deviations are visible.
Project managers can manage the deviations and implications on project
deliverables.
2
Managing Resources:In addition to scheduling each task, management needs to assign resources.
Project manager must then manage the resource deviations:
-Spot over-allocation: assigned resources exceed need.
-Spot under-allocation: too few resources assigned
-Add resources or reschedule
-Moving a task with slack time can free up resources
Stack: The amount of time an activity can be delayed without delaying the completion of the
project.
CPM- 5 STEPS!
1. Identify each activity to be done and estimate how long it will take
2. Determine the required sequence (predecessors & successors) and construct a network
diagram.
3. Determine the Early start/finish and Late start/finish
schedule
4. Identify activities with no slack time.
5. Determine the Critical Path: = path(s) through
activities with no slack time.
Drawing network diagram slide– Casserole Dish!
ES: if all prev activities began, 0 or MAX time of all immediate predecessors
EF: ES+Task time
LS: LF-Task time; finish at LF; LF-duration
LF: min LS finish without delay [bkwd]
Slack: ES-LS [OR] EF-LF
*(ES=EF if only 1 predecessor!)
BKWD: Start with MAX EF in whole network; take MIN of 2 going bkwd
No Slack=Task on Critical Path
4