Work Split

[AlexanderLanin]

1. Operational (Infrastructure & Tooling) Team Responsibilities

• This team focuses on setting up, managing, and maintaining infrastructure and tooling topics that are relevant to most or all feature teams.
• Examples include managing shared resources such as docs-as-code systems, compilers, and GitHub configurations.

2. Cross Functional Feature Teams Responsibilities

• The Cross Functional Feature Teams are responsible for using, adapting, and extending infrastructure and tooling that is specific to their feature development needs.

3. Collaborative Responsibilities, Especially in Early Stages

• During the initial weeks or months, close collaboration between teams will be critical to avoid bottlenecks and ensure alignment:
  • Example: If all feature teams require a C++ compiler but the operational team has competing priorities, feature teams may contribute directly to its setup or improvement.
• To ensure infrastructure and services meet user needs, pilot users from feature teams should be actively involved:
  • Operational team and pilot users collaborate closely through feedback loops, shared development efforts, or direct contributions.
• Cultural Collaboration: To avoid siloing, it is essential to foster a culture where feature and operational teams continuously exchange knowledge and expertise.

What do you think? Do you agree? Disagree? Have a different proposal? Leave a comment!

[hoe-jo]

Should we include that input for the operation should be based on requirements?

[MaximilianSoerenPollak]

I think that makes sense, but even if not that I think it would be important to make sure that there are tight constraints on what is requested as to make sure we can accurately implement what is needed.