The 2i2c Team Compass#
This team compass defines the policies and practices for 2i2c.
The Team Compass is the Source of Truth!. Here’s a breakdown of responsibility, and see About the Team Compass for background.
Overall structure: The Delivery Enablement team along with the Executive Director is responsibile for the system and structure of the Team Compass.
Organization-wide sections apply to the entire organization. The Executive Director, Delivery Enablement, and People Operations teams are responsible for these sections, but all team members are encouraged to contribute.
Functional areas are a way for teams to define their own practices, policies, and team documentation. The leads of each area are responsible for the content of these sections.
Below is a brief overview of our top-level structure.
Organizational documents#
These documents cover the whole organization and are relevant to everybody at 2i2c.
Organization wide
- Organization
- People operations
- Scope and responsibilities
- KPIs for People
- Expectations of team members
- Hiring process and information
- Compensation and Benefits
- People Management
- Planning for professional development
- Personal and professional development: time and money
- Job titles and levels
- Taking time off
- Cost reduction decision making framework
- Open source strategy
- Finance and accounting
- Administration
- Team-wide practices
Functional Areas#
Functional areas each have their own leads, goals, and structures.
Areas of work
- Delivery Enablement
- Business Development
- Business Development Overview
- Strategic plan for Business Development
- Key Performance Indicators for BD
- Roles in Business Development
- Pricing strategy
- Sales Operations
- Engagement management
- Creating alignment
- Workflow for hub service leads
- Grants and projects workflow
- Engagement Workflow Overview
- Using FreshDesk
- Track Hub Usage with Grafana
- Meetings in Business Development
- Marketing and outreach
- Product and Services
- Engineering
- Scope and responsibilities
- Structure and roles
- Workflow
- Engineering work definition of ready
- Communicating changes to our communities
- Technical strategy
- Accounts and cloud access
- Secrets, credentials, and passwords
- Merge and Code Review policy
- GitHub repository conventions
- Style guide for repositories
- Team meeting archive
Managed JupyterHubs Service#
2i2c oversees a single major effort, which is building a sustainable service to make interactive computing with open source infrastructure more accessible and scalable. We act as a cross-functional team around this service, and share many responsibilities and duties. We document some major aspects of this service in the sections below.
Team Reference#
Reference and archival information for our teams.