FW: PDP3.0 - Package 2 for Discussion on 17 Sept @ 13:00UTC
Hi All, I just realized I sent this to the bounce list by accident. My apologies. B From: Berry Cobb <Berry.Cobb@icann.org> Date: Sunday, September 15, 2019 at 16:51 To: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org> Subject: PDP3.0 - Package 2 for Discussion on 17 Sept @ 13:00UTC Hi All, Please find attached Package #2, which includes much of Improvement #11, #12 and #16. We will review through this package on our 17 Sep, 13UTC session. Here’s a short description and notes to consider before reviewing the package: * For Improvement #16, there’s an updated project work product catalog & deployment schedule. You’ll recall our prior discussion that this improvement was largely fulfilled by the standard work products defined under Improvement #11, but there was some discussion about how these would be rolled out to current groups. See the Work Product Catalog Deployment PDF for an initial suggestion based on the principle of not largely disrupting adoption for in-flight working groups. In short, all new groups will use the full catalog and only select work products will be used for in-flight groups under ownership from the GNSO Policy team. * The EPDP-P2 Project Package PDF is a live working example of the work products in action updated as of 31 August and is attached here for reference when comparing the descriptions in the Catalog. * An updated Status and Condition Change Procedure document is included as a part of Improvement #11. I separated the work products out used to manage thee project to create the Work Product Catalog documents above. With the exception of a few minor updates and acceptance of prior feedback, this content is largely unchanged. However, the open action here is to review the procedure against use cases. Two calls ago, we started down this path recognizing that the best use cases are our current “real” projects. We’ll pick up where we left off with the summary of projects on the GNSO Council Project List attached for your reference. Note, this was just distributed to the GNSO Council in prep for this coming week’s Council meeting. Please take few minutes to review those projects where the Status and Condition codes show a yellow or red indication. These start to test the Status and Condition Code Change Procedure (SCCCP). * As part of reviewing the use cases, one project will also involve Improvement #12 about notification of project/schedule changes to the GNSO Council. Attached is an EXAMPLE ONLY of the Project Change Request (PCR) form regarding the CCWG-AP. We can talk about the path for where this work product can be used and discuss at a high-level what the interactions should be among the WG leadership and the GNSO Council / Leadership. * I’ll be sharing my screen throughout this discussion, mostly referencing the Change Procedure diagram, but I will also have the Project List up for quick reference. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant
Hi Berry, Thank you very much for your note and the updated documents included in Package 2, which look good to me. I only have two comments: 1. Personally, I find these terminologies not as intuitive as I hoped but maybe it will take some time to become familiar and getting used to: GNSO Project Work Product Project Plan: a Gantt Chart Work Plan: a spreadsheet Fact Sheet: a spreadsheet (for resources/budget) 2. Package2_Rec11_Status-Condition-Procedure_v0.5 - At page 1, it says "Should a project encounter a situation where both the Status and Condition require a change, the Condition must be considered first" but the diagram on page 3 does not seem to reflect this and instead condition and status seem to be dealt with separately and in parallel. I might have misunderstood or missed something. Kind regards, Pam ------------------------------------------------------------------ Sender:Berry Cobb <Berry.Cobb@icann.org> Sent At:2019 Sep. 17 (Tue.) 05:08 Recipient:gnso-pdp3dot0-dt@icann.org <gnso-pdp3dot0-dt@icann.org> Subject:[GNSO-PDP3Dot0-DT] FW: PDP3.0 - Package 2 for Discussion on 17 Sept @ 13:00UTC Hi All, I just realized I sent this to the bounce list by accident. My apologies. B From: Berry Cobb <Berry.Cobb@icann.org> Date: Sunday, September 15, 2019 at 16:51 To: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org> Subject: PDP3.0 - Package 2 for Discussion on 17 Sept @ 13:00UTC Hi All, Please find attached Package #2, which includes much of Improvement #11, #12 and #16. We will review through this package on our 17 Sep, 13UTC session. Here’s a short description and notes to consider before reviewing the package: For Improvement #16, there’s an updated project work product catalog & deployment schedule. You’ll recall our prior discussion that this improvement was largely fulfilled by the standard work products defined under Improvement #11, but there was some discussion about how these would be rolled out to current groups. See the Work Product Catalog Deployment PDF for an initial suggestion based on the principle of not largely disrupting adoption for in-flight working groups. In short, all new groups will use the full catalog and only select work products will be used for in-flight groups under ownership from the GNSO Policy team. The EPDP-P2 Project Package PDF is a live working example of the work products in action updated as of 31 August and is attached here for reference when comparing the descriptions in the Catalog. An updated Status and Condition Change Procedure document is included as a part of Improvement #11. I separated the work products out used to manage thee project to create the Work Product Catalog documents above. With the exception of a few minor updates and acceptance of prior feedback, this content is largely unchanged. However, the open action here is to review the procedure against use cases. Two calls ago, we started down this path recognizing that the best use cases are our current “real” projects. We’ll pick up where we left off with the summary of projects on the GNSO Council Project List attached for your reference. Note, this was just distributed to the GNSO Council in prep for this coming week’s Council meeting. Please take few minutes to review those projects where the Status and Condition codes show a yellow or red indication. These start to test the Status and Condition Code Change Procedure (SCCCP). As part of reviewing the use cases, one project will also involve Improvement #12 about notification of project/schedule changes to the GNSO Council. Attached is an EXAMPLE ONLY of the Project Change Request (PCR) form regarding the CCWG-AP. We can talk about the path for where this work product can be used and discuss at a high-level what the interactions should be among the WG leadership and the GNSO Council / Leadership. I’ll be sharing my screen throughout this discussion, mostly referencing the Change Procedure diagram, but I will also have the Project List up for quick reference. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant
participants (2)
-
Berry Cobb -
Pam Little