Project Coordination Cheat Sheet

Updated 2026-04-29

Next Topic: Project Governance and Stage-Gate Management Cheat Sheet

🧠Study flashcards on this topic104 cards · spaced repetition→

Project coordination is the organizational practice of synchronizing activities, resources, dependencies, and stakeholder communication to deliver project outcomes on time and within budget. Rooted in both the PMBOK® Guide's principles-based performance domains and modern agile, hybrid, and scaled-agile frameworks, coordination sits at the intersection of planning, tracking, and team alignment. Successful project coordinators master not only the technical aspects of scheduling and resource allocation, but also the human elements—keeping distributed teams informed, aligned, and focused on shared deliverables. The techniques in this cheat sheet represent the practitioner's toolkit: methods actively used to prevent delays, manage constraints, track progress against baselines, and maintain visibility across complex, multi-modal project environments.

What This Cheat Sheet Covers

This topic spans 14 focused tables and 105 indexed concepts, 104 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Core Planning FrameworksTable 2: Dependency and Scheduling TechniquesTable 3: Resource Management MethodsTable 4: Progress Tracking and Performance MetricsTable 5: Baseline ManagementTable 6: Estimation TechniquesTable 7: Schedule Compression MethodsTable 8: Coordination Meetings and CeremoniesTable 9: Risk and Issue ManagementTable 10: Communication and ReportingTable 11: Agile Coordination PracticesTable 12: Advanced Scheduling ConceptsTable 13: Quality Management MethodsTable 14: Project Closure Techniques

Quick IndexSubscribe to unlock

A jump-to index of every table row in this cheat sheet.

Mind MapSubscribe to unlock

An interactive map of every table and concept in this topic.

Table 1: Core Planning Frameworks

These are the foundational structures a coordinator reaches for first to give a project shape — defining what gets built (WBS), how it's sequenced (Gantt, CPM, PERT), who owns what (RACI, Team Charter), and how work flows (Kanban, Sprint Planning). Mastering this mix lets you blend traditional and agile approaches to fit whatever project lands on your desk.

Framework	Example	Description
Work Breakdown Structure (WBS)	`Project` `1.0 Design` `1.1 Requirements` `1.2 Mockups` `2.0 Development`	• Hierarchical decomposition of total project scope into deliverable-oriented components • each level adds detail until work packages are actionable, ensuring complete coverage and enabling accurate cost and duration estimation.
Gantt Chart	`Task bars on timeline` `showing start, duration, dependencies`	• Horizontal bar chart mapping each task against a calendar • visualizes schedule, dependencies, milestones, and current progress. The most widely recognized project visualization tool across industries.
Project Charter	`Purpose, scope, objectives` `stakeholders, budget, timeline`	• Formal document that authorizes project existence and empowers the project manager • defines high-level scope, objectives, success criteria, key stakeholders, assumptions, constraints, and initial risk assessment.
RACI Matrix	`Task \| John(R) \| Sarah(A) \| Team(C)` `Design \| R \| A \| I`	• Responsibility assignment chart clarifying who is Responsible, Accountable, Consulted, and Informed for each deliverable • prevents confusion and ensures a single point of accountability per task.
Critical Path Method (CPM)	`A→B→C→D (critical)` `A→E→D (2 days float)`	• Network diagram technique identifying the longest sequence of dependent tasks determining minimum project duration • tasks on this path have zero float — any delay directly impacts the completion date.
Kanban Board	`To Do \| In Progress \| Done` `Cards move left to right`	• Visual workflow management using columns representing process stages • emphasizes work-in-progress limits and continuous flow. Originated in lean manufacturing, now ubiquitous in software and service work.
Sprint Planning (Scrum)	`2-week sprint backlog` `team commits to 23 story points`	• Agile ceremony where team selects and commits to deliverables for a fixed-duration iteration (typically 1–4 weeks) • includes capacity planning, task breakdown, and definition of sprint goal.
Phase Gate Review	`Phase 1 complete → Gate 1:` `approve, redirect, or stop`	• Formal checkpoint requiring review and sign-off before the project advances to the next phase • ensures only viable, justified work proceeds, controls scope, and aligns governance with execution.
Program Evaluation Review Technique (PERT)	`Network diagram with nodes` `showing task sequences`	• Probabilistic scheduling method using three-point estimates (optimistic, most likely, pessimistic) to calculate expected duration and variance • best suited for projects with high uncertainty in activity durations.
Team Charter	`Mission, roles, norms` `decision rights, communication rules`	• Document defining a team's purpose, roles, working norms, and collaboration expectations • established at project start, it reduces ambiguity, accelerates onboarding, and serves as a social contract for accountability.

Table 2: Dependency and Scheduling Techniques

Tasks rarely run in isolation — one waits on another, two overlap, a mandatory delay sits between them. These dependency types and timing tools (FS, SS, FF, SF, plus lead, lag, float, and milestones) are the grammar of a project schedule, telling you exactly how activities connect and where you have room to maneuver.

Type	Example	Description
Finish-to-Start (FS)	`Design must complete` `before Development starts`	• Most common dependency: successor cannot begin until predecessor completes • represents sequential workflow where one task's output is required as input for the next.

The rest of this section is part of the full cheat sheet

Table 3: Resource Management Methods

People, equipment, and budget are always finite, and these methods are how you stretch them without breaking the schedule. The key tension to watch is between leveling (which protects resource limits even if the deadline slips) and smoothing (which protects the deadline by shuffling work within available float) — knowing when to reach for each is half the job.

Method	Example	Description
Resource Allocation	`Assign Alice 50% to Project A` `John 100% to Project B`	• Process of assigning available resources (people, equipment, budget) to specific tasks based on skills, availability, and priority • foundational to capacity planning.

The rest of this section is part of the full cheat sheet

Table 4: Progress Tracking and Performance Metrics

This is the full Earned Value Management toolkit — the numbers that tell you objectively whether a project is on time and on budget, and forecast where it will land if nothing changes. Everything builds from three base measurements (PV, EV, AC); the variances and indices that follow turn raw progress into early warnings, and the EAC/ETC/TCPI forecasts answer the question every sponsor asks: will we make it?

Metric	Example	Description
Budget at Completion (BAC)	`Total approved budget: $200,000` `for all project work`	• Total authorized budget for the entire project scope • the foundational EVM constant used in all cost variance, forecast, and performance index calculations.

The rest of this section is part of the full cheat sheet

Table 1: Core Planning Frameworks

Framework	Example	Description
Work Breakdown Structure (WBS)	`Project` `1.0 Design` `1.1 Requirements` `1.2 Mockups` `2.0 Development`	• Hierarchical decomposition of total project scope into deliverable-oriented components • each level adds detail until work packages are actionable, ensuring complete coverage and enabling accurate cost and duration estimation.
Gantt Chart	`Task bars on timeline` `showing start, duration, dependencies`	• Horizontal bar chart mapping each task against a calendar • visualizes schedule, dependencies, milestones, and current progress. The most widely recognized project visualization tool across industries.
Project Charter	`Purpose, scope, objectives` `stakeholders, budget, timeline`	• Formal document that authorizes project existence and empowers the project manager • defines high-level scope, objectives, success criteria, key stakeholders, assumptions, constraints, and initial risk assessment.
RACI Matrix	`Task \| John(R) \| Sarah(A) \| Team(C)` `Design \| R \| A \| I`	• Responsibility assignment chart clarifying who is Responsible, Accountable, Consulted, and Informed for each deliverable • prevents confusion and ensures a single point of accountability per task.
Critical Path Method (CPM)	`A→B→C→D (critical)` `A→E→D (2 days float)`	• Network diagram technique identifying the longest sequence of dependent tasks determining minimum project duration • tasks on this path have zero float — any delay directly impacts the completion date.
Kanban Board	`To Do \| In Progress \| Done` `Cards move left to right`	• Visual workflow management using columns representing process stages • emphasizes work-in-progress limits and continuous flow. Originated in lean manufacturing, now ubiquitous in software and service work.
Sprint Planning (Scrum)	`2-week sprint backlog` `team commits to 23 story points`	• Agile ceremony where team selects and commits to deliverables for a fixed-duration iteration (typically 1–4 weeks) • includes capacity planning, task breakdown, and definition of sprint goal.
Phase Gate Review	`Phase 1 complete → Gate 1:` `approve, redirect, or stop`	• Formal checkpoint requiring review and sign-off before the project advances to the next phase • ensures only viable, justified work proceeds, controls scope, and aligns governance with execution.
Program Evaluation Review Technique (PERT)	`Network diagram with nodes` `showing task sequences`	• Probabilistic scheduling method using three-point estimates (optimistic, most likely, pessimistic) to calculate expected duration and variance • best suited for projects with high uncertainty in activity durations.
Team Charter	`Mission, roles, norms` `decision rights, communication rules`	• Document defining a team's purpose, roles, working norms, and collaboration expectations • established at project start, it reduces ambiguity, accelerates onboarding, and serves as a social contract for accountability.

Table 2: Dependency and Scheduling Techniques

Type	Example	Description
Finish-to-Start (FS)	`Design must complete` `before Development starts`	• Most common dependency: successor cannot begin until predecessor completes • represents sequential workflow where one task's output is required as input for the next.

Table 3: Resource Management Methods

Method	Example	Description
Resource Allocation	`Assign Alice 50% to Project A` `John 100% to Project B`	• Process of assigning available resources (people, equipment, budget) to specific tasks based on skills, availability, and priority • foundational to capacity planning.

Table 4: Progress Tracking and Performance Metrics

Metric	Example	Description
Budget at Completion (BAC)	`Total approved budget: $200,000` `for all project work`	• Total authorized budget for the entire project scope • the foundational EVM constant used in all cost variance, forecast, and performance index calculations.