From Waterfall to Agile: 7 tips for Transforming Test Organization
summary
A government system with ~19,000 internal users, millions external and one-third of national budget runs through ~300–400 systems and forces huge eight‑week acceptance tests; moving to continuous small releases and killing fixed‑price, contract‑heavy projects cuts release consequence and enables quicker feedback. Reducing from 30 test environments and forcing teams to own environments makes about 70% of errors — mostly data and environment issues — disappear, shifts testers into technical team roles, and replaces gatekeeping with shared quality and trust.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:20Identity
- 2:34Contracts
- 4:17Unique systems
- 5:33Project logic
- 7:30Projects
- 9:55Software Delivery
- 10:26Acceptance Tests
- 15:41Share Responsibility
- 16:46Continuous Delivery
- 19:37User Feedback
- 23:15Quality People
- 24:02Test Environment
- 25:49Reduce Complexity
- 27:02Agents of distrust
- 28:07Trust
- 29:02Summary
- 30:12Our journey
related talks
30mA Test Team's Unexpected Journey from Waterfall to Agile
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
37mFrom Waterfall to Agile
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
09m“Leading a Testing Revolution”
44mCan you be agile and compliant?
40mScaling testing & test automation without losing control
24mImproving Development Quality and Speed with Agile Testing