diff --git a/leads/governance.md b/cross-functional/governance.md similarity index 86% rename from leads/governance.md rename to cross-functional/governance.md index 56d9d0ce..c9ce23c5 100644 --- a/leads/governance.md +++ b/cross-functional/governance.md @@ -1,6 +1,6 @@ # Making decisions -Functional areas and their team leads follow our [Principles of decision making](../operations/governance.md). +Functional areas and their leads follow our [Principles of decision making](../operations/governance.md). This section describes more specific ways in which decisions usually happen. ## Decision-making scope @@ -10,14 +10,14 @@ This means that most decisions are made by individuals without requiring a consu ### Within-area decisions -For decisions that primarily affect their area and no others, team leads are empowered to make decisions within their own team without requiring consent from team members of other areas. +For decisions that primarily affect their area and no others, area leads are empowered to make decisions within their own group without requiring consent from team members of other areas. However, they should make decisions transparently and inclusively, especially if they think another area will be interested in the decision. They are also empowered to _delegate_ scoped decision-making authority to others at 2i2c. ### Cross-organization decisions -There are a few kinds of decisions that require discussion and agreement from our team leads: +There are a few kinds of decisions that require discussion and agreement from our area leads: - Decisions with significant financial impact across 2i2c - Decisions that will significantly impact our capacity or commit ourselves to more work diff --git a/leads/index.md b/cross-functional/index.md similarity index 69% rename from leads/index.md rename to cross-functional/index.md index f4e1d1ec..141fd868 100644 --- a/leads/index.md +++ b/cross-functional/index.md @@ -1,4 +1,4 @@ -# Cross-team leadership +# Cross-functional processes ```{toctree} overview.md diff --git a/leads/overview.md b/cross-functional/overview.md similarity index 79% rename from leads/overview.md rename to cross-functional/overview.md index ae655f95..169d8be1 100644 --- a/leads/overview.md +++ b/cross-functional/overview.md @@ -1,13 +1,8 @@ # Scope and responsibilities -The Team Leads group is a bit different than most other 2i2c teams. -It has a cross-organizational scope and focuses on high-level priorities, strategy, and ensures we are distributing attention and resources across the organization correctly. +Our cross-functional processes focus on high-level priorities, strategy, and ensures we are distributing attention and resources across the organization correctly. -Team leads are representatives of their respective areas in 2i2c. -They advocate for the goals and needs of those areas. -They also bridge and coordinate strategy, prioritization, and resources across 2i2c. - -Here are their major responsibilities: +Here are this area's major responsibilities: ## Embody our values and team practices diff --git a/cross-functional/roles/chief-of-staff.md b/cross-functional/roles/chief-of-staff.md new file mode 100644 index 00000000..8e22efcc --- /dev/null +++ b/cross-functional/roles/chief-of-staff.md @@ -0,0 +1,6 @@ +```{role} Chief of Staff +``` +# Chief of Staff + +This role is new to 2i2c, and needs to be refined in the coming months. +For information about our acting Chief of Staff, see [](../../engineering/roles/delivery-manager.md). \ No newline at end of file diff --git a/cross-functional/roles/executive-assistant.md b/cross-functional/roles/executive-assistant.md new file mode 100644 index 00000000..debadce9 --- /dev/null +++ b/cross-functional/roles/executive-assistant.md @@ -0,0 +1,8 @@ +```{role} Executive Assistant +``` +# Executive Assistant + +We partner with [VaVaVirtual](https://vavavirtual.com/) for Executive Assistant support. +This role supports a variety of needs across our leadership team. + +Our executive assistant is Camille Gonzalez. diff --git a/cross-functional/structure.md b/cross-functional/structure.md new file mode 100644 index 00000000..78d34e95 --- /dev/null +++ b/cross-functional/structure.md @@ -0,0 +1,22 @@ +# Structure and roles + +The area leads group is composed of representatives from each area (usually, the Area Lead), who advocate for the goals and needs of those areas. +However, the policies and ideas in this area apply to all of 2i2c. + +## Area leads + +Below is the current list of area leads: + +- **Executive**: {role}`Executive Director` and {role}`Chief of Staff` +- **Partnerships**: {role}`Partnerships Lead` +- **Engineering**: {role}`Engineering Manager` / {role}`Technology Lead` +- **Product**: {role}`Product Lead` + +(cross-functional:roles)= +## Team roles + +```{toctree} +:glob: +:maxdepth: 2 +roles/* +``` diff --git a/leads/workflow.md b/cross-functional/workflow.md similarity index 91% rename from leads/workflow.md rename to cross-functional/workflow.md index 6b8efe23..cb7d683c 100644 --- a/leads/workflow.md +++ b/cross-functional/workflow.md @@ -1,6 +1,10 @@ (leads:workflow)= # Workflow +```{warning} Out of date +Our cross-team workflow is being significantly re-worked, and this information is out of date. +``` + This section describes how our leadership team carries out its planning and day-to-day work. (leads:meeting:organizational-strategy)= diff --git a/engineering/roles/delivery-manager.md b/engineering/roles/delivery-manager.md new file mode 100644 index 00000000..05412480 --- /dev/null +++ b/engineering/roles/delivery-manager.md @@ -0,0 +1,47 @@ +```{role} Delivery Manager and Chief of Staff +``` +# Delivery Manager / Chief of Staff + +```{note} +This role is new, and we must define its responsibilities, metrics for success, etc more clearly. +As a starting point to describe this role, below we provide the text we used in the job posting. +``` + +We’re looking for a **Delivery Manager** who will serve as a key facilitator in ensuring the successful and efficient delivery of [our product](https://2i2c.org/service/) . Acting as a servant leader, you’ll guide our engineering team, promote collaboration, and eliminate obstacles to deliver high-quality results that are aligned with our mission and goals. + +In addition to your role as a Delivery Manager, we’re keen to have this person to take on responsibilities of a **Chief of Staff** role, organizing cross-functional work, enabling transparency in decision-making, and fostering a cohesive work environment. + +We’re ideally looking for someone who has experience of leading or facilitating globally distributed and remote-first teams, asynchronous working and coaching teams in agile best practices. + +## What you’ll do + +As a Delivery Manager you’ll be primarily responsible for the detailed planning and day-to-day management of engineering tasks, and will also act as a servant-leader to resolve and remove any blockers that individual team members may be experiencing. + +Reporting into the Engineering Manager, you’ll work closely with them on running the day-to-day delivery related tasks on their behalf. To do this you’ll be someone with extensive experience in running agile delivery processes including planning, running retrospectives, and driving continuous improvement. + +You’ll collaborate with others, in particular the Product Manager, to design a process for balancing Sprint Goal work, support tasks, reactive tasks, and upstream work that is driven by open source community needs. + +In addition to this primary role, you’ll take on responsibilities as the **Chief of Staff**, working closely with the Executive Director. In this role you’ll be responsible for **organizing cross-functional work, enabling transparency in decision-making, and fostering a cohesive work environment**. + +## About you + +You’re a Delivery Manager who understands the principles and purpose and not just the ceremonies of agile. You’ll bring experience in optimizing the delivery process, fostering collaboration and ensuring that our product priorities are delivered in the most optimal fashion, all while upholding and coaching others in the principles of agility and continuous improvement. + +### Essential experience + +- Proficient in agile frameworks (Scrum, Kanban, Lean) with a deep understanding to effectively apply agile principles. +- In-depth understanding and extensive experience of working with software engineers to enhance their day-to-day experience and optimize product delivery. +- Strong communication skills to facilitate effective team collaboration and lead the team through various project phases. +- Ability to engage and communicate with stakeholders, manage expectations, and promote alignment with goals and objectives. +- Proficiency in coordinating the efforts of remote teams, ensuring efficient collaboration and productivity. +- Strong analytical and problem-solving abilities to address impediments, make informed decisions, and keep work on track. + + +### Useful qualities + +- Facilitating globally distributed and remote-first teams. +- Asynchronous working and associated best practices. +- Creating and overseeing systems of work that organize distributed teams. +- Facilitating teams who in addition to their day-to-day work actively contribute to open-source. +- Working directly with Platform, DevOps or Site Reliability engineers. +- Understanding the challenges of contributing to and leading community-driven open source technology projects. \ No newline at end of file diff --git a/index.md b/index.md index 5c4d7c6c..639b376c 100644 --- a/index.md +++ b/index.md @@ -48,7 +48,6 @@ operations/index people/index open-source/index finance/index -product/index administration/index ``` @@ -61,9 +60,10 @@ Functional areas each have their own leads, goals, and structures. :caption: Functional Areas :maxdepth: 2 -leads/index +cross-functional/index engineering/index partnerships/index +product/index ``` (index:hubs-service)= diff --git a/leads/structure.md b/leads/structure.md deleted file mode 100644 index 7a492a3e..00000000 --- a/leads/structure.md +++ /dev/null @@ -1,18 +0,0 @@ -# Structure and roles - -The team leads group is composed of leaders from various areas of 2i2c. - -## Team leads - -Below is the current list of team leads: - -- **Organization-wide**: {role}`Executive Director` -- **Partnerships**: {role}`Partnerships Lead` -- **Engineering**: {role}`Engineering Manager` / {role}`Technology Lead` - -## Executive assistant - -We partner with [VaVaVirtual](https://vavavirtual.com/) for Executive Assistant support. -This role supports a variety of needs across our leadership team. - -Our executive assistant is Camille Gonzalez. diff --git a/partnerships/workflow.md b/partnerships/workflow.md index 257fbc04..25e0840a 100644 --- a/partnerships/workflow.md +++ b/partnerships/workflow.md @@ -66,7 +66,7 @@ Infrastructure services operated by 2i2c are managed through the [infrastructure CS&S uses AirTable to process and store tabular data. They store a record of **all invoices and executed agreements** with 2i2c's partners. -See [our Invoices and Contracts section](../../finance/contracts.md) for information about this table. +See [our Invoices and Contracts section](../finance/contracts.md) for information about this table. ### DocuSign diff --git a/product/index.md b/product/index.md index 39382c23..4b8ced3c 100644 --- a/product/index.md +++ b/product/index.md @@ -5,6 +5,7 @@ They work alongside engineering teams to define ways in which we aim to improve ```{toctree} overview.md +structure.md pricing/strategy pricing/cost-model ``` diff --git a/product/roles/product-lead.md b/product/roles/product-lead.md new file mode 100644 index 00000000..1f9b7175 --- /dev/null +++ b/product/roles/product-lead.md @@ -0,0 +1,52 @@ +```{role} Product Lead +``` +# Product Lead + +```{note} +This role is new, and we must define its responsibilities, metrics for success, etc more clearly. +As a starting point to describe this role, below we provide the text we used in the job posting. +``` + +The Product Lead is a senior-level role that will be instrumental in shaping 2i2c’s product vision, strategy, and execution of our "product function" within the team. You'll own the product vision, align it with user needs, and translate it into a clear product roadmap which defines cross-functional priorities and guides our partnerships and engineering teams, enabling efficient product delivery and continuous improvement. + +You’ll have a good level of technical understanding and be genuinely interested in the 2i2c offering, ideally having worked previously with platform teams and/or worked at a very detailed level alongside engineers and/or were a software Engineer yourself. In addition, recent experience in, or a good understanding of, [Product Operations](https://blog.logrocket.com/product-management/product-operations/) would be essential to your success in this role. + +## What you'll do + +The Product Lead would work with others, in particular the Delivery Manager and the Engineering Manager, to design a process to measure and track the flow of work through the team. You’ll shape the future of our product by gathering and distilling ideas from the collective group, fostering a shared vision. Working collaboratively, you’ll drive the development of our product and effectively position the product as a key function within our organization. + +On a day to day basis you’ll: + +- Define and own the product vision and strategy assuming ‘the voice of the user’, and doing so collaboratively and inclusively with our team and key stakeholders. +- Create a clear product roadmap that guides the engineering and partnerships teams and ensures alignment with the organizational vision. +- Collaborate closely with our engineers and users in partner organizations (researchers, educators etc.) to translate the product roadmap into actionable plans and tasks, managing a structured product backlog and sign-off of completed deliverables. +- Prioritize the product backlog based on impact, feasibility, and partner needs, ensuring alignment with the product roadmap. +- Define and manage a system to integrate and prioritize reactive tasks and contributions from the JupyterHub open-source community, which will in some instances shape the product direction in real-time. +- Working collaboratively with users to understand their news, gathering feedback and insights that shape the product vision and roadmap. +- Elicit insights and incorporate the deep experience from the Engineering team into the product vision and roadmap. +- Measure and enhance efficiency, quality, and flow within the product development lifecycle, incorporating ProductOps principles. +- Optimize processes to ensure a smooth and streamlined flow of work, promoting a structured and efficient product delivery approach. + + +## About you + +Your expertise in product management will complement the profound knowledge of our existing Engineering and Partnerships teams, as well as our partner and key stakeholder communities. + +### Essential experience + +- Previously worked with platform products and teams and/or worked at a very detailed level alongside engineers. +- Proficient in defining and articulating a clear product vision and strategy, aligning it with partner needs and organizational goals. You must be able to do this collaboratively and inclusively. +- Excellent communication and stakeholder management skills, ensuring a thorough understanding of requirements and fostering effective collaboration with internal and external stakeholders. +- Strong ability to translate product vision into a structured roadmap, prioritizing features and tasks based on impact, feasibility, and partner needs. +- In-depth understanding and experience with the product development lifecycle, from ideation to delivery. +- Familiarity with Product Ops principles, focusing on enhancing efficiency, quality, and flow within the product development lifecycle. +- Skilled in optimizing processes to ensure a smooth and streamlined flow of work. +- Strong grasp of technical concepts and proficient communication skills to effectively engage with engineering teams, comprehending the technical intricacies of product development. +- Proven expertise in the application of user-centric research and design principles and methodologies. + +### Nice to have skills + +- Experience working with distributed and remote-first teams, understanding the challenges and dynamics associated with remote collaboration. +- Experience with asynchronous working and associated best practices, allowing for productivity and collaboration across different time zones. +- Familiarity with open-source contributions, gained from environments where open-source collaboration and contributions are common. +- Experience working directly with Platform, DevOps, or Site Reliability engineers, understanding the intricacies of platform-based product design and development. \ No newline at end of file diff --git a/product/structure.md b/product/structure.md new file mode 100644 index 00000000..3f4f72f1 --- /dev/null +++ b/product/structure.md @@ -0,0 +1,12 @@ +# Structure and roles + +## Current roles + +```{toctree} +:glob: +roles/* +``` + +## Membership + +See [list of team members](../reference/team.md).