By Andreea Vitan · 2026 · Reliable evidence, ownership and decisions across software delivery
No Surprises examines control in software delivery through the principles of Getting Things Done®, applying them beyond personal organisation to QA, release management and technical delivery.
What the book is about
The book asks whether the information behind delivery decisions remains usable as work moves between people, teams and systems. A defect may exist without meaningful ownership. A dependency may have a date without a credible commitment. Test evidence may be current but no longer apply to the release candidate under discussion.
Using the GTD principles of Capture, Clarify, Organise, Reflect and Engage as a starting point, the book moves from individual control to team coordination and then to release and programme-level reliability. The emphasis is not on productivity for its own sake, but on making commitments, evidence, assumptions and decisions trustworthy enough to act on.
Who it is for
- QA Leads and Test Managers
- Release Managers
- Technical Delivery Managers
- Programme and project professionals working across software teams
- Practitioners responsible for dependencies, evidence, decisions and delivery risk
Topics covered
- Capture, clarification and reliable ownership
- Dependencies and commitments
- Test evidence and release-candidate relevance
- Risk acceptance and decision traceability
- Team coordination and delivery-state reliability
- Release and programme-level control
- Evidence-based QA and release decisions
Published: August 2026
Author: Andreea Vitan
Subject: QA, release management, technical delivery and Getting Things Done® principles
About the author
Andreea Vitan is a Quality Assurance Engineer, Release Manager and Test Manager with 13+ years of experience across enterprise software, financial services, banking, payments and telecom. Her work focuses on test strategy, QA governance, release readiness, risk, dependencies and evidence-based delivery decisions.
She writes about software quality, release management and technical delivery from a practitioner perspective, with particular interest in the gap between what a process reports and what the underlying delivery state can actually support.