Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

ScrumDay 2014 - Développer des produits avec des équipes distribuées - Alexis Monville

872 views

Published on

ScrumDay 2014 - Développer des produits avec des équipes distribuées - Alexis Monville - Avril 2014

Published in: Business
  • Be the first to comment

  • Be the first to like this

ScrumDay 2014 - Développer des produits avec des équipes distribuées - Alexis Monville

  1. 1. Alexis Monville
 Développer des produits avec des équipes distribuées
  2. 2. MERCI À NOS SPONSORS
  3. 3. 4
  4. 4. 4 libertés
  5. 5. 4 libertés • utiliser • étudier • modifier • distribuer
  6. 6. #AOSWay @alexismonville @ayeba Alexis Monville
  7. 7. Alexis Monville #AOSWay @alexismonville @ayeba @enovance
  8. 8. #ScrumDayFr #AOSWay @alexismonville @ayeba @enovance
  9. 9. Culture #agile #opensource inspect and adapt release early release often transparency build with stake holders small teams autonomy users are co-developers collaboration communication customer satisfaction continuous delivery short iterations trust technical excellence sustainable pace self organizing simplicity outside in inside out version control feedbacks continuous improvement responding to change working software source code published available to the public respect
  10. 10. The OpenStack Open Source Cloud Mission:
 to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.
  11. 11. Computing Networking Storing
  12. 12. Cloud Operating System
  13. 13. Who?
  14. 14. Who?
  15. 15. and a lot more...
  16. 16. 15834+ people 136+ Countries 850+ Companies $10+ million funding
  17. 17. analytics?
  18. 18. ohloh.net
  19. 19. Accueil
  20. 20. What Does Openness Mean?
  21. 21. feedback
  22. 22. How to contribute?
  23. 23. Principes
  24. 24. Principes
  25. 25. Outils
  26. 26. Outils • mailing lists • IRC • Wiki • Launchpad • …
  27. 27. Release Cycle
  28. 28. Release Cycle • Cycle de 6 mois avec des jalons intermédiaires • 4 phases principales • Planning • Implementation • Pre-Release • Release
  29. 29. Liberté ?
  30. 30. Release Cycle • Note: Each core project is free to choose a different release cycle contents, as long as they submit a version for the common OpenStack release at the end of the cycle. However, unless they have a good reason to differ, they are strongly encouraged to follow the common plan that is described in this document.
  31. 31. Agile ?
  32. 32. Release Cycle • Note: Nothing prevents you to do a particular task outside of the designated stages.You can design during the QA stage. You can write new code on release week. The release cycle just gives you a general idea of what's the general team focus, it is not meant to restrict you in any way.
  33. 33. Austin
  34. 34. Bexar
  35. 35. Cactus
  36. 36. Diablo
  37. 37. Essex
  38. 38. Folsom
  39. 39. Grizzly
  40. 40. Havana
  41. 41. Icehouse
  42. 42. Juno
  43. 43. Release Cycle F G H planning Openstack
 Design
 Summit G-1 G-2 G-3 RC planning H-1 H-2 H-3 RC Openstack
 Design
 Summit 6 mois 6 mois
  44. 44. Rythme 3 months 6 months 2 weeks second
  45. 45. Planning
  46. 46. Planning • 4 weeks to: • Design • Discuss • Target
  47. 47. Blueprints
  48. 48. Blueprints
  49. 49. Bugs
  50. 50. Project Technical Leads • Project Technical Leads (PTL) • A PTL is the elected technical leader of a given OpenStack core project. • At the end of the planning stage the PTLs triage the submitted blueprints and sets Priority for them. • The blueprints with a priority above Low will be tracked by Release Management throughout the cycle.
  51. 51. Product Owner • 1 product owner par équipe de développement produit • les fonctionnalités des produits eNovance en connexion avec les fonctionnalités des logiciels libres les constituants
  52. 52. Meetings • Réunion quotidienne, planning, revue, rétro : • video conférence • utilisation d’outil en ligne
  53. 53. Summit
  54. 54. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  55. 55. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  56. 56. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  57. 57. Summit • Every 6 months the Design Summit gather users and developers • The Summit closes the Planning phase
  58. 58. Distribué
  59. 59. 900+ developers
  60. 60. Implémentation
  61. 61. Qualité
  62. 62. 2 +2, 0 -2
  63. 63. Apprentissage
  64. 64. Core Devs • You need 2 +2 from Core Developers • Core Developers are co-opted among the contributors
  65. 65. Tests
  66. 66. Versions
  67. 67. branch model
  68. 68. Livrer en continu • Le déploiement et la mise à jour des produits sont testés en continu sur une architecture de référence
  69. 69. En conclusion… Communication Feedback Respect
 …
  70. 70. • Créer les conditions de la collaboration • temps passé ensemble • outillage de communication confortable • vision produit traduit dans les outils du projet • pratique d’ingénierie : tests, intégration continue, automatisation • apprentissage du feedback
  71. 71. Alexis Monville #AOSWay @alexismonville @ayeba @enovance
  72. 72. The Agileand Open SourceWay
  73. 73. Merci !
  74. 74. MERCI À NOS SPONSORS

×