Summary and Translation of Microblogging Can Enhance Productivity Interview

Courtesy of SAP, here an English-language summary translation of the interview with Oliver Günther on micro-blogging and productivity.

Originally: “Das Microblogging kann die Produktivität durchaus steigern.” Computer Zeitung, June 15, 2009.

The integration of micro-blogging in corporations makes sense, concludes a project by SAP Research in Palo Alto and the Institute for Business Informatics at the Humboldt University in Berlin. In an interview, professor Oliver Günther says that a majority of the focus group that was interviewed in Silicon Valley regard micro-blogging as a collaboration tool that potentially enhances productivity. High potential is seen in the interaction between company and client, in advertising, public relations, and informal communications within a team. Possible applications could be in creative processes or just in the exchange of hints in the service team. Micro-blogging can substitute communication by e-mail or instant-messenger putting it on the micro-blogging platform which is an easy to use tool with broad distribution. However, micro-blogging is not regarded as suitable for every business or every department. It very much depends on the corporate culture: communicative corporate cultures such as in IT would profit. Conservative cultures such as in banking would have problems with integrating this communication channel into their culture. The same applies to the enhancement of productivity. In some cases it will lead to it, in others, micro-blogging only distracts. The communication channel exists and employees and clients expect management to address the right usage of it. Not just addressing and implementing the tool is necessary for making it a success but also management actively participating in it. Last but not least, the clarification of data privacy issues is of paramount importance for the acceptance of micro-blogging in a company.

Full article in German.

Micro-Blogging in the Enterprise Can Improve Productivity

Oliver Günther, a co-author of our micro-blogging in the enterprise study and a Professor at prestigious Humboldt University (of Berlin, Germany), was interviewed by the German tech weekly “Computer Zeitung” on the subject matter. He re-iterated our main point that micro-blogging can improve productivity in enterprises (but also that more work needs to be done). Please see for yourself:

If you’d like to know more you can meet me at the 2009 Theseus Symposium in Berlin, Germany, on June 30th this year, where I will be presenting our work on micro-blogging.

Modeling Micro-Blogging Adoption in the Enterprise

Abstract: Despite a broad range of collaboration tools already available, enterprises continue to look for ways to improve internal and external communication. Micro-blogging is such a new communication channel with some considerable potential to improve intra-firm transparency and knowledge sharing. However, the adoption of such social software presents certain challenges to enterprises. Based on the results of four focus group sessions, we identified several new constructs to play an important role in the micro-blogging adoption decision. Examples include privacy concerns, communication benefits, perceptions regarding signal-to-noise ratio, as well codification effort. Integrating these findings with common views on technology acceptance, we formulate a model to predict the adoption of a micro-blogging system in the workspace. Our findings serve as an important guideline for managers seeking to realize the potential of micro-blogging in their company.

Reference: Oliver Günther, Hanna Krasnova, Dirk Riehle, Valentin Schöndienst. “Modeling Micro-Blogging Adoption in the Enterprise.” In Proceedings of the Fifteenth Americas Conference on Information Systems (AMCIS 2009). AIS Electronic Library, 2009. Paper 544.

Available as a 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.

Learning from Wikipedia: Open Collaboration within Corporations

Wikipedia is the free online encyclopedia that has taken the Internet by storm. It is written and administered solely by volunteers. How exactly did this come about and how does it work? Can it keep working? And maybe more importantly, can you transfer its practices to the workplace to achieve similar levels of dedication and quality of work? In this presentation I describe the structure, processes and governance of Wikipedia and discuss how some of its practices can be transferred to the corporate context.

This presentation represents the next step in the evolution of two Wikimania tutorials/workshops, see Presentations/Tutorials. If the slideshow doesn’t play, please use the PDF file download below.

Reference: Dirk Riehle. “Learning from Wikipedia: Open Collaboration within Corporations.” Invited talk at Talk the Future 2008. Krems, Austria: 2008.

The slides are available as a PDF file.

Open Collaboration: Self-Organizing Innovation in Large Corporations

Author: Dirk Riehle, SAP Research, SAP Labs LLC

Reference: Steven Fraser (editor). “Escaped from the Lab: Innovation Practices in Large Organizations.” In Companion of the 2008 Conference on Object Oriented Programming, Systems, Languages, and Applications (OOPSLA ’08). ACM Press, 2008: Pages 787-790.

Available as a PDF file; my part follows as HTML below.

Position statement for the OOPSLA 2008 Panel on Innovation Practices in Large Corporations

In most companies, the innovation process is organized as follows: A research unit suggests to build a prototype of some innovative product or feature, a line-of-business sponsor signs off on the project, the research unit develops the prototype, a product unit receives it and turns it into a real product.

The critical point is the transfer from research to product unit. Here, many things can go wrong, for example:

Continue reading