From 614caa1a4d11a9ac9052a2a6c32a4842a959bb5e Mon Sep 17 00:00:00 2001 From: chair28980 Date: Tue, 6 Feb 2024 15:50:36 -0800 Subject: [PATCH 1/6] add milestone scoping process flow --- PROCESS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/PROCESS.md b/PROCESS.md index b887171..3723dab 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -31,6 +31,13 @@ A *Milestone*: 3. **Transversal:** While the vertical scope of a milestone should be minimal, the delivery should be complete in terms of research, engineering, QA, documentation and dev rel assets so that the feature can be pushed to users once the milestone is marked as complete. Feedback loops should be as small as possible to ensure the value of a milestone is measured in a timely manner. 4. **Attached Estimate:** An estimate should be associated with the milestone to facilitate the measurement of potential ROI. Additionally, tracking the estimate versus the actual progress is crucial for identifying any deviation and making informed decisions (e.g., deciding whether to continue if we learn the estimate is likely to be overrun). +## Milestone scoping process flow + +1. *Milestone outline defined* - Objective, scope and deliverables outlined in Milestone Issue. +2. Epic and tasks discussed and scoped in description - break down Milestones into Epics and specific tasks within the Epics, detailing the work required to accomplish each Epic. +3. Revision and Acceptance - Milestone is reviewd by Lead, revision round if necessary and accepted. +4. Kickoff scheduled and executed + ## Epics and Workflow A *milestone* is divided in *Epics*. Each *epic* is assigned to a given subteam. From 88f92c4e50749a8b4639978a34e2b29dfd565615 Mon Sep 17 00:00:00 2001 From: chair28980 Date: Tue, 6 Feb 2024 15:51:58 -0800 Subject: [PATCH 2/6] smol edit --- PROCESS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROCESS.md b/PROCESS.md index 3723dab..6a188c5 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -33,7 +33,7 @@ A *Milestone*: ## Milestone scoping process flow -1. *Milestone outline defined* - Objective, scope and deliverables outlined in Milestone Issue. +1. Milestone outline defined - Objective, scope and deliverables outlined in Milestone Issue. 2. Epic and tasks discussed and scoped in description - break down Milestones into Epics and specific tasks within the Epics, detailing the work required to accomplish each Epic. 3. Revision and Acceptance - Milestone is reviewd by Lead, revision round if necessary and accepted. 4. Kickoff scheduled and executed From 217ddf4debc686aa8f1bb7e300ae092c73e24e5b Mon Sep 17 00:00:00 2001 From: chair28980 Date: Tue, 6 Feb 2024 15:55:24 -0800 Subject: [PATCH 3/6] moar smol edits --- PROCESS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/PROCESS.md b/PROCESS.md index 6a188c5..b43f00d 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -36,7 +36,8 @@ A *Milestone*: 1. Milestone outline defined - Objective, scope and deliverables outlined in Milestone Issue. 2. Epic and tasks discussed and scoped in description - break down Milestones into Epics and specific tasks within the Epics, detailing the work required to accomplish each Epic. 3. Revision and Acceptance - Milestone is reviewd by Lead, revision round if necessary and accepted. -4. Kickoff scheduled and executed +4. Epics and Tasks created in Github. +5. Kickoff scheduled and executed. ## Epics and Workflow From bea614084f96d33d42eff47802b4a690acfb31ea Mon Sep 17 00:00:00 2001 From: chair28980 Date: Thu, 8 Feb 2024 09:44:28 -0800 Subject: [PATCH 4/6] update scoping process flow to phases --- PROCESS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/PROCESS.md b/PROCESS.md index b43f00d..61cf1b0 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -33,11 +33,11 @@ A *Milestone*: ## Milestone scoping process flow -1. Milestone outline defined - Objective, scope and deliverables outlined in Milestone Issue. -2. Epic and tasks discussed and scoped in description - break down Milestones into Epics and specific tasks within the Epics, detailing the work required to accomplish each Epic. -3. Revision and Acceptance - Milestone is reviewd by Lead, revision round if necessary and accepted. -4. Epics and Tasks created in Github. -5. Kickoff scheduled and executed. +Phase 1: Waku lead defines the scope within the milestone. The scope is then discussed asynchronously in the comments of the Github issue by relevant subteams and stakeholders, scope of Epics and subtasks are defined. + +Phase 2: During a Waku PM call, the team reviews the Milestone to confirm scope or identify areas that require additional scoping. + +Phase 3: If the scope is agreed upon, the team can now create epics and schedule work. ## Epics and Workflow From 47356593309c32d64c685fbb8c5988e562b7610e Mon Sep 17 00:00:00 2001 From: chair28980 Date: Thu, 8 Feb 2024 09:45:46 -0800 Subject: [PATCH 5/6] misc edits --- PROCESS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PROCESS.md b/PROCESS.md index 61cf1b0..1427e68 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -33,11 +33,11 @@ A *Milestone*: ## Milestone scoping process flow -Phase 1: Waku lead defines the scope within the milestone. The scope is then discussed asynchronously in the comments of the Github issue by relevant subteams and stakeholders, scope of Epics and subtasks are defined. +Phase 1: Waku lead defines the scope within the Milestone. The scope is then discussed asynchronously in the comments of the Github issue by relevant subteams and stakeholders, scope of Epics and subtasks are defined. Phase 2: During a Waku PM call, the team reviews the Milestone to confirm scope or identify areas that require additional scoping. -Phase 3: If the scope is agreed upon, the team can now create epics and schedule work. +Phase 3: If the scope is agreed upon, the team can proceed to create Epics and schedule work for kickoff. ## Epics and Workflow From 0b6ead2ca77943b56482ab2025e97f2f94f7137c Mon Sep 17 00:00:00 2001 From: chair <29414216+chair28980@users.noreply.github.com> Date: Thu, 8 Feb 2024 17:06:43 -0800 Subject: [PATCH 6/6] Update PROCESS.md Co-authored-by: fryorcraken <110212804+fryorcraken@users.noreply.github.com> --- PROCESS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROCESS.md b/PROCESS.md index 1427e68..a2048ca 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -33,7 +33,7 @@ A *Milestone*: ## Milestone scoping process flow -Phase 1: Waku lead defines the scope within the Milestone. The scope is then discussed asynchronously in the comments of the Github issue by relevant subteams and stakeholders, scope of Epics and subtasks are defined. +Phase 1: Waku lead defines the scope within the Milestone. The scope is then discussed asynchronously in the comments of the GitHub issue by relevant subteams and stakeholders, scope of Epics and subtasks are defined. Phase 2: During a Waku PM call, the team reviews the Milestone to confirm scope or identify areas that require additional scoping.