Open World Forum - The Agile and Open Source Way
2 likes1,622 views
The document discusses the integration of Agile methodologies and open source principles for delivering high-quality software with distributed teams. It emphasizes the importance of continuous delivery, customer satisfaction, and collaboration among developers and business stakeholders while adhering to Agile values. The OpenStack project serves as a case study, highlighting its release cycle and community-driven approach to cloud computing.
Open World Forum - The Agile and Open Source Way
- 1. The Agile and Open Source Way Learn the Way of Delivering High Quality Software with Multiple Distributed Teams
- 2. The Agile and Open Source Way Learn the Way of Delivering High Quality Software with Multiple Distributed Teams
- 3. Open Source?
- 5. 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
- 6. Agile?
- 7. Agile manifesto: http://agilemanifesto.org Agile • Continuous improvement • Individuals and interactions • Working software • Customer collaboration • Responding to change
- 9. 1 or 2 weeksplanificationdaily meetingdemonstrationretrospectiveorderadaptimprovemost importantcollaboratefeatures TODO DOING DONE
- 10. Agile Methods
- 11. ≠
- 12. =
- 13. ?
- 14. Who?
- 19. Open Source = Agile ?
- 20. Open Source = Agile ? • Open Source shares the same values: • Individuals and interactions • Working software • Customer collaboration • Responding to change
- 21. 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
- 22. 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.
- 23. 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...
- 24. mix
- 29. 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.
- 32. T
- 35. and a lot more...
- 41. Scale
- 43. Onboarding
- 44. Onboarding • How to... • Ask... • Wiki... • IRC, mailing list... • Buddy... • ...
- 47. Release
- 49. Release Cycle
- 50. 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
- 51. Free?
- 52. 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.
- 53. Agile?
- 54. 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.
- 55. Austin
- 56. Bexar
- 57. Cactus
- 58. Diablo
- 59. Essex
- 60. Folsom
- 61. Grizzly
- 62. Havana
- 63. I...
- 64. Icehouse
- 65. 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
- 66. Planning
- 67. https://wiki.openstack.org/wiki/ReleaseCycle Planning • 4 weeks to: • Design • Discuss • Target
- 72. 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.
- 73. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 74. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 75. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 76. 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
- 77. Quality
- 78. Implementation
- 79. 800+
- 82. 2 +1, 0 -1
- 84. Core Devs • You need a +1 from a Core Developer • Core Developers are co-opted among the contributors
- 88. • 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...
- 89. Questions?
- 91. Thank you!