Category: 2. Building Products
-
Getting started with open source license compliance 2/4
Open source license compliance is the process of ensuring that any product that you deliver to customers (more precisely, any distribution you make to recipients) complies with the licenses of the open source code used within that product. As it turns out, this is both a simple process (at 10000 feet) and a rather complicated…
-
Ten years of inner source case studies (video)
Georg Grütter of Bosch recorded my keynote at the Inner Source Commons summit in Renningen, Germany, on May 16th, 2018, and put it on Youtube. Please watch it below (original video, local copy). According to Georg, the video is licensed under CC BY-SA 3.0 (for the Bosch part) and I agree (for my part). Hence…
-
Third time’s the charm: Ten years of inner source case studies
Actually, I just notice it is the fourth time within the last two months, but tomorrow is the first time I’ll present our research on inner source in a public venue. If you are interested in ten years of case studies on how to use open source best practices within companies (called inner source), come…
-
![The QDAcity-RE method for structural domain modeling using qualitative data analysis [RE Journal]](https://dirkriehle.com/wp-content/uploads/featured/10308-santa-cruz-seal.jpg)
The QDAcity-RE method for structural domain modeling using qualitative data analysis [RE Journal]
Abstract: The creation of domain models from qualitative input relies heavily on experience. An uncodified ad-hoc modeling process is still common and leads to poor documentation of the analysis. In this article we present a new method for domain analysis based on qualitative data analysis. The method helps identify inconsistencies, ensures a high degree of…
-
Code of conduct for code reviews
On Twitter, @arkwrite suggested that a code review should always say something nice and @chaos_monster commented that we need a code of conduct for code reviews. All of this makes sense to me, however, I suggest that we first have a general code of conduct of productive discussions (and most companies have something like it).…
-
Who writes and prioritizes user stories?
I updated this post after I realized that it is more about prioritizing user stories than it is about writing them well. In Scrum, a product owner writes user stories to capture requirements and prioritizes them in a product backlog as the upcoming work queue for developers. The main question on my mind is: Who…