Agilité, Exia/Cesi, Février 2010

528 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
528
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agilité, Exia/Cesi, Février 2010

  1. 1. Yann Klis, Exia Cesi, 4 février 2010 Agilité
  2. 2. Agile Manifesto
  3. 3. 4 valeurs
  4. 4. Individuals and interactions over processes and tools
  5. 5. Working software over comprehensive documentation
  6. 6. Customer collaboration over contract negotiation
  7. 7. Responding to change over following a plan
  8. 8. 12 principes
  9. 9. 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  10. 10. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  11. 11. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  12. 12. 4. Business people and developers must work together daily throughout the project.
  13. 13. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  14. 14. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  15. 15. 7. Working software is the primary measure of progress.
  16. 16. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  17. 17. 9. Continuous attention to technical excellence and good design enhances agility.
  18. 18. 10. Simplicity -- the art of maximizing the amount of work not done -- is essential.
  19. 19. 11. The best architectures, requirements, and designs emerge from self-organizing teams.
  20. 20. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  21. 21. Plusieurs Méthodes Agiles
  22. 22. eXtreme Programming (XP) <ul><li>“ Communication”
  23. 23. “ Simplicity”
  24. 24. “ Feedback”
  25. 25. “ Courage”
  26. 26. “ Respect”
  27. 27. Tests unitaires, égalité des membres de l'équipe, intégration continue, Pair Programming, TDD, cartons, Use Case, Milestone, etc </li></ul>
  28. 28. Lean <ul><li>TPS
  29. 29. “ Eliminate waste”
  30. 30. “ Amplify learning”
  31. 31. “ Decide as late as possible”
  32. 32. “ Deliver as fast as possible”
  33. 33. “ Empower the team”
  34. 34. “ Build integrity in”
  35. 35. “ See the whole” </li></ul>
  36. 36. Chaîne de production <ul><li>“ The Goal” / “Le But”, Goldratt
  37. 37. “ Critical Chain” / “La Chaîne Critique”, Goldratt
  38. 38. Différentes étapes des matières premières jusqu'à la création du produit
  39. 39. Garder la chaîne de production fonctionnelle
  40. 40. Identifier les points consommateurs en temps </li></ul>
  41. 41. Agilité dans-la-vraie-vie™
  42. 42. Agilité chez Novelys <ul><li>XP, puis Scrum, puis Lean
  43. 43. Tickets, Pair Programming, Use Case, Backlog, MoSCoW, SUM
  44. 44. Tests (unitaires, fonctionnels, intégration, etc)
  45. 45. Chaîne de production (mon grand dada)
  46. 46. Plugin novelys_hacks ( db:dump_and_restore )
  47. 47. Gestion des exceptions (hoptoad) </li></ul>
  48. 48. Agilité chez Novelys <ul><li>Workflow sur les tickets </li><ul><li>Choisir un ticket qui n'est pas assigné
  49. 49. Fixer le ticket
  50. 50. Ecrire le test
  51. 51. Committer le changement (avec le numéro de ticket)
  52. 52. Fermer le ticket </li></ul></ul>
  53. 54. Agilité chez Novelys <ul><li>Ordre d'importance des tickets </li><ul><li>Ceux provenant de la production ou de staging
  54. 55. Fixer la build
  55. 56. Les autres </li></ul></ul>
  56. 57. Et le client dans tout ça ? Résistance au changement Obligation contractuelle Accès aux outils appropriés
  57. 58. Ressources http://agilemanifesto.org/ http://www.extremeprogramming.org/ http://agiletour.org/ http://escalators.novelys.com

×