Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Latest commit

 

History

History
40 lines (27 loc) · 2.37 KB

00_getting_started.md

File metadata and controls

40 lines (27 loc) · 2.37 KB
Raw

Embrace InnerSource

Harness the collective intelligence of your organization

logo

What are we going to learn, and why?

Getting started:

  • Introductions (name, title/specific role in your organization)
  • Agenda and high level overview of what to expect
  • Identify a "parking lot" for questions
  • Discuss class logistics (timing of course, recording, etc)
  • After class office hours to support 30, 60, 90 day goals

◀ Our focus will be on the topics you see listed on the left in the navigation bar. ◀

Why is this important to you?

As leaders of your organization, team members will rely on you to embrace the InnerSource mentality and to help enable teams across the organization to adopt these InnerSource practices.

At the end of this course, you should have a path forward and answers to questions specific to your organization around the What, Why, and How of InnerSource. We will end with a 30, 60, and 90 day checklist compiled from each lens of InnerSource to help you measure InnerSource success within your organization.

⌨️ Activity: Organization pulse

Purpose: To gain a high-level pulse of the organization. (Time: ~10 minutes)

  1. Raise your ✋ hand if you identify with the following question from the provided list below.
  2. The instructor will tally each raised hand on each question for a collective pulse.

Raise your hand if you identify with the following:

  • Are you overwhelmed by the amount of code there is to maintain within your organization?
  • Do you discover that teams have written code that duplicates functionality written by another team?
  • Do you find that teams rewriting code they inherited because they don't understand it, or feel it’s no good, only to encounter issues encountered before?
  • Are you aware of code running in production that you wouldn't feel comfortable showing to someone else?
  • Are you aware of teams struggling to communicate and collaborate effectively across time, geographic, cultural boundaries?
  • Are you wanting to contribute to Open Source but finding existing internal processes don’t support this?
  • Do you recognize opportunities to increase levels of openness, transparency and participation within your organization?

!> Important Discussion Question(s):

What is the most challenging part of developing software in your organization?