status-im
/
samyoul-notes
mirror of https://github.com/status-im/samyoul-notes.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
samyoul-notes/attachments/2024-10/Feature Lifecycle - Team Fe...

3.2 KiB
Raw Permalink Blame History

Also see Feature Lifecycle - Team Requirements Also see Status Team Call Notes

Flexibility

  • 🎨 Design Team: Flexible in approach, especially the "3 Amigos" may sometimes be more than 3
  • 📄 Docs Team: Flexibility in documenting features and tracking changes.
  • 🖥️🔍 Desktop QA Team: Flexibility in when expert input is required and reducing formalities around user stories.
  • 🌐👛 Wallet Teams: Flexibility in feature flows and the documentation process.
  • 🌐🤘 Core Teams: Flexibility in technical specifications and iterating based on feedback. In many cases technical specs can't be written all at once and can only be discovered during development.

Improved Documentation and Communication

  • 📄 Docs Team: Concerned about documentation gaps, tracking changes, and automation in documentation processes.
  • 🖥️🔍 Desktop QA Team: Wants entry points for features in the development lifecycle, especially tracking parity across platforms.
  • 🌐🤘 Core Teams: Ensure technical specs are evolving.
  • Volo: Emphasises the importance of having a point of contact for any given feature, for clarity in communication.
  • 📱👛 Mobile Wallet Team: Moving documentation to GitHub for better tracking and closing issues.

Decision Recording

  • 📄 Docs Team: Formalising the process of documenting features and highlighting feature changes.
  • 🖥️🔍 Desktop QA Team: Needs better visibility into development processes and decision tracking.
  • 🌐🤘 Core Teams: Focus on recording decisions, technical specifications, and using living documents.
  • 📱🤘 Mobile Core Team: Recording decisions related to exiting (terminating a feature before completion) features and rationale for changes.

Feedback and Iteration

  • 🎨 Design Team: Features should be developed simultaneously across platforms to streamline feedback and iteration.
  • 📄 Docs Team: Focus on automating alerts when a feature reaches certain stages.
  • 🖥️🔍 Desktop QA Team: Ideation output and inputs from multiple teams should be visible and accessible.
  • 🌐🤘 Core Teams: Emphasise iterative development with feedback loops and continuous improvement of technical specs.
  • 🖥️👛 Desktop Wallet Team: Ensure feedback stages feed into ideation and roadmap planning.

Cross-Team Visibility and Coordination

  • 🖥️🔍 Desktop QA Team: Visibility into upcoming features and reconciling different development styles.
  • 🌐🤘 Core Teams: Input from different teams at various stages of the process.
  • 📱🤘 Mobile Core Team: Involvement of multiple "3 Amigos" may be necessary for larger epics and feature ideas from multiple sources.

Tools and Workspaces

  • 📄 Docs Team: Shared workspaces (e.g., Crews) and process automation.
  • 🖥️🔍 Desktop QA Team: Reconciling the use of GitHub and Notion.
  • 🌐👛 Wallet Teams: Moving to GitHub for better issue tracking and integration.
  • 📱🤘 Mobile Core Team: Considering tools like Notion with a voting system for feature prioritisation.