# Waku Project Management

## Teams

The Waku Team is comprised of the following subteams:

- Waku Research
- Waku Development nwaku, js-waku, go-waku
- Waku Chat

The Waku Team also gets the support from other Logos groups, in particular:

- [VAC/DST](https://vac.dev/): Distributed System Testing Team for simulations and QA/Testing
- Comms Hub: For communications, marketing, digital content, etc.

## Work Tracking and Project Management Process

See [PROCESS.md](./PROCESS.md)

## Reporting Guidelines

### Requirements

#### Weekly Reporting

Weekly reporting provides an insight on the progress by milestones.

### Reporting

**Weekly Updates**:

Report progress on each **active** Deliverables per sub-team.

Every week, all team members must add their update in the appropriate discord thread *WITH LINKS* to the GitHub **issues** (not pull requests) they own and worked on over the past week and/or plan to work on next week.

If work is done on several *Tasks* related to the same *Epic*, team members are free to link the common parent *Epic* issue.

Please include an update for the following categories:

- achieved: what was achieved this week.
- next: what will be worked on next.
- blocked: blocking items, not required if no blockers exist.

PM compiles the updates following sign-off from sub-team Leads and publishes to https://roadmap.logos.co.

### Process Flow

```md
Submit Updates (Everyone) - Tuesday
         │
         ▼
Review/Signoff (Leads) - Wednesday
         │
         ▼
Compile (PM) - Thursday
         │
         ▼
Publish (PM) - Monday
```

## Milestones

https://github.com/waku-org/pm/milestones