Data in Motion

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Eclipse Way - Or how to never deliver late! ======

There is an agile software development organization and methodology that has produced an amazing string of successes, yet nobody seems to be talking about them:

   * Never shipped late in 13 years; has never had to make an emergency patch release of a production build
   * The 2014 Luna release's achievements included
      * 61 million lines of code ((http://eclipse.org/org/press-release/20140625_luna_release_train.php))
      * 65 companies, composed of nearly 700 engineers distributed worldwide ((http://dash.eclipse.org/dash/commits/web-app/))
      * With a low stress process as required for voluntary participation

If a company had this kind of track record, they would be talking about it.  Loudly!  But this organization is Eclipse, an open-source project.

Why has Eclipse been so successful?  And can we apply lessons learned from Eclipse's success to commercial projects?

I believe so.  And with this article, I intend to start a series discussing my experiences, both positive and negative, applying Eclipse Way--because in one project in particular, I credit Eclipse Way and its lessons for playing a major role in five years of consistent on-time production releases, on a schedule sync'ed with Eclipse's milestone releases.  And I'd like to invite anyone else interested in this topic to jump in and comment and share their insights too.

Let's have fun and learn together!

~~DISQUS~~

~~LINKBACK~~

Data in Motion

User Tools

Site Tools

Page Tools