[Product/Project] Protocol PM Knowledge Transfer & Onboarding

[Olshansk]

Objective

This ☂️ ticket organizes links, references and details to onboard a PM (Project/Product/Program/Protocol) Manager to the protocol team. It acts as a central point of coordination to capture questions, discussions and results to enable a new core team member to own and drive the project and product direction of the protocol.

Goals

• Communicate: Improve communication within the core protocol team and between the core team and the community so they have visibility into what we're working on. Avoid anyone needing to ask: "What's the protocol team working on?`
• Streamline: Update, add or remove processes to streamline how to help the team function effectively.
• Update: Update scope, revisit timelines, clarifying deliverables, etc...
• Deliver: Support the protocol team, in whatever way necessary, to deliver a TestNet in Q3/Q4.

Origin Document

Lots of documentation with details is not useful if no one reads it. Scope that's too broad is applicable in some cases, and scope that's very granular is applicable in others. We need to find a balance that tends to what the team, org, community and project requires.

This Video intends just to show a quick walkthrough of what we have, but everything is fully captured in the links below.

Click on the link above to view. Screenshot preview below:

Links

• Roadmap
  • V1 Roadmap on GitHub
  • V1 Milestones on GitHub
  • E2E Feature List
  • Github Issues backlog on GitHub
  • Note: None of the milestones have all the issues created a head of time. We add issues "just in time" as things come up for the near/distant future, or on an at-needed basis
• V1 Dashboard
  • V1 Dashboard Settings
• Devlogs
  • Devlog template
  • Example Devlog
• Weekly Sync
• Iteration Planning
• Protocol Iteration Retros
• Protocol Hours
• Protocol <> PNF

Deliverable

Weekly Sync

• Update (IF needed) the template for weekly sync
• Get up to speed on leading the weekly sync

Iteration Planning

• Update (IF needed) the template for iteration planning
• Get up to speed on leading the iteration planning

Devlog

• Update (IS needed) the DevLog Template
• Streamline the process of transferring iteration goals & results to public Devlog
• Announce & live stream at least one public DevLog with the community

V1 Dashboard

• Update (IF needed) the v1 dashboard
• Update (if needed) the v1 dashboard settings

V1 Roadmap & Backlog

• Update (IS needed) the V1 Roadmap
  • Update both timelines, details, scope and community to the community
• Get up to speed on the E2E Feature List

---

Creator: @Olshansk
Co-Owners: Matthew

[Olshansk]

@mokn Could you PTAL and let us know if you have any additional thoughts or updates for this onboarding ticket?

[Olshansk]

@RossiNYC One of the deliverables of this ticket is taking over DevLogs. Would you be comfortable submitting the one for this week?