Your stakeholder asks for the project status. You have seventeen browser tabs open, a color-coded spreadsheet that stopped making sense two weeks ago, and a meeting in four minutes. This is the scenario a good project management cheat sheet is designed to prevent.
This reference covers the five PMBOK process groups, the terms that trip people up most, a framework comparison, and the specific considerations that apply when the project is an HR initiative. Bookmark it or print it—whichever tab you can actually find later.
Project Management Cheat Sheet: The Five Process Groups
The Project Management Institute structures project work into five sequential phases. Most methodologies—Waterfall, PRINCE2, hybrid approaches—map to these same stages under different names.
1. Initiating
Define what you're building and why. Key outputs: Project Charter, stakeholder register, preliminary scope statement. The charter is signed here—once you have sign-off, you have authorization to spend resources. Nothing else should start before this exists.
2. Planning
Turn the charter into a workable plan. This phase produces the most documents: scope statement, WBS (work breakdown structure), schedule, budget, risk register, communication plan, and procurement plan. Rushing planning is the single most predictable cause of blown budgets. It feels like overhead until week six of execution.
3. Executing
Do the actual work. The PM's job shifts from planning to coordination: managing the team, tracking vendor deliverables, running status meetings, and keeping stakeholders informed. The majority of project time is spent here, which is why planning matters—you're operating against the plan you built, not inventing it as you go.
4. Monitoring and Controlling
Runs concurrently with Executing, not after it. Compare actual performance to the plan. If variance exceeds your defined threshold, you either take corrective action or submit a formal change request. Earned Value Management metrics—CPI and SPI—live in this phase and give you early warning before problems become crises.
5. Closing
Formally end the project or phase. Archive documents, run lessons-learned sessions, release resources, obtain formal acceptance from the sponsor. Projects that skip closing tend to drag on indefinitely with no clear accountability—and the team moves on to new work while the old project still shows as open.
Essential Terms for Your Project Management Cheat Sheet
These are the terms that appear in every project and that practitioners frequently misuse or confuse. The misuse isn't trivial—it creates miscommunication on scope, accountability, and risk.
- Scope creep — Uncontrolled expansion of scope without corresponding changes to time, cost, or resources. Distinct from an approved scope change, which goes through change control.
- WBS (Work Breakdown Structure) — A hierarchical decomposition of deliverables. Not a task list, not a Gantt chart. Each level breaks down the level above it into components.
- Critical Path — The longest sequence of dependent tasks that determines the project's minimum duration. Delaying any task on the critical path delays the entire project end date.
- Float (or Slack) — The amount of time a non-critical task can slip without affecting the end date. Critical path tasks have zero float by definition.
- Baseline — The approved version of a plan (scope, schedule, or cost) used as a reference point for measuring variance. Once baselining, changes require formal approval.
- Change Control — The formal process for reviewing, approving, and documenting changes to any baseline. Verbal approvals from sponsors do not count and will cause disputes.
- RACI Matrix — Responsible, Accountable, Consulted, Informed. One person is Accountable per deliverable; multiple people can be Responsible. If two people are listed as Accountable for the same task, neither one actually is.
- Risk vs. Issue — A risk is a potential future event with a probability and impact. An issue is a risk that has already materialized. Keep them in separate logs.
- EVM (Earned Value Management) — A performance measurement technique. CPI (Cost Performance Index) below 1.0 means you're over budget per unit of work completed. SPI (Schedule Performance Index) below 1.0 means you're behind schedule.
- Kickoff Meeting — The formal start of execution. Not the first planning session. By kickoff, the charter and high-level plan should already exist and be approved.
- Lessons Learned — Documented knowledge captured during and after the project. The process only works if someone reviews them before the next similar project starts—which rarely happens without a deliberate process.
Framework Comparison: Waterfall, Agile, and PRINCE2
Selecting a methodology before understanding what each is optimized for leads to predictable problems. Agile doesn't fix poor requirements discipline; PRINCE2 doesn't fix organizational disinterest in governance.
- Waterfall (PMBOK-based): Sequential phases, well-suited for stable and well-defined requirements. Changes are expensive once you're past planning. The dominant approach in construction, manufacturing, and compliance-heavy HR projects.
- Agile (Scrum/Kanban): Iterative sprints, built for evolving requirements. Works well for software-adjacent HR projects (HRIS rollouts, applicant tracking implementations). Requires a dedicated product owner or scope sprawls.
- PRINCE2: Strong governance emphasis, mandatory business case review at each stage gate. Common in government and large enterprise. Documentation overhead makes it impractical for smaller teams without modification.
- Hybrid: Waterfall governance with Agile delivery. The most common real-world approach for HR and organizational change projects—structured enough for business case sign-off, flexible enough for delivery.
For most HR-specific projects—HRIS implementations, policy rollouts, organizational redesigns—hybrid approaches work best. The business case and stakeholder governance need structure; the actual delivery benefits from iteration and feedback loops rather than a fixed plan built six months in advance.
HR Project Management: Where the Cheat Sheet Gets More Specific
Standard PM training doesn't account for what happens when your deliverable is a behavioral change or a culture shift. HR projects have dynamics that are consistently underweighted in generic PM curricula.
Change Management Is Not a Phase
Technical delivery and adoption are separate problems. An HRIS can go live on time and on budget and still fail because employees route around it. Change management—stakeholder engagement, training, communication—needs its own workstream from project initiation, not a task added in week eight of execution.
Stakeholder Mapping Takes Longer Than Expected
HR projects touch almost every function. A compensation review involves HR, Finance, Legal, and every department head, each with different interests and definitions of success. Build your stakeholder register early and update it when scope changes—new stakeholders surface late when you skip this step.
Confidentiality Complicates Communication Planning
Many HR projects involve information that can't be shared broadly during planning. Restructuring, compensation changes, and performance management overhauls require tiered communication plans: one version for the project team, one for affected managers, one for general staff. Standard communication plan templates don't account for this.
Success Metrics Are Harder to Define
A construction project is complete when the building exists. An HR project is complete when the software is live, or when adoption hits 80 percent, or when satisfaction scores improve—depending on who you ask. Defining measurable success criteria in the charter prevents months of debate at closeout about whether the project actually succeeded.
Top Courses
A cheat sheet covers the vocabulary. Structured learning builds the ability to apply it under pressure. These are the courses worth the time investment.
Foundations of Project Management
Google's entry-level PM course on Coursera covers the full project lifecycle with practical exercises and real-world scenarios. Rated 10/10, it's the most complete beginner course available—the right starting point if you've been managing projects informally and want to formalize the methodology.
Project Initiation: Starting a Successful Project
The second course in Google's PM certificate series, focused on the Initiating phase: charters, stakeholder analysis, and setting measurable goals. Rated 9.8/10 and directly relevant to the stage where most HR projects are inadequately scoped.
Project Planning: Putting It All Together
Covers the Planning phase in depth—WBS, scheduling, budgeting, and risk management. Rated 9.7/10 and particularly strong on building project plans that can survive first contact with execution, rather than ones that require full reconstruction after week two.
Fundamentals of Project Planning and Management
University of Virginia's course on Coursera takes a more analytical approach, grounding each framework in the reasoning behind it rather than just the steps. Rated 9.7/10—worth taking if you want to understand why the methodology works, not just how to follow it.
Microsoft Project: The Five Keys – Key 3 Constraints
A focused Udemy module on managing constraints inside Microsoft Project. Rated 9.8/10 and specifically useful for teams that use MS Project for scheduling, where mishandling constraints is one of the most common causes of schedules that drift without explanation.
FAQ
What should a project management cheat sheet include?
At minimum: the five process groups, key terms (WBS, critical path, float, RACI, change control), a brief framework comparison, and a template checklist. The most useful versions are tailored to the type of projects you run—generic cheat sheets are a starting point, not a finished product.
What's the difference between a project plan and a project charter?
The charter authorizes the project. It's a short document signed by the sponsor that defines the objective, high-level scope, budget authority, and designated PM. The project plan is the detailed roadmap for how you deliver against what the charter defined. You need the charter before you build the plan—not simultaneously, not after.
Do HR professionals need a PMP certification?
Not necessarily. The PMP is worth pursuing if you're moving into a dedicated project management role or managing large capital projects. For HR professionals who run projects as one part of a broader role, a CAPM or Google's PM certificate covers what most employers require. The credential matters less than a track record of projects delivered on scope and on budget.
What's the most common reason HR projects fail?
Underestimating stakeholder resistance. HR projects change how people work, how they're evaluated, or how they're compensated. Technical delivery is rarely the failure point—projects stall or fail at adoption because change management was treated as optional. The technology works; the people don't use it as intended.
How is Agile used in HR project management?
Agile is applied primarily to technology-heavy HR projects where requirements evolve. It governs delivery, not governance—HR still needs formal business cases and executive sign-off. Pure Scrum without a governance layer creates accountability gaps in most HR environments, where project decisions have legal and compliance implications.
What tools do project managers actually use day-to-day?
Task management: Asana, Jira, Monday.com. Scheduling: Microsoft Project, Smartsheet. Documentation: Confluence, SharePoint. Communication: Slack or Teams. Most practitioners use a combination. What matters more than the tool is consistent team usage—a sophisticated platform nobody updates is worse than a shared spreadsheet everyone maintains.
Bottom Line
The terms and frameworks in this cheat sheet aren't trivia—they're the shared language that keeps projects from unraveling when different functions need to coordinate. If you're an HR professional managing projects without formal PM training, start with the five process groups and the RACI matrix. Those two things alone will resolve most of the accountability gaps and scope disputes that characterize failing projects.
For structured learning, the Google PM certificate on Coursera—starting with Foundations of Project Management—is the clearest path from informal PM experience to functional methodology. It's self-paced, sequenced logically, and doesn't require a background in project management to follow.