This document provides advice for teams considering adopting Agile practices. It lists reasons both for and against starting an Agile process. It then provides recommendations for implementing Agile in different project types and common best practices. Finally, it addresses potential adoption issues and asks if the reader has any other questions.

1. War for Agile Alimenkou Mikalai [email_address] http://agilecoaching.com.ua 28.06.2008

2. Stop and think! To start or not to start? Your team already has good enough process You don’t have any practical experience in Agile It is your temporary project You are only one person who like and understand Agile principles

3. Why to start? You don’t like Overtimes Buggy code External plan Tons of documentation … You like Work for fun Team collaboration Build useful software/product Improving yourself … .

4. Fixed price projects Make initial estimations more Agile Reduce time to first deadline Use Agile internally to predict failures Introduce internal releases Show benefits of Agile process Try to use popularity of Scrum

5. Hourly paid projects Use team as interface with Agile based implementation Introduce internal process and make it company standard Make proxy for external dependencies Reduce overtimes

6. Distributed projects Move to separate teams approach Often mix teams Extend communication environment Use special Agile tools

7. Internal projects Find person suitable for customer role Take part in initial project planning Proxy customer Make internal demos and deadlines

8. Common best practices Hide team from external pressure Use all engineer practices Experiment and let team to make decision Reuse team members for different roles Build the trust Be ready to any questions

9. Adoption issues No other Agile project exists Don’t use word Agile Ask for a chance Start with engineering practices Find holes in existing process Low authority to make changes Be an example Show benefits to team members Find support from management Be reliable and get the authority

10. Adoption issues Unfriendly environment for Agile Adopt practices for yourself and share results Make job done with highest quality Show hidden issues Bad previous experience with Agile Don’t use word ‘Agile’ Try to include only some practices Have answer to each question

11. Any questions?