No Surprises: Getting Things Done® in QA, Release and Technical Delivery

No Surprises is a book about control in software delivery, but not the kind created by adding more process, more dashboards or more status meetings.It takes the core principles of Getting Things Done(R) and examines what happens when they are applied beyond personal organisation, inside QA, release management and technical delivery. The focus is not on productivity in the usual sense. It is on whether commitments, evidence, dependencies, assumptions and decisions remain usable as work moves across people, teams and systems.A defect can be logged and still have no real owner. A dependency can have a date without a credible commitment behind it. Test evidence can be current and no longer apply to the release candidate being discussed. A risk can be marked accepted without any clear record of who accepted it, on what basis, or whether the conditions have since changed.These are ordinary delivery problems, and they are difficult precisely because nothing appears obviously broken. The information often exists. The harder question is whether enough of the underlying reality has survived for somebody to make the next action or release decision without reconstructing the previous three days from chat, Jira and memory.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. It examines where the analogy holds, where it becomes insufficient, and what experienced practitioners need to notice when local organisation and systemic reliability begin to diverge.Written for QA Leads, Test Managers, Release Managers, Technical Delivery Managers and other practitioners working in complex software environments, No Surprises is about making delivery information trustworthy enough to act on. Not perfect. Not complete. Just honest enough that the next decision is based on the current state of the work rather than the story the process happens to be telling.