The project management session focused on project planning, scheduling, and the Critical Path Method (CPM). The session followed a structured overview of the planning process and included a recap of previous material to ensure foundational understanding.
 
Project Planning and Scheduling Flow

 

The speaker emphasized that successful project planning follows a logical, step-by-step approach. This flow is essential for project managers to understand and articulate:

  1. Define Scope and Objectives:Understand the “why,” what is in scope, what is out of scope, and success criteria.
  2. Establish Resource and Budget: Determine high-level requirements for labor and non-labor costs.
  3. Work Breakdown Structure (WBS): Decompose the project into granular, sub-task details, ensuring each has an ID for version control.
  4. Schedule Planning: Develop a calendar-based plan including columns for activity, predecessor (dependency), assignee, duration, and start/end dates.
  5. Visual Representation: Convert the schedule into a Gantt chart or a network diagram.

Critical Path Method (CPM)

 

The speaker provided a deep dive into the CPM, defining it as the longest sequence of dependent tasks that determines the total project duration. Key takeaways include:

  • Total Float/Slack: This is the buffer time an activity can “sleep” without delaying the project end date.
  • Critical Path Identification: Tasks on the critical path have zero float or buffer. Any delay in these specific tasks directly impacts the overall project schedule.
  • Concurrent Activities: Tasks performed in tandem (e.g., slicing onions while cooking) are not part of the critical path because they contain buffer time and do not dictate the total project duration.

Practical Application and Tools

  • Excel vs. Software: While professional software (e.g., Microsoft Project, Smartsheet) automates calculations for start/end dates and dependencies, the speaker utilizes Excel to teach the fundamental principles. Understanding the manual process ensures proficiency regardless of the specific tool used.
  • Progress Monitoring: Once a plan is implemented, it should be updated and reviewed weekly to track progress, manage delays, and maintain control.
  • Network Nodes: To build a network diagram, project managers must track the Early Start/Finish and Late Start/Finish times for each activity to identify potential risks.

The session concluded with an exercise testing the attendees’ ability to calculate total project duration, identify critical path activities, and determine float times. The next session is scheduled to cover stakeholder management.

Â