mirror of
https://github.com/logos-co/roadmap.git
synced 2025-02-02 19:33:37 +00:00
create processes page
This commit is contained in:
parent
d71aa8408a
commit
1e29ee81c8
24
content/waku/process.md
Normal file
24
content/waku/process.md
Normal file
@ -0,0 +1,24 @@
|
|||||||
|
---
|
||||||
|
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.
|
Loading…
x
Reference in New Issue
Block a user