HKSM

Replace this with term.

Purpose & When to Use

This process defines how the project schedule will be planned, built, updated, reported, and controlled. It sets the rules, tools, calendars, and thresholds before detailed activities are developed. Use it early in planning for every project, and tailor it for agile, hybrid, or predictive life cycles.

• Clarifies the scheduling approach, tools, and data standards the team will use.
• Establishes units of measure, calendars, estimation methods, and levels of detail.
• Sets control thresholds, baseline practices, change process, and reporting cadence.
• Aligns schedule practices with risk, resource, procurement, and governance policies.

Mini Flow (How It’s Done)

• Review the project charter, assumptions, constraints, milestones, and delivery strategy.
• Assess enterprise policies, historical schedules, and tool standards from the organization.
• Select the scheduling approach (predictive, agile, or hybrid) and decide on timeboxing or critical path focus.
• Define rules for breaking down work, activity naming, coding, and required activity attributes.
• Choose estimation methods (expert judgment, analogous, parametric, three-point) and required accuracy ranges.
• Set project and resource calendars, work periods, and units of measure for duration and effort.
• Decide on buffers, leads and lags usage, and how dependencies will be modeled.
• Define performance measurement and reporting (e.g., percent complete rules, EVM if used, burndown charts for agile).
• Establish schedule baseline timing, control thresholds, and the change control path.
• Describe data management: tools, IDs, versioning, storage, and access rights.
• Integrate with other plans: scope, resources, risk responses, releases and iterations, and procurement timelines.
• Draft the schedule management plan, review with stakeholders, obtain approval, and communicate it.

Quality & Acceptance Checklist

• Scheduling approach and life cycle tailoring decisions are documented and justified.
• Tools, templates, calendars, and coding structures are defined and accessible.
• Estimation methods, accuracy ranges, and rounding rules are stated.
• Rules for dependencies, leads and lags, and constraints are clear.
• Thresholds for variance (e.g., percentage or days) and response actions are set.
• Baseline creation timing and approval steps are specified.
• Progress measurement rules (percent complete, EVM, or agile metrics) are described.
• Reporting formats, levels of detail, and frequency for different audiences are listed.
• Resource calendars and availability integration are addressed.
• Change control path for schedule updates is aligned with overall change control.
• Interfaces to scope, risk, procurement, and quality management are identified.
• Data governance: version control, naming conventions, storage location, and access rights are defined.

Common Mistakes & Exam Traps

• Jumping into network diagrams or Gantt charts before defining scheduling rules and calendars.
• Confusing the schedule management plan with the project schedule; one is a plan, the other is the time-phased result.
• Skipping control thresholds, leading to unclear escalation when the schedule slips.
• Not aligning with agile practices when using iterations, sprints, or rolling wave planning.
• Ignoring resource calendars and availability, causing unrealistic dates.
• Failing to define progress measurement rules, which causes inconsistent status reporting.
• Assuming baseline is set during this process; the baseline is established after the initial schedule is developed and approved.
• Overusing hard constraints instead of logical relationships and buffers.
• Neglecting integration with risk responses, procurement lead times, and external dependencies.

PMP Example Question

Your sponsor asks for a detailed Gantt chart, but the team has not yet agreed on estimation methods, calendars, or how schedule changes will be controlled. What should the project manager do first?

1. Create the network diagram from the WBS.
2. Estimate activity durations using expert judgment.
3. Create the schedule management plan that defines methods, calendars, and control rules.
4. Baseline the schedule to set stakeholder expectations.

Correct Answer: C — Create the schedule management plan that defines methods, calendars, and control rules.

Explanation: Establish the approach and rules for scheduling before building and baselining the detailed schedule. This prevents rework and sets clear control and reporting expectations.