Because enterprise applications are highly interconnected, development in stages puts a strain on the implementation and execution of automated testing. Service virtualization can be introduced to validate work in progress while reducing the dependencies on components and third-party technologies still under development.

You may feel you don't have time to write unit tests, but you really don't have time not to. Steve Poling makes the case that writing tests first not only will yield better code, but will help you get that code working right sooner. Here's how using a test-first approach changes your thinking about coding, lets you see mistakes immediately, and helps you create more testable code.

In this interview, Alon Eizenman, the CTO and cofounder at SeaLights Technologies, discusses his many experiences with startup companies, how software teams are adapting to the current demand for speed, and why you need data before you take testing actions.

"Move fast and break things” tells quite a story of the relationship between speed and agile. Speed has been a driver in our industry before it was even an industry. Books promise that certain frameworks can deliver twice as much in half the time, yet teams still struggle delivering what's expected of them. This session describes a six-month case study of a multi-team transformation. The orders were to make the teams deliver faster, but they were consistently missing deadlines. Frustration was on the rise. Only after taking the time to understand what they meant by "faster" could the teams improve—and the solution ended up being to slow down. Chris Murman will help you learn how to make the case to slow down, work in increments, deliver frequently, and delight customers. He will explain which metrics to use to measure progress, patterns of successful teams, and the necessary coaching stances.