Category Archives: 7. Opinion

From a Student Business Plan

In PROD, my course on software product management, students can choose to develop a business plan for a software product. Not all of my students seem to take this as serious as I wished. Here is the opening sentence of the exec summary from one of the teams:

With a total loss of 388,987.50 Euros in the period of 2017 to 2019, we will increase profit by 2,123,121 Euros and the customer base by 1392% […] Break even will be reached by mid 2018.

Reminds me off the bubble days: “We will make 80 cents for one dollar spent and will be profitable in no time!”

Entrepreneurship Panel at IT-Gipfel Göttingen #itgipfelgoe

A few days ago, I participated in a panel on entrepreneurship in the beautiful but small city of Göttingen, Germany. While a university town, it isn’t exactly the Silicon Valley either, much like my current home town of Erlangen.

Thus, on the panel, I ran into the usual German morals on what makes a good entrepreneur, respectively, how to treat one:

Continue reading

Impressions from Installing and Configuring Devolo Home Automation Control Center

As a first step, I had installed remote controlled (Z-Wave) thermostats for my radiators. In addition, I installed Devolo’s Control Center and registered on its website for access to the control center. I had thought, from a prior email exchange with Devolo’s support, that it would not be necessary to use their web service. However, I was not able to identify (or find documentation) about a web server or some other management UI on the control center, so I decided to go through their website. I resent this, as I didn’t necessarily want them to have data on my home configuration, but it was the fastest way to a working set-up.

The first step was still a hardware installation step. I needed to plug-in the control center box and connect it to the Internet. My current solution below utilizes a Fritz! product, Ethernet over power-line. The Devolo Control Center comes with its own built-in Ethernet over power-line support and is supposed to be plug compatible with the Fritz solution, alas, this did not work out of the box. It is the one remaining problem to solve for me, later.

Continue reading

Unwrapping and Experiences with Installing Devolo Home Automation Thermostats

As my first (rather small) home automation project I decided to install remote controlled radiator thermostats. (This is also known as a central thermostat and comes with most modern apartments, but then my new Berlin apartment is rather old and charming. It has no central thermostat, making me run around the apartment every morning to manually adjust the seven radiators.)

I chose Devolo’s “Home Control” thermostats and control center. This is an affordable entry-level product into the space of home automation, though the total of seven thermostats and one (proprietary) control center set me back about EUR 600.

Continue reading

Making Introductions for Job Interviews

(Cross-posting from http://osr.cs.fau.de.)

As a human being, as a professional, and more recently as a professor, I’m happy to help people find jobs (time permitting). In fact, as a professor we have tagged HR professionals in our CRM database so that we can reach out easily to them. Still, introductions for job interviews require preparation on the side of the job seeker. There are a couple of things to consider.

The most common mistake that job seekers make is to ask me: Help me find a job in software engineering or product management or something else. Even if accompanied by a resume, what am I supposed to make of this? Pass on the resume to every company in the world?

The job of job seeking starts with the job seeker. They must find out where they want to go.

If they can’t, they should at least determine some companies of interest to them and provide them to me so that I can decide whether I can actually be of help.

Continue reading

Platforms but no Platform Organizations

One result of our recent case study research on inner source is that companies may not always need platform organizations to get to a platform of shared reusable assets. They will certainly need platforms, but they won’t need a dedicated organizational unit to develop and maintain this platform.

You don’t have to read the research paper to come this conclusion; common sense is just fine: Through the Apache Software Foundation (ASF), for example, companies like IBM, Oracle, and SAP are able to collaboratively develop the infrastructure of the Internet. The ASF has almost no employees; all work is done by the participating companies (and a few individuals). If companies like these, who fight each other to the death in front of a customer, can join hands to develop competitively non-differentiating software, why can’t organizational units inside software companies do this?

This is the idea of inner source: You don’t always have to have a dedicated organizational unit to work on a particular component. If the component is of broad enough interest within the company, users of this component might as well chip in and collaboratively develop the component. In the extreme case, and perhaps this is also the best case, no dedicated organizational unit is needed any longer for the development of shared reusable components.

The idea of doing away with a platform organization flies in the face of conventional wisdom. Given that textbooks tell you that product line engineering requires a dedicated platform organization, and leading companies are typically set-up this way, doing away with the platform organization may indeed prove to be too disruptive in the short-term. For this reason, we have developed several solutions that let companies keep their platform organizations.

Read more in the paper or contact us through my group’s homepage for research or my company’s homepage for commercial consulting.

Challenges to making software engineering research relevant to industry

I just attended FSE 2016, a leading academic conference on software engineering research. As is en vogue, it had a session on why so much software engineering research seems so removed from reality. One observation was that academics toil in areas of little interest to practice, publishing one incremental paper of little relevance after another. Another observation was that as empirical methods have taken hold, much research has become as rigorous as it has become irrelevant.

My answer to why so much software engineering research is irrelevant to practice is as straightforward as it is hard to change. The problem rests in the interlocking of three main forces that conspire to keep academics away from doing interesting and ultimately impactful research. These forces are:

  • Academic incentive system
  • Access to relevant data
  • Research methods competence

Continue reading