PurrLearnPurrLearn
Project Management

Core Skills

From the lifecycle, scope, and schedule to risk and agile: build a solid foundation in 'getting things delivered under constraints.'

Unit 1
Project Life Cycle
Tell the project life cycle apart from the five process groups (IPECC), master the full set of moves from charter and the three baselines to monitoring, acceptance, and lessons learned, and choose among predictive, adaptive, and hybrid life cycles by uncertainty.
  1. 1Project Life Cycle & the Five Process Groups: the Road a Project Travels, and the Moves You Make on Every StretchThe life cycle is the road a project travels; IPECC is the set of management moves repeated on every stretch — start and finish properly, from charter to lessons learned, then choose predictive, adaptive, or hybrid by uncertainty10 Q
Unit 2
Scope & WBS
Understand the WBS definition and the 100% rule, learn to decompose outcomes rather than actions down to work packages you can estimate and control (8/80), tell the WBS apart from task lists, Gantt charts, and org charts, and build one in five steps with a WBS dictionary as the scope baseline.
  1. 2Work Breakdown Structure (WBS): Use the 100% Rule to Decompose Scope into Work Packages You Can Estimate and ControlA deliverable-oriented, level-by-level decomposition — break down outcomes (nouns), not actions (verbs), stop at 8-80-hour work packages, and remember: if it's not in the WBS, it's not in the project10 Q
Unit 3
Schedule & the Critical Path
Use the Critical Path Method to compute the shortest project duration: find the longest chain of zero-float activities where any delay delays everything, and spend schedule compression and management attention where they count.
  1. 3Critical Path Method (CPM): Find the Chain Where Any Delay Delays EverythingBorn 1957–1959 when Kelley and Walker scheduled plant maintenance — the longest chain of dependent activities sets the shortest project duration, and only zero-float tasks are 'critical'10 Q
Unit 4
Risk Management
From risk registers and the probability-impact matrix to EMV and the four response strategies for threats and opportunities: turn 'something might go wrong' into 'we have a plan,' and keep contingency vs management reserves straight.
  1. 4Project Risk Management: Turning 'Something Might Go Wrong' into 'We Have a Plan'Risk includes opportunities and managing it is a continuous loop — identify with a register and 'cause → uncertain event → effect,' assess with the P-I matrix and EMV, respond with four strategies each for threats and opportunities, and keep contingency vs management reserves straight10 Q
Unit 5
Agile & Scrum
Read the Agile Manifesto's 'over' statements as a priority ordering rather than a rejection, master Scrum's three empirical pillars, three accountabilities, five timeboxed events, and three artifacts with their commitments — and see through the mini-waterfall and status-meeting myths.
  1. 5Agile & Scrum: From 'Left Over Right' to the Three Pillars, Three Accountabilities, Five Events, and Three ArtifactsThe Agile Manifesto doesn't reject documentation or plans — it ranks priorities; the Scrum Master is not a project manager and the Daily Scrum is not a status meeting — the skeleton and the myths, straight from the Scrum Guide 202010 Q