SDLC Models Compared for Project Managers: Waterfall, V-Model, Iterative, Agile and Hybrid
A project manager does not choose how code is written line by line, but does influence how the work is organised across time. That organisation is the software development life cycle (SDLC) model. Choosing a model poorly leads to frustration: a rigid plan in an uncertain domain, or loose iterations where a regulator demands signed-off documentation. This lesson compares the main models from a project manager’s perspective.
What Is an SDLC?
The SDLC describes the stages a software product goes through: requirements, design, build, test, deploy and maintain. Models differ in how they sequence and repeat those stages, and in how much they fix up front.
Waterfall
Work flows in one direction through requirements, design, implementation, testing and deployment. Each phase is completed and approved before the next begins.
- Strengths: clear structure, strong documentation, easy to contract and measure against a baseline.
- Weaknesses: late feedback, difficulty accommodating change, and defects found late are costly.
- Suits: stable requirements, regulated or safety-critical systems, fixed-price contracts with clear specifications.
V-Model
An extension of Waterfall in which each development phase is paired with a testing phase: requirements with acceptance testing, high-level design with system testing, detailed design with integration testing and coding with unit testing. Test planning begins early, alongside the matching development phase.
- Strengths: emphasis on verification and validation, traceability from requirements to tests.
- Weaknesses: same rigidity as Waterfall.
- Suits: medical, automotive, aviation and similar domains where traceability is mandatory.
Iterative and Incremental
The product is built in repeated cycles. Iterative means refining the whole product with each pass; incremental means adding finished slices. Many real projects combine both.
- Strengths: earlier working software, feedback shapes later cycles, risk is reduced progressively.
- Weaknesses: needs a sound architecture early, and scope can drift without discipline.
- Suits: projects with some uncertainty where partial delivery has value.
Spiral
A risk-driven model where each loop includes planning, risk analysis, engineering and evaluation. It is used on large, high-risk projects where early prototyping reduces uncertainty, but it is heavy and less common today.
Agile
Agile approaches such as Scrum, Kanban and Extreme Programming deliver working software in short cycles, welcome changing requirements and rely on close collaboration with the customer. Scope is a prioritised backlog, not a fixed list. See The Agile Manifesto Explained and What Is Scrum?
- Strengths: adaptability, fast feedback, early value delivery, high customer involvement.
- Weaknesses: harder to fix scope, cost and date in a contract, and it demands engaged product ownership and disciplined teams.
- Suits: evolving requirements, products where users’ reactions drive direction.
Hybrid Approaches
Many organisations combine models. A common pattern is predictive governance with Agile delivery: the programme has stage gates, a budget and a milestone plan, while the build phase runs in Sprints. Another is Waterfall for infrastructure and procurement work alongside Agile for application development. Hybrid works when the team is clear about which rules apply where, and fails when it becomes “the worst of both”, with detailed upfront plans that are then changed constantly.
Comparison Table
| Model | Requirements | Change handling | Customer involvement | First working product |
|---|---|---|---|---|
| Waterfall | Fixed early | Formal, costly | Start and end | Late |
| V-Model | Fixed early | Formal, costly | Start and end, plus testing | Late |
| Iterative / Incremental | Refined each cycle | Moderate | At each cycle | After first increment |
| Spiral | Evolve with risk | Built into loops | At each loop | Prototype early |
| Agile | Evolving backlog | Welcomed | Continuous | First Sprint or release |
| Hybrid | Fixed at high level, detailed in iterations | Governed | Mixed | Depends on design |
How to Choose a Model
Ask these questions before settling on an approach:
- How stable are the requirements? Stable favours predictive; volatile favours Agile.
- What are the consequences of failure? Safety, compliance or large financial impact favours more upfront verification.
- How available is the customer? Agile needs frequent, empowered participation.
- What does the contract require? Fixed-price deals push toward defined scope, although Agile contracts exist.
- How experienced is the team? Agile requires self-management and engineering discipline.
- What does the organisation support? Funding, governance and culture may constrain the choice.
- How large and distributed is the work? Scale may need extra coordination in any model.
For a deeper decision framework, see Agile vs Waterfall: How to Choose the Right Approach.
What Changes for the Project Manager?
In predictive projects, the project manager owns the plan, assigns tasks and tracks variance against the baseline. In Agile projects, planning is shared: the Product Owner orders the work, the team forecasts and organises it, and the project manager (if the role exists) focuses on stakeholder alignment, risk, budget, dependencies and removing obstacles. Reporting also differs: instead of percent complete, Agile projects report delivered, working increments and trends such as throughput. The skills of facilitation, risk management and stakeholder communication remain valuable in every model.
Common Mistakes
- Picking a model because it is fashionable rather than fit for the situation.
- Calling a project Agile while demanding a fixed scope and date with no flexibility.
- Running Waterfall with no change control in an uncertain domain.
- Mixing models without explaining the rules to the team and sponsor.
- SDLC models differ in how much they fix up front and how often they gather feedback.
- Waterfall and the V-Model suit stable, regulated work; Agile suits evolving needs.
- Hybrid approaches are common, but need explicit rules.
- Choose by requirement stability, risk, customer availability, contract and team maturity.