How to plan and coordinate work items for Partnerships / Community Guidance

[choldgraf]

Context

Now that we have two new team members with time to dedicate outside of engineering ( @2i2c-org/partnerships-and-community-guidance ), we should decide how to coordinate and organize our work items.

Our current coordination / planning workflow has been used in the @2i2c-org/tech-team for a while, and the "source of truth" for what we're working on is in the Team Backlog and stewarded / managed by @damianavila .

Proposal

We should decide what kind of of system @2i2c-org/partnerships-and-community-guidance wishes to use for things like:

• Tracking and shaping work items
• Triaging and prioritizing work
• Tracking planned and development work, as well as unplanned operational work and toil
• Time-boxing and having checkpoints
• Collaborating and communicating amongst team members

This might be as simple as "just do what we already do via our current team processes", but given that this team has significantly different kinds of deliverables / work items / etc, I feel that @jmunroe and @colliand should decide what works best for them. Either way, we should find ways to make sure this team remains connected to the @2i2c-org/tech-team.

Updates and actions

No response

[choldgraf]

cc also @damianavila - I'd be curious to hear your thoughts on this one as well since you are helping keep track of all the WIP in our backlog already.