Commercial Open Source: Faster, Better, Cheaper, and More Easily?

I’m trying to create a pithy statement as to how commercial open source firms are superior to traditional (closed source) software development firms. For that, I need to define what the specific effects are that using an open source go-to-market strategy has on the bottom line. (If your answer is “it’s the community, naturally”—that’s not the intent of my question.) So far, I’ve been enumerating the benefits by business function, that is:

A commercial open source firm can

  1. go to market faster
  2. with a superior product
  3. at lower overall costs, and
  4. sell it more easily

than possible for traditional closed source competitors. I think that’s it: Faster, better, cheaper, and more easily.

As you can see, I’ve basically enumerated the various business functions as you might find them on a firm’s income statement. (1) and (2) address product management and engineering, (3) addresses pretty much all business functions, and (4) addresses marketing and sales. Anything that I should add? Rearrange things? Take a totally different perspective? Thanks for any thoughts you might have!

Red Hat on Patents and Total Growth of Open Source

A couple of days ago, Red Hat filed a brief with the EPO (European Patent Office), arguing that patents hinder software innovation (as masterfully summarized by Glynn Moody). From Red Hat’s press release:

Today Red Hat took its efforts to confront the problem of software patents to new ground by filing a brief with the European Patent Office. The brief explains that software patents hinder software innovation, and that there is a sound legal basis not to expand availability of such patents in Europe.

I particularly liked that Red Hat uses Amit Deshpande’s and my work on the Total Growth of Open Source software as evidence of the significance of open source. An added bonus is that our little academic paper is referenced right next to the work of one of my heroes, Eric von Hippel’s Democratizing Innovation.

The good news is that I have tons of material to make an even stronger case for the economic significance and future impact of open source. The bad news is that time and resources are in short supply… but that will change eventually.

The Commercial Open Source Business Model

Abstract: Commercial open source software projects are open source software projects that are owned by a single firm that derives a direct and significant revenue stream from the software. Commercial open source at first glance represents an economic paradox: How can a firm earn money if it is making its product available for free as open source? This paper presents the core properties of commercial open source business models and discusses how they work. Using a commercial open source approach, firms can get to market faster with a superior product at lower cost than possible for traditional competitors. The paper shows how these benefits accrue from an engaged and self-supporting user community. Lacking any prior comprehensive reference, this paper is based on an analysis of public statements by practitioners of commercial open source. It forges the various anecdotes into a coherent description of revenue generation strategies and relevant business functions.

Reference: Dirk Riehle. “The Commercial Open Source Business Model.” In Proceedings of the Fifteenth Americas Conference on Information Systems (AMCIS 2009). AIS Electronic Library, 2009. Paper 104.

Available as HTML or PDF file.

Bringing Open Source Best Practices into Corporations Using a Software Forge

You may have noticed our work on improving corporate software development at SAP using an in-house software forge. The main benefit is in transferring open source best practices to our software development processes. At an upcoming industry conference presentation I’ll be talking about some of the lessons we learned. Here is the abstract of the talk:

Abstract: A software forge is a tools platform for collaborative software development, similar to integrated CASE environments. Unlike CASE tools software forges have been designed for the software development practices of the open source community. Open source software projects succeed where waterfall and agile methods fail: They can cope with changing requirements and they can scale to large project sizes. Thus, corporate software development can learn from open source best practices. In this presentation, I discuss our experiences with using a software forge to bring open source best practices into SAP. We present the design principles and benefits of a firm-internal software forge, and we present a case study of how one project inside SAP benefited significantly from being on the forge.

Reference: Dirk Riehle. “Bringing Open Source Best Practices into Corporations Using a Software Forge.” Talk at SEACON 2009. Hamburg, Germany: 2009.

Open Collaboration within Corporations Using Software Forges

Abstract: Over the past 10 years, open source software has become an important cornerstone of the software industry. Commercial users have adopted it in standalone applications, and software vendors are embedding it in products. Surprisingly then, from a commercial perspective, open source software is developed differently from how corporations typically develop software. Research into how open source works has been growing steadily. One driver of such research is the desire to understand how commercial software development could benefit from open source best practices. Do some of these practices also work within corporations? If so, what are they, and how can we transfer them?

Keywords: Inner source, firm-internal open source, corporate source, software forge, open collaboration, open source.

Reference: Dirk Riehle, John Ellenberger, Tamir Menahem, Boris Mikhailovski, Yuri Natchetoi, Barak Naveh, Thomas Odenwald. “Open Collaboration within Corporations Using Software Forges.” IEEE Software, vol. 26, no. 2 (March/April 2009). Page 52-58.

Available as HTML or as a PDF file.