French Scrum User Group @Google - The Agile and Open Source Way
1 like2,782 views
The document discusses the relationship between Agile methodologies and open-source principles, highlighting shared values such as customer collaboration and responding to change. It outlines key Agile processes and the OpenStack initiative aimed at creating an accessible cloud computing platform. Additionally, it emphasizes the importance of communication and collaboration within distributed teams, marking a distinction between Agile practices and their application in open-source environments.
French Scrum User Group @Google - The Agile and Open Source Way
- 2. merci à nos sponsors !
- 3. Agile?
- 4. Agile • Continuous improvement • Individuals and interactions • Working software • Customer collaboration • Responding to change Agile manifesto: http://agilemanifesto.org
- 5. Open Source?
- 7. 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
- 8. ≠
- 9. =
- 10. ?
- 11. Who?
- 16. merci à nos sponsors !
- 17. Open Source = Agile ?
- 18. Open Source = Agile ? • Open Source shares the same values: • Individuals and interactions • Working software • Customer collaboration • Responding to change
- 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-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. 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
- 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. mix
- 27. 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.
- 33. and a lot more...
- 39. Scale
- 41. Onboarding
- 42. Onboarding • How to... • Ask... • Wiki... • IRC, mailing list... • Buddy... • ...
- 45. Release
- 46. Release Cycle
- 47. Release Cycle
- 48. 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
- 49. Free?
- 50. 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.
- 51. Agile?
- 52. 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.
- 53. Austin
- 54. Bexar
- 55. Cactus
- 56. Diablo
- 57. Essex
- 58. Folsom
- 59. Grizzly
- 60. Havana
- 61. Icehouse
- 62. 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
- 63. Planning
- 64. Planning • 4 weeks to: • Design • Discuss • Target https://wiki.openstack.org/wiki/ReleaseCycle
- 69. 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
- 70. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 71. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 72. OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 73. 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/
- 74. Quality
- 75. Implementation
- 76. 800+
- 79. 2 +1, 0 -1
- 81. Core Devs • You need a +1 from a Core Developer • Core Developers are co-opted among the contributors
- 85. • 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...
- 86. Questions?
- 88. Thank you!
- 89. Alexis Monville #AOSWay @alexismonville ! stay tuned: http://www.the-agile-and-open-source-way.com/