Julian Cambridge

Julian Cambridge is an Agile and Software Testing trainer, consultant, and coach based in London, with over a decade of experience delivering high-impact learning and transformation across global organisations . He has worked with institutions including WIPO at the United Nations in Geneva, NATO in Belgium, Arab National Bank and Al Rajhi Bank in Riyadh, as well as major UK and international private-sector clients .

 

Over the course of his career, Julian has delivered more than 100 professional courses spanning Agile, Scrum, Kanban, software testing, Agile testing, and product development . He has trained thousands of professionals across Europe and the Middle East, equipping teams to modernise delivery, improve quality, and embed practical Agile ways of working . His approach combines deep industry experience with clarity of instruction, translating complex technical and organisational concepts into practical, outcome-focused capability.

 

Julian’s corporate background includes senior testing and quality leadership roles with Royal Mail, Allwyn (UK National Lottery), Dr Martens, CIPD, Brewin Dolphin, Investec, Shawbrook Bank, and Camelot . This hands-on experience informs his teaching, ensuring that his training is grounded in real-world delivery challenges across banking, financial services, retail, government, and regulated environments.

The V-Model is often referenced, frequently misunderstood, and rarely explored through the lens of intent.

 

In this session, Julian Cambridge examines the origins of the V-Model and the thinking that led to its creation. At a time when software projects were struggling with late defect discovery, weak traceability, and costly rework, a structural shift was needed — not simply a new sequence of phases, but a clearer relationship between development decisions and their validation.

 

This talk explores the conditions that made such a model necessary, the structural principles it introduced, and the enduring value of pairing definition with verification. Through a clear walkthrough of the V-Model diagram, Julian explains the symmetry between the left side — requirements, system design, architecture, and module design — and the right side — acceptance, system, integration, and unit testing.

 

Rather than presenting the V-Model as a historical artefact, this session reframes it as a disciplined approach to confidence: for every decision made during development, there must be a deliberate method to prove it works.

 

Whether working in regulated industries or modern iterative environments, the principles embedded in the V-Model remain highly relevant.

 

This session is ideal for quality professionals, testers, architects, and leaders seeking to strengthen alignment between intent and validation in their software systems.