Upload
alexis-monville
View
370
Download
0
Embed Size (px)
DESCRIPTION
ScrumDay 2014 - Développer des produits avec des équipes distribuées - Alexis Monville - Avril 2014
Citation preview
Alexis Monville
Développer des produits avec des équipes distribuées
MERCI À NOS SPONSORS
4
4 libertés
4 libertés
• utiliser
• étudier
• modifier
• distribuer
#AOSWay @alexismonville
@ayeba
Alexis Monville
Alexis Monville#AOSWay
@alexismonville @ayeba
@enovance
#ScrumDayFr#AOSWay
@alexismonville @ayeba
@enovance
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 publicrespect
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.
Computing Networking Storing
Cloud Operating System
Who?
Who?
and a lot more...
15834+ people136+ Countries
850+ Companies
$10+ million funding
analytics?
ohloh.net
Accueil
What Does Openness
Mean?
feedback
How to contribute?
Principes
Principes
Outils
Outils
• mailing lists
• IRC
• Wiki
• Launchpad
• …
Release Cycle
Release Cycle
• Cycle de 6 mois avec des jalons intermédiaires
• 4 phases principales
• Planning
• Implementation
• Pre-Release
• Release
Liberté ?
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.
Agile ?
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.
Austin
Bexar
Cactus
Diablo
Essex
Folsom
Grizzly
Havana
Icehouse
Juno
Release Cycle
F G H
planning
OpenstackDesignSummit
G-1 G-2 G-3
RC planning
H-1 H-2 H-3
RC
OpenstackDesignSummit
6 mois 6 mois
Rythme
3 months
6 months
2 weekssecond
Planning
Planning
• 4 weeks to:
• Design
• Discuss
• Target
Blueprints
Blueprints
Bugs
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.
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
Meetings
• Réunion quotidienne, planning, revue, rétro :
• video conférence
• utilisation d’outil en ligne
Summit
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
Summit
• Every 6 months the Design Summit gather users and developers
• The Summit closes the Planning phase
Distribué
900+developers
Implémentation
Qualité
2 +2, 0 -2
Apprentissage
Core Devs
• You need 2 +2 from Core Developers
• Core Developers are co-opted among the contributors
Tests
Versions
branch model
Livrer en continu
• Le déploiement et la mise à jour des produits sont testés en continu sur une architecture de référence
En conclusion…Communication
Feedback Respect
…
• 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
Alexis Monville#AOSWay
@alexismonville @ayeba
@enovance
The Agile
and Open
Source Way
Merci !
MERCI À NOS SPONSORS