mirror of https://github.com/logos-co/roadmap.git
24 lines
704 B
Markdown
24 lines
704 B
Markdown
|
---
|
||
|
|
title: Processes
|
||
|
|
tags:
|
||
|
|
- Waku
|
||
|
|
date: 2024-03-10
|
||
|
|
lastmod: 2024-03-10
|
||
|
|
---
|
||
|
|
## Epic Owner
|
||
|
|
### Objective
|
||
|
|
This section defines the responsibilities of a Waku engineer assigned as the owner of an Epic within a Milestone.
|
||
|
|
|
||
|
|
### **Defining Deliverables and Acceptance Criteria**
|
||
|
|
Epic owners are responsible for:
|
||
|
|
- the clear definition of deliverables for the epic,
|
||
|
|
- aligning the work with Milestone objectives and expectations
|
||
|
|
- establishing acceptance criteria for each deliverable
|
||
|
|
- RAID evaluation for the epic
|
||
|
|
- risks
|
||
|
|
- assumptions
|
||
|
|
- issues
|
||
|
|
- dependencies
|
||
|
|
|
||
|
|
### Task Breakdown
|
||
|
|
The epic should be broken down into tasks for the relevant client-teams: nwaku, js-waku, go-waku, research, etc.
|