Key IT Project Management Methodologies

Why This Matters

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.

---

Sequential and Structured Approaches

These methodologies prioritize upfront planning, documentation, and predictable phases. They work best when requirements are stable and changes are costly.

Waterfall

Waterfall follows linear, sequential phases where each stage must be completed before the next begins. The typical flow is: requirements → design → implementation → testing → deployment.

• Thorough documentation at every stage creates clear audit trails and reduces ambiguity for large teams
• Best for low-uncertainty projects where requirements are well-defined upfront and changes are expensive or impractical
• The major tradeoff: if you discover a problem late in the process, going back to fix it is expensive because earlier phases are already "locked in"

PRINCE2

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.

• Controlled environment focus with clearly defined roles, responsibilities, and decision-making authority
• Business case driven: the project must demonstrate continued viability at each stage gate, or it gets shut down
• Widely used in government and large enterprise settings where accountability and audit trails are non-negotiable

Critical Path Method (CPM)

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.

• Float (or slack) time tells you which tasks have scheduling flexibility without delaying the overall project. Tasks on the critical path have zero float.
• Essential for complex, interdependent projects where resource allocation and timing directly impact delivery
• If any task on the critical path slips, the entire project slips by the same amount

---

Agile and Iterative Approaches

These methodologies embrace change, deliver value incrementally, and prioritize customer feedback over rigid plans. They're ideal when requirements evolve throughout the project.

Agile

Agile is more of an umbrella philosophy than a single methodology. It's defined by the Agile Manifesto (2001), which values:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

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

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.

• Three defined roles: Scrum Master (removes obstacles and facilitates the process), Product Owner (prioritizes requirements and represents stakeholders), and Development Team (builds the product)
• Key ceremonies: sprint planning, daily stand-ups (brief 15-minute syncs), sprint reviews, and sprint retrospectives
• Retrospectives are where the team reflects on what went well and what to improve, enforcing continuous adaptation

Extreme Programming (XP)

XP is an Agile framework that zeroes in on technical excellence to keep code quality high and defects low.

• Core practices include pair programming (two developers at one workstation), test-driven development (TDD, writing tests before code), and continuous integration (merging code changes frequently)
• Frequent small releases with heavy customer involvement throughout development
• Simplicity principle: build only what's needed now, refactor continuously, and avoid over-engineering

---

Flow-Based and Continuous Improvement Methods

These methodologies focus on optimizing ongoing work rather than managing discrete projects. They're ideal for maintenance, support, and process refinement.

Kanban

Kanban uses visual workflow boards (columns like "To Do," "In Progress," "Done") to display work items moving through stages. This makes bottlenecks immediately visible.

• Work-in-progress (WIP) limits cap how many items can be in any stage at once, preventing teams from being overloaded and improving flow efficiency
• Continuous delivery model with no fixed iterations. Work flows through the system as capacity allows, and new items are pulled in when space opens up.
• Particularly well-suited for teams handling unpredictable or ongoing work like IT support, bug fixes, or content production

Lean

Lean's central goal is to maximize value while minimizing waste. It systematically identifies and eliminates non-value-adding activities from processes.

• Defines seven types of waste (overproduction, waiting, transport, over-processing, inventory, motion, defects)
• Respect for people combined with continuous improvement (kaizen, a Japanese term for "change for the better") creates sustainable efficiency gains
• Originated in Toyota's manufacturing system but is now widely adopted in software development and service industries

---

Quality and Data-Driven Methodologies

These approaches use measurement and statistical analysis to drive improvement. They're ideal when defect reduction and process consistency are primary goals.

Six Sigma

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.

• DMAIC framework provides a structured improvement cycle:
  1. Define the problem and project goals
  2. Measure current performance with data
  3. Analyze data to identify root causes
  4. Improve the process based on analysis
  5. Control the improved process to sustain gains
• Data-driven decision making uses statistical tools to identify root causes rather than relying on intuition or guesswork

Rational Unified Process (RUP)

RUP is a hybrid approach that incorporates structure from Waterfall (defined phases) with flexibility from Agile (iteration and feedback within each phase).

• Four phases, each with specific goals and milestones:
  1. Inception: define scope, identify risks, build initial business case
  2. Elaboration: establish architecture, refine requirements, address major risks
  3. Construction: build out the system iteratively
  4. Transition: deploy to users, conduct training, gather feedback
• Risk-driven iteration addresses the highest-risk elements early, so you don't discover deal-breaking problems late in the project

---

Quick Reference Table

---

Self-Check Questions

1. 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?

2. 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?

3. Compare and contrast Scrum and Kanban: what do they share as Agile-influenced approaches, and what fundamental difference makes each suited to different contexts?

4. 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?

5. How do Six Sigma and Lean differ in their primary focus, and in what situation might an organization implement both simultaneously?