The Rules of Extreme Programming Extreme Programming Planning Full Size Extreme Programming Project Ted Scenarios User stories are written. User Stories Nee User Biory Project vilechy Release planning creates the release Literal Architectural Mataghe Release PI . Iteration Writen, Acceptance Approved Small Planning Tests schedule. Spike Releases Uncertain Centden Make frequent small releases The project is divided into iterations. Spike Iteration planning starts each iteration. Coding Managing The customer is always available. Give the team a dedicated open work Code must be written to agreed standards. Code the unit test first. space. All production code is pair programmed. Set a sustainable pace. A stand up meeting starts each day. Only one pair integrates code at a time. Integrate often The Project Velocity is measured. Set up a dedicated integration computer. Move people around. Fix XP. when it breaks. Use collective ownership. Designing Testing All code must have unit tests. Simplicity. All code must pass all unit tests before it Choose a system metaphor. can Use CRC cards for design sessions. Create spike solutions to reduce risk. be released. No functionality is added early. When a bug is found tests are created. Refactor whenever and wherever possible. Acceptance tests are run often and the score is published