Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
When you're tested on IT project management methodologies, you're not just being asked to recall names and definitions. You're being evaluated on your understanding of when and why organizations choose specific approaches. The core tension in project management is between predictability and adaptability: some projects need rigid structure and upfront planning, while others thrive on flexibility and rapid iteration.
These methodologies also demonstrate key Information Systems concepts: risk management, stakeholder alignment, resource optimization, and continuous improvement. Each approach represents a different philosophy about how to handle uncertainty, manage teams, and deliver value. Don't just memorize what each methodology does. Know what problem it solves and when it's the right tool for the job.
These methodologies prioritize upfront planning, documentation, and predictable phases. They work best when requirements are stable and changes are costly.
Waterfall follows linear, sequential phases where each stage must be completed before the next begins. The typical flow is: requirements → design → implementation → testing → deployment.
PRINCE2 (Projects IN Controlled Environments) is a governance-heavy framework built around seven principles, seven themes, and seven processes. It emphasizes organization, control, and quality at every level.
CPM is a scheduling technique that identifies the longest sequence of dependent tasks in a project. That sequence is the "critical path," and it determines the minimum possible project duration.
Compare: Waterfall vs. PRINCE2: both emphasize structure and documentation, but PRINCE2 adds explicit governance principles and continuous business case validation. If a question asks about government or enterprise projects, PRINCE2 is your go-to example.
These methodologies embrace change, deliver value incrementally, and prioritize customer feedback over rigid plans. They're ideal when requirements evolve throughout the project.
Agile is more of an umbrella philosophy than a single methodology. It's defined by the Agile Manifesto (2001), which values:
The key idea is iterative, incremental delivery: break projects into short cycles that each produce working functionality, then use continuous feedback to steer the next cycle.
Scrum is the most widely adopted Agile framework. It organizes work into time-boxed sprints (typically 2-4 weeks), each producing a potentially shippable product increment.
XP is an Agile framework that zeroes in on technical excellence to keep code quality high and defects low.
Compare: Scrum vs. XP: both are Agile frameworks, but Scrum focuses on project management structure (roles, ceremonies, sprints) while XP emphasizes engineering practices (pair programming, TDD). Many teams combine both.
These methodologies focus on optimizing ongoing work rather than managing discrete projects. They're ideal for maintenance, support, and process refinement.
Kanban uses visual workflow boards (columns like "To Do," "In Progress," "Done") to display work items moving through stages. This makes bottlenecks immediately visible.
Lean's central goal is to maximize value while minimizing waste. It systematically identifies and eliminates non-value-adding activities from processes.
Compare: Kanban vs. Scrum: Kanban has no fixed iterations or prescribed roles, focusing purely on flow optimization, while Scrum provides more structure with sprints and defined ceremonies. Kanban suits ongoing operations; Scrum suits discrete projects with defined goals.
These approaches use measurement and statistical analysis to drive improvement. They're ideal when defect reduction and process consistency are primary goals.
Six Sigma aims for statistical defect elimination, targeting fewer than 3.4 defects per million opportunities. That's where the name comes from: six standard deviations (sigma) from the mean in a normal distribution.
RUP is a hybrid approach that incorporates structure from Waterfall (defined phases) with flexibility from Agile (iteration and feedback within each phase).
Compare: Six Sigma vs. Lean: both focus on efficiency, but Six Sigma targets defect reduction through statistical analysis while Lean targets waste elimination through process streamlining. Organizations often combine them as "Lean Six Sigma" to get the benefits of both.
| Concept | Best Examples |
|---|---|
| Sequential/Predictive Planning | Waterfall, PRINCE2, CPM |
| Iterative/Adaptive Delivery | Agile, Scrum, XP, RUP |
| Flow-Based Continuous Work | Kanban, Lean |
| Quality/Defect Reduction | Six Sigma, XP |
| Heavy Documentation | Waterfall, PRINCE2, RUP |
| Customer Collaboration Focus | Agile, Scrum, XP |
| Statistical/Data-Driven | Six Sigma, CPM |
| Hybrid Approaches | RUP, Lean Six Sigma |
Which two methodologies would you recommend for a project with well-defined requirements that cannot change mid-development, and why do they share this characteristic?
A software team needs to maintain a production system while handling unpredictable support requests. Which methodology best fits this scenario, and what specific feature makes it appropriate?
Compare and contrast Scrum and Kanban: what do they share as Agile-influenced approaches, and what fundamental difference makes each suited to different contexts?
If a question asks you to recommend a methodology for a startup building a new app with unclear requirements and heavy user involvement, which approach would you choose and what three features would you cite?
How do Six Sigma and Lean differ in their primary focus, and in what situation might an organization implement both simultaneously?