Adding some smaller aspects that might be of particular interest to product managers.

Author: MaineC

product/outline.md

@@ -2,6 +2,8 @@
 
 While the content of this segment can be intersting to engineers in order to help their teams better navigate business decisions related to InnerSource the core audience are people in your team and across your organisation that deal with product development. The goal of this segment is to help you understand how InnerSource can help interdependent teams resolve requirements without syncing work to the point where both teams operate in lock-step.
 
+Based learnings and best practices of successful, global Open Source projects this training shows you ways to increase collaboration and reduce waste by consollidating work on the shared technological basis. 
+
 # Takeaways
 
 After going through this segment, you will:
@@ -12,14 +14,19 @@ After going through this segment, you will:
         * cross-team collaboration
         * remote first teams
    * In what aspects does InnerSource differ from agile or traditional software development - in particular when the same terminology and technology is used? (Think "Issue tracker for backlog/ board management vs. issue tracker for communication", "code review as quality gate vs. continuous code review as a conversation").
-*  understand how even with InnerSource the host team still has to plan time and capacity when receiving features as pull requests as opposed to features requests.
-*  understand additional negotiation possibilities that InnerSource brings (think "host teams implements tricky feature request of contributing team, in return the contributing team helps with simpler features that the host teams has higher up on their priority list")
+*  understand the impact of InnerSource on capacity planning when receiving features as pull requests as opposed to features requests: There is no free lunch - while InnerSource reduces the amount of work for the host team, mentoring contributors does cost time.
+*  understand additional negotiation possibilities that InnerSource brings - keeping the balance of Give and Take with InnerSource
 
 # Outline
 
 InnerSource and Agile
 
+You want to improve your product and deliver those improvements faster to customers. You want to make stakeholders happy. InnerSource helps your team deliver value and maintain autonomy especially in a highly interconnected world.
+
 - Issues InnerSource solves
+   - avoid lengthy roadmap syncronization discussions: "help with solution" instead of "wait it out" or "build workarounds"
+   - resolve cross dependencies without compromising autonomy, code ownership and quality
+   - better support for remote first by higher focus on written communication
 - Common mis-understandings
    - Common fears (like losing control) and counter measures
    - Same phrase - different meaning: How issue trackers and code reviews are used differently in InnerSource projects than is common in the industry.
@@ -56,3 +63,6 @@ Options for shared ownership
 
 
 Relation to open source
+- Governance levels in open source and their impact on your adoption decision
+- Parallel of upstream participation to InnerSource
+- Gaining by sharing aspect of open source