← QA Library
Chapter 9 / 9 · 7 min read

SDLC, STLC and processes

How software is built and where testing fits: life cycles, development models, Agile and Scrum, and practices such as TDD and BDD.

Testing doesn't happen in a vacuum. Its timing, depth and style depend on how the team builds software. Understanding the process helps testers join early, ask the right questions and avoid becoming a bottleneck at the end.

Software development life cycle (SDLC)

Whatever the model, software goes through the same stages: requirements (what and why), design (how), implementation (code), testing (does it work and is it right), deployment (release to users) and maintenance (fixes and improvements). Models differ in how these stages are ordered and how often they repeat.

ModelHow it worksTesting in it
WaterfallStages run once, one after anotherTesting comes late; changes are expensive
V-modelEach development stage has a matching test levelTest planning starts early, per level
Iterative / incrementalProduct grows in repeated cyclesTesting in every cycle, regression grows
Agile (Scrum, Kanban)Short iterations, constant feedbackTesting is continuous and shared by the team

Software testing life cycle (STLC)

Requirements analysisTest planningTest designEnvironment setupExecutionClosure
The testing life cycle runs inside every release or sprint.
  1. Requirements analysis: what can be tested, what is unclear, what is risky
  2. Test planning: scope, approach, effort, environments, schedule
  3. Test design: checklists, test cases, test data, automation
  4. Environment setup: test servers, devices, accounts, data
  5. Execution: running tests, reporting bugs, re-testing fixes
  6. Closure: report, lessons learned, updating the regression suite

Scrum in one table

ElementWhat it isQA's role
Product backlogOrdered list of everything the product might needHelp write testable stories and acceptance criteria
Sprint (1–4 weeks)Fixed time box to deliver a usable incrementTest stories as soon as they're ready
Sprint planningThe team chooses work for the sprintEstimate testing effort, flag risks
Daily scrum15-minute syncRaise blockers early
Sprint reviewDemo to stakeholdersShow quality status honestly
RetrospectiveHow can we work better?Propose process improvements

Definition of Ready says when a story can enter a sprint (clear, small, with acceptance criteria). Definition of Done says when it's finished (tested, reviewed, releasable). Kanban drops fixed sprints in favour of a continuous flow with limits on work in progress; QA columns make testing bottlenecks visible.

Test-first practices

  • TDD (test-driven development): write a failing unit test, write code to pass it, refactor
  • BDD (behaviour-driven development): describe behaviour in examples (Given/When/Then) agreed by business, developers and QA, then automate them
  • ATDD (acceptance test-driven development): agree acceptance tests before development starts
  • Shift-left: move testing activities as early as possible; shift-right: learn from production through monitoring, feature flags and gradual rollouts

We show how this looks in a real sprint in Shift-left in practice.

In a healthy process, quality is everyone's job and QA is the person who makes it visible.