The

Agile
and
Open
Source
Way
merci à nos sponsors !
Agile?
Agile
• Continuous improvement	

• Individuals and interactions	

• Working software	

• Customer collaboration	

• Respon...
Open Source?
Open Source
• source code is published	

• made available to the public	

• enabling anyone to copy, modify and

redistrib...
≠
=
?
Who?
Alexis Monville
#AOSWay	

@alexismonville	

!
Alexis Monville
#AOSWay	

@alexismonville	

@ayeba
Alexis Monville
#AOSWay	

@alexismonville	

@ayeba	

@enovance
#frenchsug
#AOSWay	

@alexismonville	

@ayeba	

@enovance
merci à nos sponsors !
Open Source = Agile ?
Open Source = Agile ?
• Open Source shares the same values:	

• Individuals and interactions	

• Working software	

• Cust...
Principles behind...
• Our highest priority is to satisfy the customer through early and continuous delivery of valuable s...
Yes!
• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welco...
But...
• Not the same principles and practices:	

• No day to day face to face conversation	

• No collocated teams	

• In...
mix
Agile and
Open Source
Virtual Gemba Walk
The OpenStack Open Source Cloud Mission:	

to produce the ubiquitous Open Source Cloud Computing
platform that will meet t...
Computing

Networking

Storing
Cloud Operating System

http://www.openstack.org
Who?

http://www.openstack.org/foundation/companies/
Who?

http://www.openstack.org/foundation/companies/
and a lot more...
12120+ people
130 Countries
http://www.stackalytics.com/
What Does
Openness Mean?
Scale
Onboarding
Onboarding
• How to...	

• Ask...	

• Wiki...	

• IRC, mailing list... 	

• Buddy...	

• ...
How?

https://wiki.openstack.org/wiki/How_To_Contribute
Communication

https://wiki.openstack.org/wiki/IRC
Release
Release Cycle
Release Cycle
Release Cycle
•

A coordinated 6-month release cycle with
frequent development milestones. 	


• The Release Cycle is made...
Free?
Release Cycle
• Note: Each core project is free to choose a

different release cycle contents, as long as
they submit a ve...
Agile?
Release Cycle
• Note: Nothing prevents you to do a

particular task outside of the designated
stages.You can design during...
Austin
Bexar
Cactus
Diablo
Essex
Folsom
Grizzly
Havana
Icehouse
Release Cycle
Openstack

Design

Summit

Openstack

Design

Summit

F

G

planning

RC

G-1

G-2 G-3
6 mois

H

planning

...
Planning
Planning
• 4 weeks to:	

• Design	

• Discuss	

• Target
https://wiki.openstack.org/wiki/ReleaseCycle
Tenets

https://wiki.openstack.org/wiki/BasicDesignTenets
Blueprints

https://wiki.openstack.org/wiki/Blueprints
Blueprints

https://blueprints.launchpad.net/ceilometer/+spec/api-v2-improvement
Bugs

https://bugs.launchpad.net/ceilometer
PTLs
• Project Technical Leads.	

• A PTL is the elected technical leader of a given
OpenStack core project.	


• At the e...
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aa...
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aa...
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aa...
Summit
• Every 6 months the

Design Summit gather
users and developers	


• The Summit closes the
Planning phase

http://w...
Quality
Implementation
800+
2 +1, 0 -1
Core Devs
• You need a +1 from a Core Developer	

• Core Developers are co-opted among the
contributors
• Teams are distributed between Paris and
Montreal Offices, plus people working
remotely from home (somewhere...)	


• They...
Questions?
Thank you!
Alexis Monville
#AOSWay	

@alexismonville	

!

stay tuned: 

http://www.the-agile-and-open-source-way.com/
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
French Scrum User Group @Google - The Agile and Open Source Way
Upcoming SlideShare
Loading in …5
×

French Scrum User Group @Google - The Agile and Open Source Way

2,423 views

Published on

Support de la présentation donnée lors de la soirée du French Scrum User Group @Google le 4 novembre 2013.

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,423
On SlideShare
0
From Embeds
0
Number of Embeds
1,074
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

French Scrum User Group @Google - The Agile and Open Source Way

  1. 1. The Agile and Open Source Way
  2. 2. merci à nos sponsors !
  3. 3. Agile?
  4. 4. Agile • Continuous improvement • Individuals and interactions • Working software • Customer collaboration • Responding to change Agile manifesto: http://agilemanifesto.org
  5. 5. Open Source?
  6. 6. Open Source • source code is published • made available to the public • enabling anyone to copy, modify and redistribute the source code without paying royalties or fees http://en.wikipedia.org/wiki/Open_source
  7. 7.
  8. 8. =
  9. 9. ?
  10. 10. Who?
  11. 11. Alexis Monville #AOSWay @alexismonville !
  12. 12. Alexis Monville #AOSWay @alexismonville @ayeba
  13. 13. Alexis Monville #AOSWay @alexismonville @ayeba @enovance
  14. 14. #frenchsug #AOSWay @alexismonville @ayeba @enovance
  15. 15. merci à nos sponsors !
  16. 16. Open Source = Agile ?
  17. 17. Open Source = Agile ? • Open Source shares the same values: • Individuals and interactions • Working software • Customer collaboration • Responding to change
  18. 18. Principles behind... • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a 
 preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-toface conversation. • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior
  19. 19. Yes! • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-toface conversation. • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior
  20. 20. But... • Not the same principles and practices: • No day to day face to face conversation • No collocated teams • Individuals and several teams • Distributed • Business People, Customer...
  21. 21. mix
  22. 22. Agile and Open Source
  23. 23. Virtual Gemba Walk
  24. 24. 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.
  25. 25. Computing Networking Storing
  26. 26. Cloud Operating System http://www.openstack.org
  27. 27. Who? http://www.openstack.org/foundation/companies/
  28. 28. Who? http://www.openstack.org/foundation/companies/
  29. 29. and a lot more...
  30. 30. 12120+ people 130 Countries
  31. 31. http://www.stackalytics.com/
  32. 32. What Does Openness Mean?
  33. 33. Scale
  34. 34. Onboarding
  35. 35. Onboarding • How to... • Ask... • Wiki... • IRC, mailing list... • Buddy... • ...
  36. 36. How? https://wiki.openstack.org/wiki/How_To_Contribute
  37. 37. Communication https://wiki.openstack.org/wiki/IRC
  38. 38. Release
  39. 39. Release Cycle
  40. 40. Release Cycle
  41. 41. Release Cycle • A coordinated 6-month release cycle with frequent development milestones. • The Release Cycle is made of four major stages: • Planning • Implementation • Pre-Release • Release https://wiki.openstack.org/wiki/ReleaseCycle
  42. 42. Free?
  43. 43. 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.
  44. 44. Agile?
  45. 45. 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.
  46. 46. Austin
  47. 47. Bexar
  48. 48. Cactus
  49. 49. Diablo
  50. 50. Essex
  51. 51. Folsom
  52. 52. Grizzly
  53. 53. Havana
  54. 54. Icehouse
  55. 55. Release Cycle Openstack
 Design
 Summit Openstack
 Design
 Summit F G planning RC G-1 G-2 G-3 6 mois H planning RC H-1 H-2 H-3 6 mois https://wiki.openstack.org/wiki/Releases
  56. 56. Planning
  57. 57. Planning • 4 weeks to: • Design • Discuss • Target https://wiki.openstack.org/wiki/ReleaseCycle
  58. 58. Tenets https://wiki.openstack.org/wiki/BasicDesignTenets
  59. 59. Blueprints https://wiki.openstack.org/wiki/Blueprints
  60. 60. Blueprints https://blueprints.launchpad.net/ceilometer/+spec/api-v2-improvement
  61. 61. Bugs https://bugs.launchpad.net/ceilometer
  62. 62. PTLs • Project Technical Leads. • 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. https://wiki.openstack.org/wiki/Governance/TechnicalCommittee
  63. 63. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  64. 64. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  65. 65. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  66. 66. Summit • Every 6 months the Design Summit gather users and developers • The Summit closes the Planning phase http://www.openstack.org/summit/portland-2013/session-videos/
  67. 67. Quality
  68. 68. Implementation
  69. 69. 800+
  70. 70. 2 +1, 0 -1
  71. 71. Core Devs • You need a +1 from a Core Developer • Core Developers are co-opted among the contributors
  72. 72. • Teams are distributed between Paris and Montreal Offices, plus people working remotely from home (somewhere...) • They used the Openstack collaborative tools (launchpad, wiki, mailing lists, irc channels...) • Openstack continuous integration tools : Gerrit, Jenkins, Zuul...
  73. 73. Questions?
  74. 74. Thank you!
  75. 75. Alexis Monville #AOSWay @alexismonville ! stay tuned: 
 http://www.the-agile-and-open-source-way.com/

×