Organising Issues, Epics and Milestones

[fryorcraken]

This issue described how Waku's project work is organized to help with tracking and reporting.

Requirements

The current reporting requirements are 2 folds:

1. Weekly Reporting

Weekly reporting by sub-team of progress on milestones. See https://notes.status.im/waku-2023-report as the initiating document

2. Monthly Reporting

Monthly reporting is current done in a private Google Sheet and has 3 majors sections:

• Progress on yearly milestones (10 milestones as defined in https://notes.status.im/Uz9HeCwZTDSYyOq36Q54cA#, now marked as Epics).
• Key achievements/highlights of previous month
• Planned achievement for next month

The Google Sheet will soon be replaced by a dashboard that extract data using GitHub with the ability to organise the data by epic using GitHub labels.

Terminology

Moving forward, the proposed terminology is:

Name	Number of	Time Scope	Team Scope	Description
Priority Track	3-5	Year	All sub-teams	Focus for the Waku project for the year, must be aligned with Logos Collective's priorities.
Epic	<=10	Year	Several sub-team per Epic	Scoped work to deliver each Priority Track. Set for the year.
Milestone	Few per Epic	Quarter

• Priority Track: 3-5 tracks that are the focus for the Waku project for the year and should be aligned with Logos Collective's priority. These tracks may impacts several Waku sub-teams.
• Epic: For each Priority Track, a number of high level deliverables are identified (=<10) and used as key deliverables for the year.
• Milestone

[fryorcraken]

Will do PR instead as it's a timeless document.