Writing down and sharing what you have learned helps to start conversations with others. Then you can learn together! One way of writing about collaboration challenges and solutions is to put them into the form of InnerSource Patterns.

1. Sebastian Spier
2021-02-12
Learning through Writing
(e.g. InnerSource Patterns)

2. InnerSource?

3. “the use of open source best
practices for software
development within the confines
of an organization”
innersourcecommons.org

4. A little simpler:
Open-Source-style
collaboration inside
of your company

5. InnerSource Pattern?

6. A template
for how to solve an
InnerSource problem.

7. A little simpler:
Written stories
of what has
worked for others

8. InnerSource Patterns book
with 19 mature patterns
Covers all stages of an
InnerSource Program.

9. Problem
Context
Forces
Solutions
Resulting Context
Known Instances
These don’t look like
normal stories though!
What are all these
headlines about?

10. Who is writing
such Patterns?

11. anybody really
Developers
Architects
Product Owners
Program Office
...

12. What’s in it for me?
(Why should I write and share e.g. Patterns?)

13. Writing things down helps
to understand what you are
really thinking!

14. Sharing what you have written
helps to start conversations
(which again improves clarity of thinking! a feedback loop!)

15. Find people with
the same challenge!
Maybe even
solve it together!

16. It’s all Open Source!
(Source) Code == (Text) Writing
Share more. Learn faster!

17. ● InnerSource Patterns book
● Slack
● Another example of learning faster through writing:
Transparent Cross-Team Decision Making using RFCs
Links

18. Thanks for listening.
spier.hu
Work: underthehood.meltwater.com
Contact: sebastian@spier.hu and @sebastianspier