Contribute to the Success of OpenStack

During the OpenStack Summit in Austin, Mark McLoughlin and I delivered a talk titled: “Contribute to the Success of OpenStack”.

Our talk was meant to explain how we were inspired by agile values and principles to improve our internal organization, and how we thought it could impact our ability to contribute more effectively to the OpenStack project.

One of the idea that is often used to describe the way companies are contributing to open source project is that you need at some point to wear your company hat to represent what your company needs, and some times you need to wear your upstream hat to represent what the project needs. We speak some time of the need to balance between upstream and downstream.

Our point was to say that this idea represents the reality perfectly well in projects were the developers are the users of the projects. In this case they are solving problems they are facing on a regular basis.

The OpenStack project is more complex in this sense that the developers are rarely the main users of the project. They don’t have to operate a large scale cloud on a day to day basis.

So, to be able to understand the needs, and to propose effective solutions, the developers of the project need to hear from the real users. That’s were they need to wear at the same time their corporate and upstream hats, because the customers and partners of their company represents the needs of the real users, and wearing those hats they are bringing a lot of value to the project by proxying the real users.

We also explored the fact that when the reaction toward one of the idea that we were bringing on the table was really hostile, there was probably good reason for that, and that was great value for our company that the project was bringing to us. This obvioulsy can only be achieved when the maturity of the project is high enough, especially on the corporate diversity aspect.

We covered after that how we were organizing the teams that are contributing to OpenStack by giving them a clear focus to solve some real user’s needs, and end to end responibility to solve this. Those teams are primary responsible for contributing to some of the components, but the components are not driving the structure of the organization.

For each team, we want the team members to understand their mission, their goals, and to drive their contribution in the value flow.

Here is the recording of the session:


For the next Summit in Barcelona, I proposed 3 talks:

  • The first one with Maria Bracho: “Providing Tooling for Effective Collaboration”
  • The second one with Nick Barcet: “Does your voice count in OpenStack? Yes!” this one could be consider as a followup of the talk given this spring
  • The third one: “Raising the awareness on diversity”, one workshop during the last summit was an eye opener for me, and I would like to continue the effort to raise the awarness on that topic.

You can vote on your preferred presentation here:

If you want to vote for the one I submitted search  for my name: monville 🙂



Header photo by William White

Richard and Open Source…

GNU_30th_badgeDo you know this guy?

It’s Richard Stallman , the initiator of the free software movement ( the gnu movement celebrates its 30th anniversary this year ).

I use this picture of Richard Stallman in a presentation I gave on several occasions (AgileTour Brussels, Open World Forum, French Scrum User Group…). This presentation is named : “The Agile and Open Source Way“.

When Richard Stallman’s image is displayed, I ask participants if they know this person. Depending on the audience, the number of raised hands is variable. I explain why Richard Stallman would probably not appreciate being associated with an “Open Source” presentation and I encourage them to read the excellent article: “Why Open Source misses the point of Free Software“. To sum up, we could say that Open Source is interested in practical benefits (quality, reliability, performance …) of the four freedoms, putting aside the moral values ​​of free software.

I use this to draw a parallel with what is happening since the publication of the agile manifesto in 2001.
Some are interested in the values ​​and principles of the Agile Manifesto, others to certain practices of agile methods: allowing the user satisfaction, better quality, better predictability …

The difference ​​between “Making Agile” and “Being agile”.

Thank you Pascal, for making me notice that the slideshare presentation needed clarification on intentions.