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

2. Alexis Monville
Développer des produits
avec des équipes
distribuées

3. MERCI À NOS SPONSORS

6. 4

7. 4 libertés

8. 4 libertés
• utiliser
• étudier
• modifier
• distribuer

11. #AOSWay
@alexismonville
@ayeba
Alexis Monville

12. Alexis Monville
#AOSWay
@alexismonville
@ayeba
@enovance

13. #ScrumDayFr
#AOSWay
@alexismonville
@ayeba
@enovance

14. 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

16. 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.

17. Computing Networking Storing

18. Cloud Operating System

20. Who?

21. Who?

22. and a lot more...

23. 15834+ people
136+ Countries
850+ Companies
$10+ million funding

24. analytics?

25. ohloh.net

26. Accueil

27. What Does
Openness
Mean?

29. feedback

30. How to
contribute?

32. Principes

33. Principes

34. Outils

35. Outils
• mailing lists
• IRC
• Wiki
• Launchpad
• …

36. Release
Cycle

37. Release Cycle
• Cycle de 6 mois avec des jalons
intermédiaires
• 4 phases principales
• Planning
• Implementation
• Pre-Release
• Release

38. Liberté ?

39. 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.

40. Agile ?

41. 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.

42. Austin

43. Bexar

44. Cactus

45. Diablo

46. Essex

47. Folsom

48. Grizzly

49. Havana

50. Icehouse

51. Juno

52. 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

54. Rythme
3 months
6 months
2 weeks
second

55. Planning

56. Planning
• 4 weeks to:
• Design
• Discuss
• Target

57. Blueprints

58. Blueprints

59. Bugs

60. 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.

61. 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

62. Meetings
• Réunion quotidienne, planning, revue,
rétro :
• video conférence
• utilisation d’outil en ligne

63. Summit

64. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com

65. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com

66. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com

67. Summit
• Every 6 months the
Design Summit gather
users and developers
• The Summit closes the
Planning phase

68. Distribué

69. 900+
developers

70. Implémentation

72. Qualité

73. 2 +2, 0 -2

75. Apprentissage

76. Core Devs
• You need 2 +2 from Core Developers
• Core Developers are co-opted among the
contributors

78. Tests

82. Versions

83. branch model

84. Livrer en continu
• Le déploiement et la mise à jour des
produits sont testés en continu sur une
architecture de référence

85. En conclusion…
Communication
Feedback
Respect
…

86. • 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

87. Alexis Monville
#AOSWay
@alexismonville
@ayeba
@enovance

88. The
Agileand
Open
SourceWay

89. Merci !

90. MERCI À NOS SPONSORS