This session will explore how much time and energy we currently waste when writing software, simply to answer two simple questions:

* "Does my code work?"
* "Did I just break something?"

As we explore these pain-points, Test-Driven Development will emerge as a surprisingly efficient workflow putting us in a position to ship code sooner, more often, on a sustained basis.

Most of us are "surprised" by this, as it just seems very counter-intuitive to write a test before even having written any code. Yet, as we explore this workflow, we start uncovering the efficiencies that we gain, and things become fascinating.

As a result, we will show what it "feels" like to write software that responds to change, as a true sensation of agility emerges, driven not by Scrum, but instead, driven by better code.