Conférence sur l'Agilité présentée par Yann Klis à Exia/Cesi Strasbourg en février 2010

1. Yann Klis, Exia Cesi, 4 février 2010 Agilité

2. Agile Manifesto

3. 4 valeurs

4. Individuals and interactions over processes and tools

5. Working software over comprehensive documentation

6. Customer collaboration over contract negotiation

7. Responding to change over following a plan

8. 12 principes

9. 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

10. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

11. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

12. 4. Business people and developers must work together daily throughout the project.

13. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

14. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

15. 7. Working software is the primary measure of progress.

16. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

17. 9. Continuous attention to technical excellence and good design enhances agility.

18. 10. Simplicity -- the art of maximizing the amount of work not done -- is essential.

19. 11. The best architectures, requirements, and designs emerge from self-organizing teams.

20. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

21. Plusieurs Méthodes Agiles

23. “ Simplicity”

24. “ Feedback”

25. “ Courage”

26. “ Respect”

27. Tests unitaires, égalité des membres de l'équipe, intégration continue, Pair Programming, TDD, cartons, Use Case, Milestone, etc

29. “ Eliminate waste”

30. “ Amplify learning”

31. “ Decide as late as possible”

32. “ Deliver as fast as possible”

33. “ Empower the team”

34. “ Build integrity in”

35. “ See the whole”

37. “ Critical Chain” / “La Chaîne Critique”, Goldratt

38. Différentes étapes des matières premières jusqu'à la création du produit

39. Garder la chaîne de production fonctionnelle

40. Identifier les points consommateurs en temps

41. Agilité dans-la-vraie-vie™

43. Tickets, Pair Programming, Use Case, Backlog, MoSCoW, SUM

44. Tests (unitaires, fonctionnels, intégration, etc)

45. Chaîne de production (mon grand dada)

46. Plugin novelys_hacks ( db:dump_and_restore )

47. Gestion des exceptions (hoptoad)

49. Fixer le ticket

50. Ecrire le test

51. Committer le changement (avec le numéro de ticket)

52. Fermer le ticket

55. Fixer la build

56. Les autres

57. Et le client dans tout ça ? Résistance au changement Obligation contractuelle Accès aux outils appropriés

58. Ressources http://agilemanifesto.org/ http://www.extremeprogramming.org/ http://agiletour.org/ http://escalators.novelys.com