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.
| Model | How it works | Testing in it |
|---|---|---|
| Waterfall | Stages run once, one after another | Testing comes late; changes are expensive |
| V-model | Each development stage has a matching test level | Test planning starts early, per level |
| Iterative / incremental | Product grows in repeated cycles | Testing in every cycle, regression grows |
| Agile (Scrum, Kanban) | Short iterations, constant feedback | Testing is continuous and shared by the team |
Software testing life cycle (STLC)
- Requirements analysis: what can be tested, what is unclear, what is risky
- Test planning: scope, approach, effort, environments, schedule
- Test design: checklists, test cases, test data, automation
- Environment setup: test servers, devices, accounts, data
- Execution: running tests, reporting bugs, re-testing fixes
- Closure: report, lessons learned, updating the regression suite
Scrum in one table
| Element | What it is | QA's role |
|---|---|---|
| Product backlog | Ordered list of everything the product might need | Help write testable stories and acceptance criteria |
| Sprint (1–4 weeks) | Fixed time box to deliver a usable increment | Test stories as soon as they're ready |
| Sprint planning | The team chooses work for the sprint | Estimate testing effort, flag risks |
| Daily scrum | 15-minute sync | Raise blockers early |
| Sprint review | Demo to stakeholders | Show quality status honestly |
| Retrospective | How 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.