PMP Project Management Essentials in 3 Minutes
The project management ideas the PMP keeps coming back to, explained out loud in three minutes — then test yourself with ten practice questions.
Transcript
The PMP exam rarely asks you to recite definitions. Instead it puts you in a situation and asks what a good project manager would do next. To answer those questions well, you need a few core ideas that shape how you think. Here are five.
First, the triple constraint: scope, time, and cost. These three are linked, and quality sits in the middle of them. If a sponsor adds scope, something else has to give. Either the schedule grows, the budget grows, or quality suffers. A good project manager does not quietly absorb a change. They analyze its impact and take it through change control.
Second, the critical path. This is the longest path of dependent activities through the schedule, and it sets the shortest possible time to finish the project. Activities on the critical path usually have zero float, which means any delay to them delays the whole project. Here is a worked example. Path one takes four days, then three days, for seven days total. Path two takes two days, then six days, for eight days total. Path two is longer, so it is the critical path, and the project needs at least eight days. Path one has one day of float, because it can slip one day without moving the finish date.
Third, stakeholder engagement. Stakeholders are anyone who affects or is affected by the project. You identify them early, understand their interest and influence, and communicate with them in a planned way. When a powerful stakeholder is unhappy, the answer is almost never to ignore them or go around them. It is to engage them directly.
Fourth, predictive versus agile. A predictive, or waterfall, approach plans the full scope up front and works well when requirements are clear and stable. An agile approach delivers in short iterations, welcomes changing requirements, and gets frequent feedback from the customer. Many real projects mix the two, which is called hybrid.
Fifth, risk responses for threats. Avoid means changing the plan to eliminate the risk entirely. Transfer means shifting the impact to a third party, like buying insurance or signing a fixed price contract. Mitigate means reducing the probability or impact, like adding extra testing. Accept means acknowledging the risk and dealing with it if it happens, sometimes with a contingency reserve.
Recap: scope, time, and cost move together; the critical path is the longest path with zero float; engage stakeholders directly; match predictive or agile to the situation; and know avoid, transfer, mitigate, and accept.
Test yourself on Project Management
10 questions, easy to hard. No account needed to try it.
Which three elements make up the classic triple constraint?
Buying insurance to cover a project risk is an example of which risk response?
Which approach delivers work in short iterations and welcomes changing requirements?
What is the critical path of a project schedule?
Adding extra testing to reduce the chance of defects reaching customers is which risk response?
A sponsor asks to add a new feature without changing the deadline or budget. What should the project manager do first?
Path A takes 4 days then 3 days. Path B takes 2 days then 6 days. What is the minimum project duration?
Using the same example, how much float does Path A have?
A team changes the project plan to remove an activity that carries a major risk, eliminating the risk entirely. Which response is this?
An influential stakeholder is unhappy with the direction of the project. What is the best action?