HKSM

The planning activity that builds a realistic, approved timeline for delivering the project. It combines activities, sequencing, durations, resources, calendars, and risks into a usable schedule model and baseline, tailored for predictive, agile, or hybrid approaches.

Purpose & When to Use

• Create a credible timeline to guide execution, coordination, and stakeholder expectations.
• Integrate scope, resources, and risk information into a single schedule model and baseline.
• Enable forecasting and decision-making through views such as Gantt, network diagrams, release plans, and iteration calendars.
• Use during planning and refine continuously as estimates improve, risks emerge, and change requests are approved.
• Apply in all delivery modes: predictive (detailed baseline), agile (releases, sprints, cadence), and hybrid (timeboxes with milestone anchors).

Mini Flow (How It’s Done)

• Confirm Inputs: WBS or backlog, activity list and attributes, dependencies, resource calendars, effort and duration estimates, risks and assumptions, constraints, procurement lead times, and organizational calendars.
• Sequence Activities: Define logical relationships, leads and lags, and mandatory versus discretionary links. Build a network diagram for transparency.
• Estimate Durations: Convert effort to duration using resource availability. Use historical data, Monte Carlo where needed, and for agile use velocity, cycle time, and team capacity.
• Assign Resources and Calendars: Match skills to activities, apply working time, holidays, and team availability. Adjust for part-time resources and concurrent work.
• Build the Schedule Model: Choose methods such as critical path or critical chain for predictive, and release or sprint planning for agile. Create milestones and buffers where appropriate.
• Analyze and Optimize: Run what‑if scenarios, level or smooth resources, adjust leads/lags, and apply schedule compression (fast-tracking or crashing) while assessing risk and cost impacts.
• Baseline and Communicate: Obtain approval, store the schedule baseline, define metrics (e.g., SPI/SV or burn charts), and publish views tailored to stakeholders.
• Set Update Cadence: Define how often the schedule is reviewed, how progress is captured, and how changes are controlled through the change process.

Quality & Acceptance Checklist

• All scope is represented as scheduled activities or backlog items with clear entry and exit criteria.
• Relationships are logical and minimal; leads and lags are justified and documented.
• Calendars, constraints, and assumptions are explicit and visible to the team.
• Critical path or timeboxes are identified, understood, and communicated.
• Resource loading is feasible; major overallocations are resolved or formally accepted.
• Risks and uncertainty are reflected using buffers, ranges, or contingency plans.
• Milestones, external dependencies, and procurement lead times are included and dated.
• Schedule baseline is approved, versioned, and linked to scope and cost baselines.
• Reporting views are ready for stakeholders, including management summaries and team-level details.
• Update rules and measurement methods are defined, including how progress is captured and variances are handled.

Common Mistakes & Exam Traps

• Baselining without team buy-in or resource confirmation.
• Overusing hard constraints instead of proper logic links and calendars.
• Compressing non-critical activities and expecting overall finish to improve.
• Ignoring capacity and calendars, leading to hidden overallocation.
• Applying leads and lags without justification or documentation.
• Assuming agile teams do not need schedules; agile still plans cadence, releases, and milestones.
• Not integrating risk responses and buffers, leading to overly optimistic timelines.
• Failing to include external dependencies and vendor lead times.
• Changing the schedule baseline informally instead of using change control.
• Confusing percent complete with value delivered; verify progress against finished deliverables or accepted backlog items.

PMP Example Question

A project’s schedule shows a six-week overallocation of a key specialist on critical path activities. What should the project manager do first to produce a realistic schedule without extending the final milestone?

1. Apply a fixed date constraint to the critical activities to keep the finish date.
2. Fast-track by overlapping all critical activities regardless of risk.
3. Level resources and accept the milestone slip, then request more budget.
4. Analyze the network for alternative sequencing, adjust leads and lags, and consider targeted crashing of critical work.

Correct Answer: D — Analyze the network and adjust logic, then consider selective crashing to address overallocation without blindly increasing risk.

Explanation: Start with analysis to optimize sequencing and dependencies, then apply focused compression where it helps the critical path. Constraints or indiscriminate fast-tracking can hide problems or increase risk.