Your SlideShare is downloading. ×
0
The Agile and
Open Source Way
Learn the Way of Delivering High Quality Software
with Multiple Distributed Teams
The Agile and
Open Source Way
Learn the Way of Delivering High Quality Software
with Multiple Distributed Teams
Open Source?
http://en.wikipedia.org/wiki/Open_source
Open Source
• source code is published
• made available to the public
• enabling ...
Agile?
Agile manifesto: http://agilemanifesto.org
Agile
• Continuous improvement
• Individuals and interactions
• Working softwar...
1 or 2 weeksplanificationdaily meetingdemonstrationretrospectiveorderadaptimprovemost importantcollaboratefeatures
TODO DOI...
Agile Methods
≠
=
?
Who?
Alexis Monville
#AOSWay
@alexismonville
Alexis Monville
#AOSWay
@alexismonville
@ayeba
Alexis Monville
#AOSWay
@alexismonville
@ayeba
@enovance
#OWF13
#AOSWay
@alexismonville
@ayeba
@enovance
Open Source = Agile ?
Open Source = Agile ?
• Open Source shares the same values:
• Individuals and interactions
• Working software
• Customer c...
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
• Individu...
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 the...
Computing Networking Storing
http://www.openstack.org
Cloud Operating
System
T
http://www.openstack.org/foundation/
companies/
Who?
http://www.openstack.org/foundation/
companies/
Who?
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...
• ...
https://wiki.openstack.org/wiki/
How_To_Contribute
How?
https://wiki.openstack.org/wiki/IRC
Communication
Release
Release Cycle
photo tambour
Release Cycle
https://wiki.openstack.org/wiki/ReleaseCycle
Release Cycle
• A coordinated 6-month release cycle with
frequent development...
Free?
Release Cycle
• Note: Each core project is free to choose a
different release cycle contents, as long as
they submit a ver...
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
I...
Icehouse
https://wiki.openstack.org/wiki/Releases
Release Cycle
F G H
planning
Openstack
Design
Summit
G-1 G-2 G-3
RC planning
H-1 ...
Planning
https://wiki.openstack.org/wiki/ReleaseCycle
Planning
• 4 weeks to:
• Design
• Discuss
• Target
https://wiki.openstack.org/wiki/BasicDesignTenets
Tenets
https://wiki.openstack.org/wiki/Blueprints
Blueprints
https://blueprints.launchpad.net/ceilometer/+spec/api-v2-improvement
Blueprints
https://bugs.launchpad.net/ceilometer
Bugs
https://wiki.openstack.org/wiki/Governance/TechnicalCommittee
PTLs
• Project Technical Leads.
• A PTL is the elected techn...
photo of the summit
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAli...
photo of the summit
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAli...
photo of the summit
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAli...
http://www.openstack.org/summit/portland-2013/session-videos/
Summit
• Every 6 months the
Design Summit gather
users and d...
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 us...
Questions?
Thank you!
Alexis Monville
#AOSWay
@alexismonville
stay tuned:
http://www.the-agile-and-open-source-way.com/
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Open World Forum - The Agile and Open Source Way
Upcoming SlideShare
Loading in...5
×

Open World Forum - The Agile and Open Source Way

1,064

Published on

Slides from Open World Forum 2013 (#OWF13)

The Agile and Open Source Way is the book for everyone who wants to scale agile in multiple distributed teams. This book will also help you to collaborate upstream with Open Source projects.
Whether you want to improve interactions with other teams inside or outside your company, or just interested in scaling from more than one team, you will find in this publication the information you need, illustrated by a real case.

http://www.the-agile-and-open-source-way.com/

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

No Downloads
Views
Total Views
1,064
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
13
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "Open World Forum - The Agile and Open Source Way"

  1. 1. The Agile and Open Source Way Learn the Way of Delivering High Quality Software with Multiple Distributed Teams
  2. 2. The Agile and Open Source Way Learn the Way of Delivering High Quality Software with Multiple Distributed Teams
  3. 3. Open Source?
  4. 4. http://en.wikipedia.org/wiki/Open_source 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
  5. 5. Agile?
  6. 6. Agile manifesto: http://agilemanifesto.org Agile • Continuous improvement • Individuals and interactions • Working software • Customer collaboration • Responding to change
  7. 7. 1 or 2 weeksplanificationdaily meetingdemonstrationretrospectiveorderadaptimprovemost importantcollaboratefeatures TODO DOING DONE
  8. 8. Agile Methods
  9. 9.
  10. 10. =
  11. 11. ?
  12. 12. Who?
  13. 13. Alexis Monville #AOSWay @alexismonville
  14. 14. Alexis Monville #AOSWay @alexismonville @ayeba
  15. 15. Alexis Monville #AOSWay @alexismonville @ayeba @enovance
  16. 16. #OWF13 #AOSWay @alexismonville @ayeba @enovance
  17. 17. Open Source = Agile ?
  18. 18. Open Source = Agile ? • Open Source shares the same values: • Individuals and interactions • Working software • Customer collaboration • Responding to change
  19. 19. 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- to-face 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. 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- to-face 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.
  21. 21. 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...
  22. 22. mix
  23. 23. Agile and Open Source
  24. 24. Virtual Gemba Walk
  25. 25. 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.
  26. 26. Computing Networking Storing
  27. 27. http://www.openstack.org Cloud Operating System
  28. 28. T
  29. 29. http://www.openstack.org/foundation/ companies/ Who?
  30. 30. http://www.openstack.org/foundation/ companies/ Who?
  31. 31. and a lot more...
  32. 32. 12120+ people 130 Countries
  33. 33. http://www.stackalytics.com/
  34. 34. What Does Openness Mean?
  35. 35. Scale
  36. 36. Onboarding
  37. 37. Onboarding • How to... • Ask... • Wiki... • IRC, mailing list... • Buddy... • ...
  38. 38. https://wiki.openstack.org/wiki/ How_To_Contribute How?
  39. 39. https://wiki.openstack.org/wiki/IRC Communication
  40. 40. Release
  41. 41. Release Cycle photo tambour
  42. 42. Release Cycle
  43. 43. https://wiki.openstack.org/wiki/ReleaseCycle 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
  44. 44. Free?
  45. 45. 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.
  46. 46. Agile?
  47. 47. 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.
  48. 48. Austin
  49. 49. Bexar
  50. 50. Cactus
  51. 51. Diablo
  52. 52. Essex
  53. 53. Folsom
  54. 54. Grizzly
  55. 55. Havana
  56. 56. I...
  57. 57. Icehouse
  58. 58. https://wiki.openstack.org/wiki/Releases 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
  59. 59. Planning
  60. 60. https://wiki.openstack.org/wiki/ReleaseCycle Planning • 4 weeks to: • Design • Discuss • Target
  61. 61. https://wiki.openstack.org/wiki/BasicDesignTenets Tenets
  62. 62. https://wiki.openstack.org/wiki/Blueprints Blueprints
  63. 63. https://blueprints.launchpad.net/ceilometer/+spec/api-v2-improvement Blueprints
  64. 64. https://bugs.launchpad.net/ceilometer Bugs
  65. 65. https://wiki.openstack.org/wiki/Governance/TechnicalCommittee 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.
  66. 66. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  67. 67. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  68. 68. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
  69. 69. http://www.openstack.org/summit/portland-2013/session-videos/ Summit • Every 6 months the Design Summit gather users and developers • The Summit closes the Planning phase
  70. 70. Quality
  71. 71. Implementation
  72. 72. 800+
  73. 73. 2 +1, 0 -1
  74. 74. Core Devs • You need a +1 from a Core Developer • Core Developers are co-opted among the contributors
  75. 75. • 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...
  76. 76. Questions?
  77. 77. Thank you!
  78. 78. Alexis Monville #AOSWay @alexismonville stay tuned: http://www.the-agile-and-open-source-way.com/
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×