The Agile and Open Source Way (AgileTour Brussels)
3 likes1,796 views
The document discusses the integration of Agile methodologies with open source software development, emphasizing principles such as customer satisfaction, collaboration, and responsiveness to change. It outlines the Agile manifesto, contrasting it with open source practices, which allow for shared code and community contributions. Additionally, the document describes the OpenStack project and its structured six-month release cycle, alongside the role of technical leads and community participation in the development process.
The Agile and Open Source Way (AgileTour Brussels)
- 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. Agile?
- 4. Agile manifesto: http://agilemanifesto.org Agile • Continuous improvement • Individuals and interactions • Working software • Customer collaboration • Responding to change
- 5. Open Source?
- 6. 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
- 7. ≠
- 8. =
- 9. ?
- 10. Who?
- 15. Open Source = Agile ?
- 16. Open Source = Agile ? • Open Source shares the same values: • Individuals and interactions • Working software • Customer collaboration • Responding to change
- 17. 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
- 18. 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.
- 19. 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...
- 20. mix
- 22. it’s a AND • Be Agile • with Open Source Software
- 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.
- 28. T
- 31. and a lot more...
- 37. Release Cycle
- 38. 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
- 39. Free?
- 40. 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.
- 41. Agile?
- 42. 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.
- 43. Austin
- 44. Bexar
- 45. Cactus
- 46. Diablo
- 47. Essex
- 48. Folsom
- 49. Grizzly
- 50. Havana
- 51. I...
- 52. Icehouse
- 53. 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
- 54. Planning
- 55. https://wiki.openstack.org/wiki/ReleaseCycle Planning • 4 weeks to: • Design • Discuss • Target
- 60. 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.
- 61. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 62. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 63. photo of the summit OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com
- 64. 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
- 65. Implementation
- 66. 800+
- 71. 2 +1, 0 -1
- 73. Core Devs • You need a +1 from a Core Developer • Core Developers are co-opted among the contributors
- 77. • 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...
- 78. • Daily Meeting? • There’s an irc bot for that! • Review, Retrospective, Planning • Videoconference, shared screen, shared documents...
- 79. Pre-release
- 80. https://wiki.openstack.org/wiki/ReleaseCycle Pre-release • Release Candidates dance :) • RC1 • stop adding features • concentrate on bug fixes • If there’s critical release issues... Go for a RC respin...
- 81. Release
- 83. InYour Company?
- 84. Onboarding
- 85. Onboarding • How to... • Ask... • Wiki... • IRC, mailing list... • Buddy... • ...
- 86. Design
- 87. Design Process • Design Tenets • Blueprints • PTLs • Devs • Summit • ...
- 88. Code
- 89. Coding Process • Coding guidelines • Version control • Reviewing process • Automated Testing • Automated Deployment • Tools... • PTLs • Core Dev • Dev
- 90. Release
- 92. People
- 93. People • Humble • Collaborative • Learners • Free...
- 94. Questions
- 96. Thank you!