-
Notifications
You must be signed in to change notification settings - Fork 3
Product team roles, responsibilities, and activities
Stephen Diesel @ EOS Network Foundation edited this page Jun 14, 2022
·
9 revisions
- Public channels are typically better than DMs
- Try to evaluate whether the meeting can be accomplished via thread
- Breakout rooms are a great way to work asynchronously on brainstorms in smaller groups
- Small talk rocks
- Share screen to give context
- Open is better than closed
- Careful about generating noise
- Only comment if you have something to add to the disucssion
- Avoid drive-by opinions
- Provide context
- Use URLs as much as possible or #-based links to other issues!
- Cross referencing reinforces organic collaboration
- Having accurate links to all supporting materials provide maximum context
- Easier to come back to rich documentation than just pieces
- Roadmap maintenance
- Core Protocol team Product Ownership
- Feedback collection
- Stakeholder management
- RFP Authoring support - depending on capacity, product may support the authoring of certain RFPs. Naturally, backlog refinement will occasionally give way to bodies of work worth compiling and authoring as RFP instead of dedicating time from the Core ENF Dev team.