From 10e90ad3e478fe9b237f90198361b902a5e104f3 Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Wed, 5 Sep 2018 09:11:39 -0700 Subject: [PATCH 1/7] Charter for PM team --- charters/PM/charter.md | 60 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 charters/PM/charter.md diff --git a/charters/PM/charter.md b/charters/PM/charter.md new file mode 100644 index 00000000..ca6cd506 --- /dev/null +++ b/charters/PM/charter.md @@ -0,0 +1,60 @@ +# PM Team Charter + +## Description + +The Data Coordination Platform (DCP) PM team is responsible for the oversight of the Data Coordination Platform (DCP) *as product*, developing the shared understanding of the overall product vision, priorities, and release schedule with the community. + +The core team is composed of *Project Leads* and *Product Owners* from each DCP project, *DCP UX* (Voice of the Customer), and a *Science Program Manager*. + +## Definitions + +* 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 (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* + +* Develop standard processes and best practices for DCP community governance including (but not limited to): + * Program and technical oversight, decision making, and conflict resolution + * Charters for DCP projects + * Enhancements (RFC) to DCP software or governance + * Planning + * Communication + +* Review and approve non-technical charters for DCP projects + +* Act as final arbiter for escalated conflicts from the DCP community + +*Communication* +* Coordinate regular outreach and announcements to the DCP community and the HCA Science Leadership + +* Primary liaison between the HCA Science Leadership and the DCP community facilitated by the *Science Program Manager* + +*Planning* + +Strategic + +* Identify and maintain a repository of user requirements, use cases, and journeys informed by *DCP UX* research + +* Facilitate a `` planning process 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 + +Tactical + +* Translate the customer priorities from the Thematic Roadmap RFC into actionable quarterly plans + +* Coordinate with the DCP Architecture team on emerging tactical requests needing to be addressed in Sprint planning priorities + +* Maintain the DCP project management *dashboard* to ensure visibility into the *state of play* (issues, dependencies, progress) across the DCP projects + +## Out-of-scope + +*Intentionally Blank* + +### Slack Channels + +HumanCellAtlas/dcp-project-mgmt:This channel is for PM(s) to discuss coordination and logistics. \ No newline at end of file From 27efe56d05096a969fd8ee84b3190eebba3fe5af Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Wed, 5 Sep 2018 09:18:37 -0700 Subject: [PATCH 2/7] Minor editorial change --- charters/PM/charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/PM/charter.md b/charters/PM/charter.md index ca6cd506..ce5910c8 100644 --- a/charters/PM/charter.md +++ b/charters/PM/charter.md @@ -2,7 +2,7 @@ ## Description -The Data Coordination Platform (DCP) PM team is responsible for the oversight of the Data Coordination Platform (DCP) *as product*, developing the shared understanding of the overall product vision, priorities, and release schedule with the community. +The Data Coordination Platform (DCP) PM team is responsible for the oversight of the DCP *as product*, developing the shared understanding of the overall product vision, priorities, and release schedule with the community. The core team is composed of *Project Leads* and *Product Owners* from each DCP project, *DCP UX* (Voice of the Customer), and a *Science Program Manager*. From 3ed088929adc8311d7f3bc064fe2f74713a8968a Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Tue, 2 Oct 2018 14:41:59 -0700 Subject: [PATCH 3/7] Added mailing list --- charters/PM/charter.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/charters/PM/charter.md b/charters/PM/charter.md index ce5910c8..c3b4c561 100644 --- a/charters/PM/charter.md +++ b/charters/PM/charter.md @@ -57,4 +57,8 @@ Tactical ### Slack Channels -HumanCellAtlas/dcp-project-mgmt:This channel is for PM(s) to discuss coordination and logistics. \ No newline at end of file +HumanCellAtlas/dcp-project-mgmt:This channel is for PM(s) to discuss coordination and logistics. + +### Mailing List + +Team email: pm@data.humancellatlas.org \ No newline at end of file From 6a0937e0ac93069473f3bfbe41c17529598c7561 Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Wed, 10 Oct 2018 15:42:59 -0700 Subject: [PATCH 4/7] Added role defintions --- charters/PM/charter.md | 42 +++++++++++++++++++++++++++++++++++------- 1 file changed, 35 insertions(+), 7 deletions(-) diff --git a/charters/PM/charter.md b/charters/PM/charter.md index c3b4c561..c023ddd4 100644 --- a/charters/PM/charter.md +++ b/charters/PM/charter.md @@ -1,4 +1,4 @@ -# PM Team Charter +# PM (_Program, Product, or Project Management_) Team Charter ## Description @@ -8,11 +8,36 @@ The core team is composed of *Project Leads* and *Product Owners* from each DCP ## Definitions -* 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 +### Project Lead -* **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 +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. + +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. + +### Product Owner +As adapted from the [Scrum process](https://www.scrumguides.org/scrum-guide.html#team-po), a **Product Owner** manages the [Product Backlog](https://www.scrumguides.org/scrum-guide.html#artifacts-productbacklog) for their DCP project including: +>* Clearly expressing Product Backlog items +>* Ordering the items in the Product Backlog to best achieve goals and missions +>* Optimizing the value of the work the Development Team performs +>* Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next +>* Ensuring the Development Team understands items in the Product Backlog to the level needed + +**NOTE**: The responsibilities of the **Project Lead** and **Product Owner** are tightly intertwined. At an overly simplistic level, the **Project Lead** is more responsible for strategic objectives while the **Product Owner** drives tactical execution. In actual practice, it is a close partnership when planning and coordinating development with other projects. + +### Science Program Manager + +The **Science Program Manager** is the formal liaison between HCA Science Leadership and the DCP community. + +*Current Science PM*: [Jonah Cool](jcool@chanzuckerberg.com) + +### 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 @@ -40,7 +65,7 @@ Strategic * Identify and maintain a repository of user requirements, use cases, and journeys informed by *DCP UX* research -* Facilitate a `` planning process to solicit input from the HCA Science and DCP communities +* 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 Tactical @@ -51,13 +76,16 @@ Tactical * Maintain the DCP project management *dashboard* to ensure visibility into the *state of play* (issues, dependencies, progress) across the DCP projects +* Monitor user metrics and analyze the resulting data set to improve the quality of the DCP and inform HCA Science Leadership + + ## Out-of-scope *Intentionally Blank* ### Slack Channels -HumanCellAtlas/dcp-project-mgmt:This channel is for PM(s) to discuss coordination and logistics. +HumanCellAtlas/dcp-project-mgmt: This channel is for PM(s) to discuss coordination and logistics. ### Mailing List From b911aa6fc74c078d69f3fd727c8236cd1e1a0960 Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Wed, 10 Oct 2018 15:57:56 -0700 Subject: [PATCH 5/7] Simplify strategic UX description --- charters/PM/charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/PM/charter.md b/charters/PM/charter.md index c023ddd4..e0723fa2 100644 --- a/charters/PM/charter.md +++ b/charters/PM/charter.md @@ -63,7 +63,7 @@ A **Thematic Roadmap** identifies and expresses customer needs as a small collec Strategic -* Identify and maintain a repository of user requirements, use cases, and journeys informed by *DCP UX* research +* 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 From 7e7da5b3bc6cd05e168109c7a17b64a3c1e4d547 Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Fri, 12 Oct 2018 10:16:39 -0700 Subject: [PATCH 6/7] Editorial updates to Slack Channels --- charters/PM/charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/PM/charter.md b/charters/PM/charter.md index e0723fa2..cf0d6884 100644 --- a/charters/PM/charter.md +++ b/charters/PM/charter.md @@ -85,7 +85,7 @@ Tactical ### Slack Channels -HumanCellAtlas/dcp-project-mgmt: This channel is for PM(s) to discuss coordination and logistics. +[HumanCellAtlas/dcp-project-mgmt](https://humancellatlas.slack.com/messages/dcp-project-mgmt): This channel is for PM(s) to discuss coordination and logistics. ### Mailing List From acfb4b951f292b02efadc9aea49ccf9f30e1f83a Mon Sep 17 00:00:00 2001 From: Brian Raymor Date: Tue, 16 Oct 2018 14:08:46 -0700 Subject: [PATCH 7/7] Removed thematic roadmaps --- charters/PM/charter.md | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/charters/PM/charter.md b/charters/PM/charter.md index cf0d6884..43886e53 100644 --- a/charters/PM/charter.md +++ b/charters/PM/charter.md @@ -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](jcool@chanzuckerberg.com) -### 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