If an iteration is the heartbeat of an agile development process, then Iteration Zero (IZero) creates the heart. While you can (and should) retrospect and adjust throughout the software lifecycle, few things are as valuable as a good start. In this talk, you will learn how we run Iteration Zero at Relevance.

The purpose of IZero is to prepare all stakeholders, so that Iteration One can begin normal iteration pace, heading in the right direction. In this talk, we will visit each of the four principles of the Agile Manifesto, and show how to establish them in IZero.

AM #1. Individuals and interactions over processes and tools. In IZero, you should identify the team roles, and find the right people to fill them. You should create places and times (both physical and virtual) to maximize contact and interaction.

AM #2. Working software over comprehensive documentation. In IZero, you establish the practices you will use to create working software, which may include test-driven development, pair programming, continuous integration, code review, various metrics, and more.

AM #3 Customer collaboration over contract negotiation. In IZero, create the shared vision, and commit to keeping it collaborative. Define a flow that will work for all stakeholders, that can take ideas -> planning -> development -> testing -> acceptance.

AM #4 Responding to change over following a plan. IZero sets the initial parameters, but also prepares for change. Decide how to use standups, iteration planning meetings, iteration summaries, and retrospectives to adapt to change throughout the project.

IZero does not have to be a blank slate. Once you have practiced it, you will build up a stock of IZero habits that work for your team, and draw on it for future projects.