Managing the Test Activities Across the Software Development Lifecycle
This domain tests how test management adapts to different SDLC models, test levels and delivery cadences. Expect questions on aligning test activities with sequential, iterative, incremental and continuous delivery contexts without losing appropriate verification and evidence.
SDLC models and test levels
Sequential models such as the V-model emphasize early test design, verification and validation, and formal entry/exit criteria. Iterative and agile models emphasize continuous feedback, backlog refinement and regression automation. Test levels are component, component integration, system, system integration and acceptance. Test types include functional, non-functional, structural and change-related. A test level is not a test type; a level can host several types.
Managing across the lifecycle
The ISO 29119 test process covers planning, monitoring and control, analysis, design, implementation, execution, and closure. In agile, the test manager supports release and sprint planning, definition of done, daily coordination and retrospectives. DevOps adds CI/CD, continuous testing, test environments as code and fast feedback. Entry/exit criteria, regression suites and test data must be planned per level, and shift-left moves analysis and design earlier.
Worked example
An agile product releases weekly but faces a quarterly regulatory audit. The approach runs automated component and API regression in CI, risk-based system and exploratory testing each sprint, and formal acceptance evidence quarterly. Traceability is maintained in the backlog. Reasoning: continuous feedback supports speed, formal gates satisfy audit, and automation protects regression at release cadence.
Traps
Do not apply V-model gates mechanically to agile delivery. Do not skip system testing because unit tests pass. Do not confuse test levels with test types. Do not treat DevOps as documentation-free testing.