diff --git a/README.md b/README.md
index cd4ff0e509ec30bcb54294393b5fb3bb4a4a1091..40d2d9bfb669acf33097c8886585d6c9db8e76e5 100644
--- a/README.md
+++ b/README.md
@@ -81,21 +81,39 @@ The "What to Build" pattern focuses on determining what to create by aligning cu
 ## Look at the practice areas in the pattern and think about the car radio product line. What skill or knowledge is available in our team? What is missing? Write down your findings for each practice area.
 Market Analysis:
 - Available skills:
-- Missing skills: The analysis with students should not be as good as needed
+- Missing skills: The analysis with students should not be as good as needed, marketing knowledge
 Understanding relevant Domains: 
-- Available skills: Differentiate between common and different features, we know which capability goes to the core asset
-- Missing skills: legal restrictions, standards are unknown for radios
+- Available skills: Differentiate between common and different features, we know which capability goes to the core asset (only basics)
+- Missing skills: legal restrictions, standards are unknown for radios, not experts for creating core asset for car radios
 Technology forecasting:
-- Available skills: Tool knowledge
-- Missing skills: don't know which tool to use because time frame is unknown
+- Available skills: 
+- Missing skills: we can not forecast technologies, collecting information about products
 Building a business case:
-- Available skills: we can decide which product belong to the product line, Justify the effort to adapt a product line
+- Available skills: we can decide which product belong to the product line, Justify the effort to adapt a product line (only basics)
+- Missing skills: no business knowledge of car radios
+Scoping:
+- Available skills: We can decide whether a planned or existing product is part of the product line or not (only basics)
+- Missing skills: We have no input for scoping. We don't know which technology to use.
+
+Moodle or OBS
+Market Analysis:
+- Available skills: need for it. You know this because you are a student
+- Missing skills:
+Understanding relevant Domains:
+- Available skills:
 - Missing skills: 
+Technology forecasting:
+- Available skills:
+- Missing skills: 
+Building a business case:
+- Available skills:
+- Missing skills: there is not much money. University is not paying for this core asset (unlike car companies)
 Scoping:
-- Available skills: We can decide whether a planned or existing product is part of the product line or not
+- Available skills: 
+- Missing skills: 
 
 ### Is it a good idea to start such a product line? Why (not)? 
-No, because we need all answers to the missing information before. Otherwise the product line is not planned very good and strategic. A radio is not a quite good example for building a product line, because it is very simple. It is not worth it. Also most of us don't have any hardware or business knowledge.
+No, because we need all answers to the missing information before. Otherwise the product line is not planned very good and strategic. A radio is not a quite good example for building a product line, because it is very simple. It is not worth it. Nowadays cars have navigation systems with integrated radio. Also most of us don't have any hardware or business knowledge.
 
 ### If you think that a product line for car radios is no good idea - can you imagine any other products that could be a reasonable product line for a group of CS students? 
 We can build a CMS with multiple versions. One version is for customer who are paying for the product for using more Features (eg. AI) and we can build other community versions with less features, but all versions should be stable.
@@ -103,4 +121,8 @@ We can build a CMS with multiple versions. One version is for customer who are p
 ### Imagine you have a successful product line running. What does this mean to flexibility? Your willingness to change your processes or technologies? What should you do about this? 
 - A successful product line often locks a team into specific processes, technologies, and market expectations.
 - Introducing changes can risk disrupting the established workflow and product consistency.
-- We don't do harmful changes that are disrupting the whole product line that we have to rebuild it
\ No newline at end of file
+- We don't do harmful changes that are disrupting the whole product line that we have to rebuild it
+
+Tooling:
+- configurator
+- 
\ No newline at end of file