Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Project management methodologies aren't just buzzwords for your resume—they're the operational frameworks that determine whether projects deliver on time, on budget, and at the quality level stakeholders expect. You're being tested on your ability to recognize when to apply which methodology, understand the trade-offs between flexibility and control, and explain how different approaches handle uncertainty, change, and resource constraints. These concepts connect directly to broader operations themes like process improvement, quality management, capacity planning, and lean operations.
Don't fall into the trap of memorizing definitions in isolation. The real exam value comes from understanding why a methodology works for certain project types and how it addresses specific operational challenges. When you see a scenario question, you need to instantly recognize whether the situation calls for predictive planning or adaptive iteration, whether the priority is eliminating waste or controlling defects. Master the underlying principles, and you'll handle any application question thrown your way.
These approaches assume requirements can be defined upfront and that following a structured sequence leads to successful delivery. They prioritize control, documentation, and phase-gate reviews over flexibility.
Compare: Waterfall vs. PRINCE2—both are structured and phase-based, but PRINCE2 adds explicit governance roles and stage-gate reviews that Waterfall lacks. If an exam question asks about accountability and control mechanisms, PRINCE2 is your stronger example.
These approaches embrace uncertainty by delivering work incrementally and incorporating feedback continuously. They prioritize working deliverables and customer collaboration over comprehensive documentation.
Compare: Scrum vs. Kanban—both are Agile, but Scrum uses fixed-length sprints with defined roles, while Kanban emphasizes continuous flow with WIP limits. FRQ tip: if asked about managing unpredictable workloads (like support tickets), Kanban is usually the better answer.
These frameworks focus on eliminating waste, reducing defects, and continuously improving operational performance. They often complement project methodologies rather than replace them.
Compare: Lean vs. Six Sigma—Lean focuses on speed and waste elimination, while Six Sigma targets defect reduction through statistical control. Many organizations combine them as "Lean Six Sigma" to address both efficiency and quality simultaneously.
These aren't methodologies you "implement" but rather reference frameworks that define best practices and professional standards across methodologies.
Compare: PMBOK vs. PRINCE2—PMBOK is a knowledge standard describing what to manage, while PRINCE2 is a methodology describing how to manage it. PMBOK provides the vocabulary; PRINCE2 provides the process.
| Concept | Best Examples |
|---|---|
| Predictive/Sequential Planning | Waterfall, PRINCE2, CPM |
| Adaptive/Iterative Delivery | Agile, Scrum, XP, Kanban |
| Waste Elimination | Lean, Value Stream Mapping |
| Defect Reduction & Quality | Six Sigma, DMAIC |
| Visual Workflow Management | Kanban, Value Stream Mapping |
| Time-boxed Iterations | Scrum, XP |
| Continuous Flow | Kanban, Lean |
| Professional Standards | PMBOK, PRINCE2 |
A client has fixed regulatory requirements and needs extensive documentation for compliance audits. Which methodology (Waterfall or Agile) is better suited, and why?
Compare Scrum and Kanban: what do they share as Agile approaches, and what key structural difference determines when you'd choose one over the other?
A manufacturing team wants to reduce production defects while also shortening lead times. Which two methodologies would you recommend combining, and what does each contribute?
If a project manager uses CPM analysis and discovers Task D has zero float, what does this mean for resource allocation and schedule risk?
An FRQ describes a software team struggling with changing requirements and stakeholder dissatisfaction with delivered features. Identify which Agile practices (from Scrum or XP) would directly address these problems and explain the mechanism.