What You Actually Need for the Exam
The PMP exam is 180 questions split across three domains: People, Process, and Business Environment. Most people treat the formula sheet like it's going to save them, but it's only a small part of what you need. I built mine from scratch after failing my first attempt, and the difference was less about memorization and more about knowing where to look when you're stuck. Here's what I ended up with and why each section matters.
Pmp Cheat Sheet
Formulas That Show Up
You don't need every formula in the PMBOK. The exam focuses on these six, and knowing when to use each one matters more than rote memorization. Expected Monetary Value (EMV): Multiply the probability by the impact. If a risk has a 30% chance of costing $50,000, the EMV is minus $15,000. Positive numbers go on opportunities, negative on threats. I once had a question that gave me three separate risks on the same work package and asked for the total exposure. I just added them up after calculating individual EMVs. Took me about two minutes. Profit Margin: (Revenue minus Cost) divided by Revenue. Don't confuse it with markup, which divides by cost. The PMI wants the profit margin definition. I've seen people pick the wrong answer here because they mixed up the denominator.
CPI and SPI: CPI is EV divided by AC. SPI is EV divided by PV. CPI above 1.0 means you're under budget. SPI above 1.0 means you're ahead of schedule. That's it. The confusion comes when the question gives you actual costs and you have to calculate EV first. Pay attention to what numbers are actually stated versus what you need to derive. To-Complete Performance Index (TCPI): This is the harder one. If you need to finish within the original budget, it's (BAC minus EV) divided by (BAC minus AC). If you're working off a new estimate at completion, swap BAC for EAC in the denominator. I kept mixing these up during my second study pass, so I wrote a note on my cheat sheet: "TCPI = remaining work divided by remaining money. Which money depends on whether they changed the target." Communication Channels: n times n minus 1 divided by 2. Five stakeholders means ten channels. Ten means forty-five. It shows up maybe once per exam, but when it does, people waste time drawing diagrams. Just plug into the formula.
Get the Full Details
Payback Period and NPV: Expected to come up in business environment questions. For NPV, discount future cash flows using the given rate. If the question gives you a table of cash flows and asks which option is best, NPV is the tiebreaker when payback periods are similar.
Versions Matter More Than You Think
The biggest mistake I see is treating agile and predictive the same way on answers. The exam uses-based questions, and the right answer changes depending on which approach the scenario describes. If the scenario mentions short iterations, frequent feedback, changing requirements, or a product backlog, go with the agile answer. Look for terms like sprint, scrum master, retrospective, adaptive planning. The PMBOK 7th edition shifted hard toward principles instead of prescriptive processes, and the exam reflects that. If the question talks about a fixed scope, detailed planning upfront, change control boards, and earned value tracking, it's predictive. The answer will involve formal change requests, baseline updates, and documented approvals.
Hybrid scenarios exist too. A project might plan the architecture predictively but build in agile sprints. In those cases, read every line of the question carefully before picking an answer. I lost two questions on my second attempt because I assumed the answer without finishing the read-through.
Process Groups and Knowledge Areas
The old process group matrix is still useful as a reference, even though the 7th edition moved away from it. Here's what maps where: Initiating covers the project charter and stakeholder register. Planning produces the project management plan and all subsidiary plans. Executing is where the team does the work and quality assurance happens. Monitoring and controlling tracks variance and manages changes. Closing wraps up deliverables and releases resources. Knowledge areas like scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder management each have their own inputs, tools, and outputs. You don't need to memorize every ITCITO, but knowing which process belongs to which area helps you eliminate wrong answers quickly.
Agile-Specific Concepts
Agile questions make up roughly half the exam now. These are the ones people lose points on because they studied from an older edition. Scrum events include sprint planning, daily standup, sprint review, and retrospective. Roles are product owner, scrum master, and development team. Artifacts are product backlog, sprint backlog, and increment. Kanban focuses on visual workflow, work in progress limits, and flow efficiency. There are no fixed iterations. If the scenario describes a team pulling work based on capacity rather than working in timeboxes, Kanban is the answer, not Scrum.
Lean principles include eliminating waste, building quality in, delivering fast, deciding late, empowering the team, and optimizing the whole. These show up as concept questions where you match a scenario to a principle. Agile estimating uses story points, planning poker, and t-shirt sizing. Velocity measures how many story points a team completes per sprint. Use it for forecasting, not for comparing teams against each other. I saw a question asking which metric to use for capacity planning, and velocity was the right call, not burn-down rate.
A Real Problem I Ran Into
During my second attempt, I hit a question that described a project using agile development but predictive procurement. The team was doing two-week sprints, but contracts were fixed-price with milestone payments. I almost picked a purely agile answer because the development side dominated the scenario. The correct answer involved a hybrid approach: use agile for delivery but follow the contract terms for procurement and financial tracking. The workaround was simpler than I thought. I started underlining every methodological term in the question before reading the answer choices. If half the terms said agile and the other half said formal contracts or baselines, I marked it hybrid immediately. That habit alone probably saved me three or four questions on the actual exam.
What Your Cheat Sheet Should Not Include
Don't waste space on definitions you can reason through. Don't copy entire process groups. The exam tests application, not recall. A good cheat sheet is maybe two pages, front and back, with only things you actually mix up under pressure. Things to leave out: the full list of estimating techniques, generic definitions of leadership styles, and every input-tool-output combination. You'll forget half of it during the exam anyway if you try to cram everything in.
How I Used Mine During the Test
I brought a printed version. The PMI allows one sheet, single-sided, letter size. I used a pen to circle answers I was unsure about and marked a question number in the corner of my scratch paper so I could come back. Flagging doesn't matter as much since the exam is computer-based and doesn't let you return to flagged questions easily. The biggest time sink on the exam is reading the scenario. Each question can be 150 to 300 words. I learned to read the question first, then the scenario, then the answer choices. Some people read backwards and find it faster, but I found that flipping the order helped me identify what was actually being asked before getting lost in context.
Where to Get a Reliable Version
There are dozens of Pmp Cheat Sheet PDFs online. Most are outdated or filled with incorrect formulas. The ones from official PMI members and recently updated courses tend to be accurate. Check the publication date. If it references only the 6th edition PMBOK or doesn't include agile content, skip it. A few reliable sources include the PMI member resources, well-reviewed study guides from certified instructors, and forums where people share their personal sheets with version notes. I found mine by cross-referencing three different sheets and keeping only the sections where all three agreed.
The Limits of a Cheat Sheet
It won't help if you haven't done practice questions. The exam is designed to catch people who memorize without understanding. A formula sheet is a safety net, not a strategy. If you're scoring below 60 percent on practice exams, no amount of memorizing will close that gap. You need to work on scenario comprehension and answer elimination. Also, the exam occasionally includes questions that test your judgment on ethics or professional responsibility. Those don't map to any formula or process. They map to the PMI Code of Ethics and Professional Conduct. Memorize the four values: responsibility, respect, fairness, and honesty. If an answer choice aligns with any of those, it's usually right. If it shifts blame, hides information, or breaks a contract, it's wrong. The cheat sheet is a tool. The real work is understanding when to apply each concept and when to step back and think about what the question is actually testing. I wish someone had told me that on my first attempt.
