Testing Tools

SDLC Models for Testers: Waterfall, V-Model and Agile

How Waterfall, V-Model, Iterative, Spiral and Agile change a tester’s daily work, with a comparison table, real project examples and interview-ready answers.

✍️ By QA Jobs India📅 20 Nov 2026⏱ 7 min read

A tester joining a bank’s core system upgrade and a tester joining a food delivery startup will both “test software”, but their weeks will look completely different. One might spend a month reviewing requirement documents before seeing a build. The other might test three small features before lunch. The difference comes largely from the SDLC models their teams follow.

This guide explains the main SDLC models from a tester’s point of view: when testing starts, what artefacts you work with, what can go wrong and how to talk about each model in interviews. The focus is on Waterfall, V-Model and Agile, which you are most likely to meet in Indian IT projects, with short notes on Iterative and Spiral models.

Key takeaways

  • The SDLC (software development life cycle) defines how a product moves from idea to release; the model chosen shapes when and how testing happens.
  • In Waterfall, testing is a separate phase after development, so defects found late are expensive to fix.
  • The V-Model pairs each development phase with a test level, which brings test planning forward.
  • In Agile, testing happens continuously inside short sprints, with testers working alongside developers.
  • Many real projects are hybrids. In interviews, describe what your team actually did, not just the textbook model.

What the SDLC is and why testers should care

The SDLC is the sequence of activities used to build software: requirements, design, development, testing, deployment and maintenance. An SDLC model decides the order of these activities, how long each lasts and how often they repeat.

For testers, the model answers practical questions:

  • When do I first see requirements, and how stable are they?
  • When do I get a testable build?
  • How much documentation is expected?
  • How often do we release, and how much regression is needed each time?

The software testing life cycle (STLC) runs inside whichever SDLC model the project uses. Our guide to the software testing life cycle explains the STLC phases in detail.

Waterfall model

Waterfall is a linear model: each phase finishes before the next starts. Requirements are gathered and signed off, design follows, then development, then testing, then deployment.

Where testing fits

Testing is a distinct phase after development. Testers may write test plans and test cases during earlier phases, but execution starts only when the full build is ready.

A typical example

A government department commissions a records management system with fixed, documented requirements and a contractual delivery date. The vendor follows Waterfall: six months of build, then a dedicated system testing phase, then user acceptance testing.

Pros and cons for testers

  • Pros: Clear, stable requirements; thorough documentation; well-defined test phase.
  • Cons: Defects in requirements are found late; testing time gets squeezed when development overruns; large builds mean many defects at once.

V-Model (Verification and Validation model)

The V-Model extends Waterfall by pairing each development phase on the left side of the “V” with a corresponding testing level on the right side.

Development phase (verification)Matching test level (validation)
Requirements analysisAcceptance testing
System designSystem testing
Architecture or high-level designIntegration testing
Module or low-level designUnit testing
CodingBottom of the V

Where testing fits

Test planning and design start alongside each development phase. While business analysts finalise requirements, testers prepare acceptance test scenarios. While architects design the system, testers plan system tests. Execution still happens after coding, moving up the right side of the V.

A typical example

A medical device software project or a regulated banking module, where traceability from each requirement to a test is mandatory for audits.

Pros and cons for testers

  • Pros: Early test design catches unclear requirements; strong traceability; clear entry and exit criteria for each level.
  • Cons: Still rigid; changes in requirements are costly; working software appears late.

Iterative and Spiral models

Iterative model

The product is built in repeated cycles, each producing a working, partial version. Testers test each iteration’s features and run regression on earlier ones. This model laid the foundation for Agile practices.

Spiral model

The Spiral model combines iterative development with explicit risk analysis in every cycle. Each loop includes planning, risk analysis, engineering and evaluation. It suits large, high-risk projects. Testers contribute to risk assessment and prototype evaluation, not just execution. You will rarely see pure Spiral in day-to-day project work, but it appears in interviews and certification syllabi.

Agile model

Agile is a family of approaches, with Scrum and Kanban the most common, that deliver working software in short cycles and welcome changing requirements. In Scrum, work happens in sprints of typically one to four weeks.

Where testing fits

Testing is continuous and happens inside each sprint. Testers:

  • Join backlog refinement to clarify user stories and acceptance criteria.
  • Write test scenarios while developers build the feature.
  • Test stories as soon as they are ready, often the same day.
  • Automate regression checks so each sprint does not grow the manual workload.
  • Take part in sprint reviews and retrospectives.

A typical example

A fintech startup releasing its app every two weeks. Each story has acceptance criteria agreed by the product owner, developer and tester before work starts. Automated smoke tests run on every build, and the tester decides with the team whether a story meets the definition of done. Our guide on smoke vs sanity testing explains the quick checks used in such fast cycles.

Pros and cons for testers

  • Pros: Early and frequent feedback; testers influence requirements; defects are cheaper to fix; varied work.
  • Cons: Less documentation; testing can be squeezed at sprint end; regression load grows without automation; requires strong communication.

SDLC models compared

AspectWaterfallV-ModelIterative or SpiralAgile
FlowLinearLinear with paired test levelsRepeated cyclesShort continuous cycles
Testing startsAfter developmentPlanning starts early, execution after codingEach iterationFrom day one of each sprint
Requirement changesCostlyCostlyManageableExpected
DocumentationHeavyHeavyModerateLight, just enough
Tester’s roleSeparate phaseEarly planning plus phasesPer-iteration testing and risk inputEmbedded team member
Typical useFixed-scope contractsRegulated or safety-criticalLarge or high-risk productsMost product and digital projects

Hybrid models in real projects

Many Indian service projects follow a hybrid. A client may run Agile sprints for development but require a formal system integration testing phase and UAT before each quarterly release. Banks often combine Agile delivery with V-Model style documentation for audit.

As a tester in a hybrid setup, you might write stories and test within sprints, then also run a hardening sprint or regression cycle before release, and maintain a traceability matrix for compliance. Knowing the pure models helps you understand why each of these steps exists.

How to answer SDLC model questions in interviews

Interviewers usually ask “Which SDLC model does your project follow?” followed by “What is your role in it?” A strong answer:

  1. Name the model honestly. “We follow Scrum with two-week sprints, plus a regression cycle before each monthly release.”
  2. Describe your activities. Refinement meetings, test design, execution, automation, defect triage.
  3. Mention a trade-off. “Requirements change mid-sprint sometimes, so I keep test cases lightweight and update them as stories evolve.”

Also be ready for comparisons: Waterfall vs Agile, V-Model vs Waterfall, and verification vs validation. These appear frequently in manual testing interview questions, and Agile-specific questions are covered in our Agile interview questions for testers. The ISTQB website syllabi describe sequential and iterative development models if you are preparing for certification.

🚀 Looking for QA roles in Agile teams?

QA Jobs India shares 100+ fresh QA & software testing openings every morning — manual, automation, API and remote roles.

See today’s QA jobs →

FAQs

What are the main SDLC models?

The commonly discussed SDLC models are Waterfall, V-Model, Iterative, Spiral and Agile (including Scrum and Kanban). Some lists also include the Incremental, RAD and Big Bang models.

Which SDLC model is best for testing?

No single model is best. Agile gives earlier and more frequent feedback, which usually helps quality. The V-Model suits regulated projects needing strong traceability. The best model depends on the project’s requirements, risk and constraints.

What is the difference between SDLC and STLC?

SDLC covers the full life cycle of software development, from requirements to maintenance. STLC covers the testing activities within it: requirement analysis, test planning, test design, environment setup, execution and closure.

What is the difference between the V-Model and Waterfall?

Both are sequential, but the V-Model explicitly pairs each development phase with a testing level and starts test planning early. In Waterfall, testing is treated mainly as a single phase after development.

Do testers need to know SDLC models for interviews?

Yes. Fresher and manual testing interviews often include questions on SDLC models, especially Waterfall, V-Model and Agile. Experienced candidates are asked how testing worked in their actual project model.

Conclusion

Write a five-line description of the SDLC model your current or most recent project used, including where testing started and one problem the model caused. Practise saying it aloud; it is one of the most predictable interview questions, and a specific answer stands out immediately.

SIGN UP ONCE
Once you sign up, you get all this
Sign up now
  • 100+ fresh QA jobs daily + Direct HR email IDsLive every morning at 9 AM — apply straight to HR
  • Weekly Mega Job Fair800+ QA jobs from India & around the world, every week
  • Certified QA coursesUp to 3 courses included · all 17 for ₹500
  • AI ATS Resume BuilderFree resume points included
  • Full LinkedQA feedEvery post, fully unblurred
  • Complete QA Material libraryInterview Q&A, cheat sheets, templates & roadmaps

Instant activation right after payment · One login for jobs, courses, resume & LinkedQA

💎 Get every QA opening, every day

Join QA Jobs India Premium for 100+ verified QA jobs daily with HR contact details.

✓ You're subscribed — job alerts arrive daily at 9 AM
Scroll to Top