summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSarah Sharp <sarah@thesharps.us>2016-04-12 08:31:03 -0700
committerSarah Sharp <sarah@thesharps.us>2016-04-12 08:31:03 -0700
commitf839cc773bcb9f3a2eef45359847aedef1acf634 (patch)
tree644192cfa6a55da38c16aa6deb71d67b1698a5ca
parent0a3211ba6b112d9190f366c6e8fde8a2cb7272f6 (diff)
downloadcorporate-foss-training-f839cc773bcb9f3a2eef45359847aedef1acf634.tar.gz
corporate-foss-training-f839cc773bcb9f3a2eef45359847aedef1acf634.zip
Draft for outline of manager/PM talk.
Signed-off-by: Sarah Sharp <sarah@thesharps.us>
-rw-r--r--open-source-101-pms.txt23
1 files changed, 23 insertions, 0 deletions
diff --git a/open-source-101-pms.txt b/open-source-101-pms.txt
index 64da5c2..0ff4bac 100644
--- a/open-source-101-pms.txt
+++ b/open-source-101-pms.txt
@@ -1,3 +1,26 @@
+Approach:
+
+20 minutes:
+
+Start by asking for their concerns about open source. Treat this as
+a brainstorming session, and write down their concerns on a whiteboard (or
+similar). Do a similar brainstorming session for why companies choose to
+participate in open source. This allows us to gauge the knowledge and concerns
+of the room, and make people feel like they're being listened to. Tailor content
+based on that session (with lots of backup slides).
+
+10 minutes:
+
+Level set on open source process vs. closed source top-down software
+development.
+
+30 minutes:
+
+Discuss cultural changes that need to be made, and how to approach them.
+Brainstorm with managers. Identify key managers, engineers, and architects to be
+agents of change within the organization.
+
+
1. FOSS quality
1a. Security Myths: