Chapter 3 Planning the Project

A project plan turns an analytical intention into coordinated work. This chapter shows how to define deliverables, work backward from decision dates, estimate effort and elapsed time, identify dependencies, establish review gates, and manage risks without treating the original plan as fixed when evidence changes.

Learning outcomes

After completing this chapter, you should be able to:

• convert deliverables into a workable project schedule;
• estimate effort using tasks, dependencies, review cycles, and contingency;
• distinguish active work time from calendar time;
• identify project risks and appropriate response strategies; and
• use milestones and definitions of done to detect schedule problems early.

Key terms

• Milestone: A meaningful checkpoint that indicates a stage of the project has been completed or is ready for review.

• Dependency: A relationship in which one task, decision, or resource must be completed or available before another task can proceed.

• Critical task: A task whose delay would directly delay a major milestone or final deliverable unless the plan is changed.

• Buffer: Time or capacity reserved to absorb uncertainty, rework, delays, or unexpected problems.

• Risk register: A maintained record of possible events that could harm the project, including their likelihood, impact, warning signs, owner, and planned response.

• Deliverable: A defined product that must satisfy stated content, quality, and format expectations.

• Review cycle: A planned sequence of drafting, checking, feedback, revision, and approval.

• Definition of done: A specific set of conditions that must be satisfied before a task or deliverable can be considered complete.