HKSM

Create a realistic, logically linked timetable for the project, analyze the network, optimize resources, and set the approved schedule baseline used to track progress.

Purpose & When to Use

• Turn the activity list, estimates, dependencies, and resources into a time-phased project schedule and baseline.
• Identify the critical path, total float, and key milestones to understand schedule feasibility.
• Apply resource optimization and schedule compression to meet targets without losing logical integrity.
• Use during planning, and repeat in rolling waves or when major change requests, risks, or re-estimates occur.
• In agile or hybrid, create release roadmap, iteration calendar, and cadence-based forecasts tied to team capacity.

Mini Flow (How It’s Done)

• Confirm inputs: WBS and scope, activity list and attributes, effort and duration estimates, dependencies, resource availability, and calendars.
• Sequence activities and model logic with finish-to-start as default, adding justified leads and lags.
• Build the schedule model in a PMIS, apply calendars, and assign resources to activities.
• Run network analysis to find the critical path and float across all paths.
• Optimize resources by leveling or smoothing to handle over-allocation or to stabilize workload.
• Evaluate feasibility with what-if scenarios and, if needed, perform schedule compression focused on the critical path.
• Account for risks through reserves and buffers, and integrate external and supplier dates.
• Review with team and stakeholders, adjust assumptions, and finalize logic, durations, and assignments.
• Baseline the schedule, define performance measures, and set update and reporting rules.
• For agile or hybrid, timebox iterations, align backlog items to capacity, and publish the release plan and iteration schedule.

Quality & Acceptance Checklist

• All in-scope activities are included and traceable to the WBS.
• Every activity has a clear predecessor and successor, except start and finish nodes.
• Critical path, near-critical paths, and float are identified and reviewed.
• Calendars reflect working time, holidays, and resource-specific availability.
• Minimal use of date constraints; any must-have constraints are justified and documented.
• Leads and lags are purposeful, limited, and explained in notes.
• Resource over-allocations are resolved through leveling, smoothing, or assignments.
• External and supplier dependencies are captured with realistic dates and risk responses.
• Schedule compression decisions target critical activities and balance cost and risk.
• Risk reserves or buffers are explicitly modeled and not hidden in activity durations.
• Milestones are clear, measurable, and aligned with delivery objectives.
• Baseline is approved, versioned, and ready for change control.
• Reporting cadence, update rules, and data fields (percent complete, remaining duration) are defined.
• For agile, iteration length, team capacity, and velocity assumptions are visible and agreed.

Common Mistakes & Exam Traps

• Thinking duration estimates equal commitments; they are inputs to the model, not the approved baseline.
• Compressing non-critical activities and wondering why the finish date does not improve.
• Overusing hard date constraints that break logic and hide float.
• Ignoring resource limits and calendars, leading to impossible assignments.
• Using excessive lags instead of modeling discrete activities with clear ownership.
• Assuming fast-tracking is free; it typically raises risk and coordination effort.
• Crashing the schedule without focusing on the critical path or without cost-benefit analysis.
• Leaving external dependencies vague, causing later schedule slippage.
• Not documenting schedule assumptions and then being unable to defend the baseline.
• In agile, promising fixed scope by a fixed date without considering capacity and velocity data.

PMP Example Question

Your developed schedule finishes two weeks after the required deadline. What is the best next step?

1. Ask the team to work overtime across all activities.
2. Apply schedule compression on the critical path (crash or fast-track).
3. Add more lags to smooth the timeline.
4. Freeze the current dates and request scope changes later.

Correct Answer: B — Apply schedule compression on the critical path (crash or fast-track).

Explanation: When the finish date misses the target, analyze and compress activities on the critical path first. Overtime and added lags are not systematic and may increase risk or worsen the schedule.