update process doc #269
Open
update process doc #269
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chair28980
commented
Oct 25, 2024
fryorcraken
approved these changes
Oct 28, 2024
| | Epic | Several per milestone | Set for a milestone | Usually one subteam or external team (e.g. DST) | Subteam Lead or Member | Milestone work for a given subteam. | | ||
| | Task | Many per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. | | ||
| | Deliverable | Several per milestone | Set for a milestone | Subtean leads | Subteam Lead or Member | Milestone work for a given subteam. | | ||
| | Epic | Several per deliverable | Set for a deliverable | Usually one subteam or external team (e.g. DST) | Subteam Lead or Member | Milestone work for a given subteam. | |
There was a problem hiding this comment.
Suggested change
| | Epic | Several per deliverable | Set for a deliverable | Usually one subteam or external team (e.g. DST) | Subteam Lead or Member | Milestone work for a given subteam. | | |
| | Epic | Several per deliverable | Set for a deliverable | One subteam | Subteam Lead | The work of a team for a given deliverable. | |
As discussed, we move away from epics for several subteam (dogfood) or for non waku teams (QA).
One epic = work of a waku subteam for a given deliverable.
subteam lead is accountable to ensure work is delivered, dogfed and handed over to QA, DST, eco dev or other waku subteam.
| | Task | Many per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. | | ||
| | Deliverable | Several per milestone | Set for a milestone | Subtean leads | Subteam Lead or Member | Milestone work for a given subteam. | | ||
| | Epic | Several per deliverable | Set for a deliverable | Usually one subteam or external team (e.g. DST) | Subteam Lead or Member | Milestone work for a given subteam. | | ||
| | Task | Several per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. |q |
There was a problem hiding this comment.
Suggested change
| | Task | Several per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. |q | |
| | Task | Several per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. | |
| | Task | Many per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. | | ||
| | Deliverable | Several per milestone | Set for a milestone | Subtean leads | Subteam Lead or Member | Milestone work for a given subteam. | | ||
| | Epic | Several per deliverable | Set for a deliverable | Usually one subteam or external team (e.g. DST) | Subteam Lead or Member | Milestone work for a given subteam. | | ||
| | Task | Several per Epic | Set monthly-ish, delivered weekly | One subteam or individual | Team Member | May be one or several piece of work, client specific. |q | ||
|
|
||
| ## Milestone Definition | ||
|
|
||
| A *Milestone*: |
There was a problem hiding this comment.
This is now a "Deliverable" definition. But I think we can remove the "bundle" concept
| - SHOULD be added to a GitHub Milestone. | ||
| - MUST have a matching GitHub issue in the relevant team's repo. | ||
| - MUST have a label with format `Epic`. | ||
| - MUST be added to the description of the parent _Deliverable_ issue. | ||
| - SHOULD have a `Planned Start` and `Due Date` set (these are GitHub projects fields you can find in the `Projects` section of the issue view sidebar). |
There was a problem hiding this comment.
We need dates on deliverables too, right?
| - MUST have an _acceptance criteria_ and/or a list of _tasks_ (that can be other GH issues). | ||
|
|
||
| Finally, for _Tasks_ that do not belong to a given _Epic_ or _Milestone_: | ||
| Finally, for _Tasks_ that do not belong to a given _Epic_ or _Deliverable_: |
There was a problem hiding this comment.
maybe specified that a task MUST belong to an epic or have one of those below.
| - `dependencies`: Upgrade dependencies in a timely manner to avoid time wasting when the dependency upgrade becomes critical. | ||
|
|
||
| - `bug`: This is a bug, likely reported by a user | ||
| - `maintenance`: This is maintenence work that is out of the scope of the technical roadmap |
There was a problem hiding this comment.
Suggested change
| - `maintenance`: This is maintenence work that is out of the scope of the technical roadmap | |
| - `maintenance`: This is maintenance work that is out of the scope of the technical roadmap |
| - In the GitHub milestone, we have a list of _Epics_ to be achieved, the _Epics_ are being closed as the work is done and handed over. | ||
| - To look at remaining work for an _Epic_, one need to look at all issues (_Tasks_) with the corresponding _Epic_ label (`E:...`) | ||
| - Milestones and Deliverables are defined in the pm repo | ||
| - Deliverables have many epics, one epic per team |
There was a problem hiding this comment.
Suggested change
| - Deliverables have many epics, one epic per team | |
| - Deliverables have one or several epics, one epic per subteam |
| - To look at remaining work for an _Epic_, one need to look at all issues (_Tasks_) with the corresponding _Epic_ label (`E:...`) | ||
| - Milestones and Deliverables are defined in the pm repo | ||
| - Deliverables have many epics, one epic per team | ||
| - Team lead is responsible to ensure Vac-QA is aware of changes, but no need to create a QA epic |
There was a problem hiding this comment.
Let's have a table
| Task | Responsible | Accountable |
|---|---|---|
| Set Milestones and Deliverables in master document | Waku Lead | Insights |
| Create GitHub milestones and deliverables issues in pm repo | Program Manager | Waku Lead |
| Create epic for team | Team Lead | Program Manager |
| Create issues, PR (tasks) and link them to epics | Team Member | Team Lead |
| Close epic | Team Lead | Program Manager |
| Close deliverable | Waku Lead | Program Manager |
| Handover to Vac-QA, Vac-DST | Team Lead | Vac PoC (?) |
| Proceed with Dogfooding | Team Lead | Waku Lead |
Responsible: who does it
Accountable: delegates and review
Waku Lead: @fryorcraken
Program Manager: @chair28980
Team Lead: @plopezlpz @Ivansete-status @jm-clius @weboko
Vac PoC: @jm-clius (?)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update process doc and readme.
Needs mermaid flow chart update.