-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7e7da5b
commit acfb4b9
Showing
1 changed file
with
4 additions
and
13 deletions.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,7 +10,7 @@ The core team is composed of *Project Leads* and *Product Owners* from each DCP | |
|
|
||
| ### Project Lead | ||
|
|
||
| When a DCP charter is approved, the community explictly delegates authority and leadership for a specific project and its scope to a **Project Lead**. The **Project Lead** is responsible for clearly defining and communicating the long-term vision and direction of the project. | ||
| When a DCP charter is approved, the community explictly delegates authority and leadership for a specific project and its scope to a **Project Lead**. The **Project Lead** is responsible for clearly defining and communicating the long-term vision and direction of their project. | ||
|
|
||
| Similar to [Mozilla module owners](https://www.mozilla.org/en-US/about/governance/policies/module-ownership/), **Project Leads** are never *tyrants*. They are chartered to make decisions for their DCP project with input from the community and in the best interests of the community. | ||
|
|
||
|
|
@@ -26,19 +26,10 @@ As adapted from the [Scrum process](https://www.scrumguides.org/scrum-guide.html | |
|
|
||
| ### Science Program Manager | ||
|
|
||
| The **Science Program Manager** is the formal liaison between HCA Science Leadership and the DCP community. | ||
| The **Science Program Manager** is the formal liaison for requests between HCA Science Leadership and the DCP community. | ||
|
|
||
| *Current Science PM*: [Jonah Cool]([email protected]) | ||
|
|
||
| ### Thematic Roadmap | ||
| A **Thematic Roadmap** identifies and expresses customer needs as a small collection of themes or strategic objectives which: | ||
| * Focuses the DCP community on a documented set of high-level customer priorities | ||
| * Excites users about the future of DCP | ||
|
|
||
| ### Request for Comments | ||
|
|
||
| **Request for Comments (RFC)** is the transparent process that manages all significant enhancements to the DCP software technical and governance documentation, both normative and informative | ||
|
|
||
| ## In-scope | ||
|
|
||
| *Governance* | ||
|
|
@@ -66,11 +57,11 @@ Strategic | |
| * Identify and maintain a repository of user personas and stories informed by *DCP UX* research | ||
|
|
||
| * Facilitate a planning process on a regular cadence to solicit input from the HCA Science and DCP communities | ||
| * Publish a Thematic Roadmap RFC based on that input that also adddresses strategic technical objectives from the DCP Architecture team | ||
| * Publish a roadmap based on this input that also adddresses strategic technical objectives from the DCP Architecture team | ||
|
|
||
| Tactical | ||
|
|
||
| * Translate the customer priorities from the Thematic Roadmap RFC into actionable quarterly plans | ||
| * Translate the customer priorities from the roadmap into actionable quarterly plans | ||
|
|
||
| * Coordinate with the DCP Architecture team on emerging tactical requests needing to be addressed in Sprint planning priorities | ||
|
|
||
|
|
||