Project management Study Guide

📖 Core Concepts Project – A temporary, unique effort with a defined start and end that creates a product, service, or result. Primary Constraints (Iron Triangle) – Scope, Time, Cost (budget). Successful projects meet all three. Secondary Challenge – Optimally allocate inputs (people, materials, money) to meet client‑driven objectives. Project vs. Operations – Projects are one‑off, non‑repetitive; operations are ongoing, repetitive activities. Work Breakdown Structure (WBS) – Hierarchical decomposition of the project’s work into manageable work packages. Critical Path – The longest sequence of dependent activities with zero float; any delay on this path delays the whole project. Earned Value Management (EVM) – Integrates scope, schedule, and cost performance into a single set of metrics. Complexity Types – Structural (many interrelated parts) and Dynamic (uncertainty, emergence). Success vs. Performance – Performance = meeting triple constraints; Success = delivering benefits, outcomes, and strategic impact. --- 📌 Must Remember Triple Constraint (Iron Triangle) – Time ↔ Cost ↔ Scope; quality is the center of the triangle. Critical Path Method (CPM) – Deterministic activity durations; critical path = tasks with 0 % float. Program Evaluation and Review Technique (PERT) – Uses optimistic (O), most likely (M), pessimistic (P) estimates: $$\text{Expected duration } = \frac{O + 4M + P}{6}$$ Earned Value Formulas Planned Value (PV) – Budgeted cost for work scheduled to date. Earned Value (EV) – Budgeted cost for work actually performed: $EV = \% \text{complete} \times BAC$. Actual Cost (AC) – Money spent to date. Schedule Performance Index (SPI) – $SPI = \dfrac{EV}{PV}$ ( >1 = ahead). Cost Performance Index (CPI) – $CPI = \dfrac{EV}{AC}$ ( >1 = under budget). RACI Matrix – Responsible, Accountable, Consulted, Informed – clarifies role assignments. Complexity Classification (Cynefin) – Simple → Complicated → Complex → Chaotic. BRM (Benefits Realization Management) – Focuses on measuring benefits (outcomes) rather than just outputs. Agile / Iterative Approaches – Use sprints, incremental delivery, and embrace change. --- 🔄 Key Processes Initiating Define project purpose, high‑level scope, and objectives. Produce Project Charter, Stakeholder Analysis, SWOT, PBS, WBS, and RACI. Planning Choose methodology (predictive, iterative, rolling‑wave). Sequence activities → build network diagram → calculate CPM/PERT. Estimate resources, durations, costs → develop baseline schedule and budget. Conduct risk identification, analysis, and develop mitigation plan. Obtain formal approval to proceed. Executing Mobilize resources, assign work packages, hold kickoff meeting. Manage communications, procurements, and stakeholder expectations. Monitoring & Controlling Track EV, PV, AC → compute SPI, CPI → identify variances. Perform integrated change control; update schedule, budget, and risk registers. Use float analysis to protect non‑critical tasks. Closing Obtain formal acceptance, close contracts, archive documentation. Conduct lessons‑learned session and post‑implementation review. --- 🔍 Key Comparisons Project vs. Operations Project: temporary, unique, defined end. Operations: ongoing, repetitive, no defined end. Hard vs. Soft Project Management Hard: physical deliverables (buildings, bridges). Soft: intangible outcomes (software, services). CPM vs. PERT CPM: deterministic times, best for stable activities. PERT: stochastic times, uses O‑M‑P weighting for uncertainty. Predictive vs. Iterative vs. Rolling‑Wave Predictive: scope fixed up‑front, detailed plan early. Iterative: scope evolves; deliverables built in increments. Rolling‑Wave: detailed planning only for near‑term work; later phases are high‑level. Project Success vs. Project Performance Performance: meets time, scope, cost (efficiency). Success: delivers benefits, outcomes, strategic impact (effectiveness). --- ⚠️ Common Misunderstandings Scope = Deliverables only – Scope also includes work needed to create those deliverables. Critical Path = Critical Tasks – Only tasks on the critical path have zero float; other tasks can slip without harming the finish date. Agile eliminates documentation – Agile still requires sufficient documentation; the difference is “just enough” and often living in shared tools. EVM only tracks cost – EVM simultaneously tracks schedule (SPI) and cost (CPI) against the baseline. Complexity = Size – A small project can be highly complex (dynamic uncertainty) and a large project can be simple (well‑defined processes). --- 🧠 Mental Models / Intuition Balancing Scale (Iron Triangle) – Imagine a three‑legged stool; remove or shorten any leg (time, cost, scope) and the stool (project) collapses. Longest Road Analogy (Critical Path) – The project’s finish date is set by the longest “road” you must travel; shortening side roads (non‑critical tasks) won’t speed you up. Thermometer (EVM) – EV is the temperature reading of progress; CPI and SPI are the “heat” and “speed” gauges indicating whether you’re burning fuel efficiently or lagging. Puzzle Pieces (Complexity) – Structural complexity = many pieces; dynamic complexity = pieces that change shape while you’re assembling. --- 🚩 Exceptions & Edge Cases Ill‑Defined Objectives – Vague client goals lead to scope creep and uncontrolled changes; always convert objectives into measurable requirements. Stochastic Activity Times – Use PERT when activity durations are uncertain; CPM assumptions break down. Scope Change Approved Late – May require re‑baselining the schedule and budget; treat as a formal change request. Virtual Teams – Time‑zone differences can create “hidden float” in communication; schedule overlapping hours for critical syncs. Benefit Realization – Even if triple constraints are met, failure to capture benefits (BRM) means the project may still be deemed unsuccessful. --- 📍 When to Use Which CPM → Deterministic activities, well‑defined durations, need exact schedule. PERT → High uncertainty in activity times; need probabilistic duration estimates. EVM → Projects where cost and schedule integration is critical (large budgets, stakeholder scrutiny). Agile / Scrum → Projects with ambiguous or rapidly changing requirements, especially software or service development. BRM → When strategic benefits and ROI are the primary success criteria (e.g., transformation programs). CCPM → Resource‑constrained environments where the Theory of Constraints can improve throughput. Waterfall (Predictive) → Construction, hardware, or any project with stable, well‑understood requirements. --- 👀 Patterns to Recognize Zero Float Activities → Likely belong on the critical path; watch for any delay. High Number of Dependencies → Indicates structural complexity; may need decomposition (more WBS levels). Repeated Scope Change Requests → Red flag for poorly defined objectives; trigger re‑baseline. Large Discrepancy between SPI and CPI → Schedule progressing well but cost overruns (or vice‑versa) – investigate root cause. Stakeholder Map with Many “Informed” Only → Potential communication gaps; consider expanding RACI. --- 🗂️ Exam Traps “Triple Constraint includes Quality” – Quality is the center of the triangle, not a corner constraint. Confusing Critical Path with Critical Chain – Critical chain adds resource buffers (CCPM); critical path is pure schedule logic. Assuming a WBS is a Schedule – WBS organizes work, not when it occurs; the schedule comes from sequencing the WBS elements. Choosing Agile because the exam mentions “fast‑changing” – Verify that the question also specifies iterative delivery and stakeholder collaboration; otherwise a hybrid approach may be correct. “All risks must be eliminated before starting” – Risk management is about identification, analysis, and mitigation, not eradication. Misreading PERT formula – Remember the 4 × M weighting; using a simple average (O+M+P)/3 is wrong. ---