Improvement #16 - Confirmation
Hi All, Per our meeting last week and discussion around Improvement #16, please find attached a rationale for how this improvement can be satisfied.
From GNSO PDP 3.0 Implementation Plan:
#16. Criteria for PDP WG Updates Ensure standardized set of information provided by PDP WGs GNSO Council to provide criteria for information that needs to be provided by PDP WG leadership teams as part of their updates to be in a position to closely track progress and identify issues at an early stage. This would include a requirement for a PDP WG to provide early warning as well as identify potential risks that could hamper progress. Staff should develop a template for reporting with criteria and information to be shared in PDP WG updates such as issues, risks, progress against work plan See #11 - Adapt fact sheet that is being used for EPDP Team to template so it can also be used for other efforts Staff / May 2019 As presented in prior meetings for Improvement #11, multiple work products were created or updated to compliment the new feature of Status and Conditions codes being applied to our GNSO projects. The intent of those work products is to provide greater project management discipline. One such component of effective project management is project communications, which is what Improvement #16 mostly sets out to accomplish. Reviewing the work product descriptions (as attached in the catalog) achieves the #16 objectives by providing standard sets of information when WG leadership teams update the GNSO Council via the newly enhanced project list or other special updates as required. In its most common form, the Project Situation Report (also a part of the GNSO Project List) will be used as the authoritative work product to provide said updates. The other work products will be included the communications package as necessary based on the requirements of the update requested and as fulfilled by the WG Leadership team and staff support. The early warning component of the Improvement #16 objective listed above can also be satisfied by the soon to be completed escalation procedure as part of the Status/Condition feature presented under of Improvement #11. I will have a set of use cases for review by the PDP3.0 team to compliment the escalation procedure discussion shortly. Regarding implementation of Improvement #16, consistent use of these standard work products is also a requirement. However, it may not make sense to deploy these to all in-flight projects we have today, especially those that are nearing completion as it may disrupt continuity of previous communications on their work plans. It also may not make sense to devote time in developing fully developed Gantt chart project plans for these in-flight groups either. Thus, the deliverable here, also as a part of implementing #11, staff will commit to storing templates of these work products for use on newly formed working groups or other efforts launched by the GNSO Council. They will also be deployed for in-flight groups where it makes practical sense and as determined by the working group leadership team and staff support. At a minimum, the Project Situation Report is now deployed on the GNSO Council Project List (1st edition 22 August 2019). The EPDP Phase 2 will also continue to use the full spectrum of work products as recently submitted to the GNSO Council for its consideration. I've attached it here for in-use reference and convenience. One final note, the last work product published in the attached catalog is the Project Change Request form. This has yet to be discussed specifically by the PDP3.0 in regards to part of Improvement #12, but it is suggested as a part of the escalation procedure in Improvement #11. Perhaps this component can also be packaged together? Absent any objections, staff will include #16 and #12 as part of a consolidated package for Improvement #11. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant
Thanks, Berry. I agree that implementing this process for PDPs nearing completion may be disruptive. Can staff provide the target end dates for current PDPs? When we deliver this, we should consider making a recommendation as to which PDPs would be appropriate for use now. I’m thinking RPM PDP phase 2 because I think the other PDPs (excluding the EPDP) are nearing final reports. Darcy From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces@icann.org> on behalf of "mail@berrycobb.com" <mail@berrycobb.com> Date: Monday, August 26, 2019 at 2:29 AM To: "gnso-pdp3dot0-dt@icann.org" <gnso-pdp3dot0-dt@icann.org> Subject: [GNSO-PDP3Dot0-DT] Improvement #16 - Confirmation Hi All, Per our meeting last week and discussion around Improvement #16, please find attached a rationale for how this improvement can be satisfied.
From GNSO PDP 3.0 Implementation Plan: #16. Criteria for PDP WG Updates
Ensure standardized set of information provided by PDP WGs GNSO Council to provide criteria for information that needs to be provided by PDP WG leadership teams as part of their updates to be in a position to closely track progress and identify issues at an early stage. This would include a requirement for a PDP WG to provide early warning as well as identify potential risks that could hamper progress. Staff should develop a template for reporting with criteria and information to be shared in PDP WG updates such as issues, risks, progress against work plan See #11 - Adapt fact sheet that is being used for EPDP Team to template so it can also be used for other efforts Staff / May 2019 As presented in prior meetings for Improvement #11, multiple work products were created or updated to compliment the new feature of Status and Conditions codes being applied to our GNSO projects. The intent of those work products is to provide greater project management discipline. One such component of effective project management is project communications, which is what Improvement #16 mostly sets out to accomplish. Reviewing the work product descriptions (as attached in the catalog) achieves the #16 objectives by providing standard sets of information when WG leadership teams update the GNSO Council via the newly enhanced project list or other special updates as required. In its most common form, the Project Situation Report (also a part of the GNSO Project List) will be used as the authoritative work product to provide said updates. The other work products will be included the communications package as necessary based on the requirements of the update requested and as fulfilled by the WG Leadership team and staff support. The early warning component of the Improvement #16 objective listed above can also be satisfied by the soon to be completed escalation procedure as part of the Status/Condition feature presented under of Improvement #11. I will have a set of use cases for review by the PDP3.0 team to compliment the escalation procedure discussion shortly. Regarding implementation of Improvement #16, consistent use of these standard work products is also a requirement. However, it may not make sense to deploy these to all in-flight projects we have today, especially those that are nearing completion as it may disrupt continuity of previous communications on their work plans. It also may not make sense to devote time in developing fully developed Gantt chart project plans for these in-flight groups either. Thus, the deliverable here, also as a part of implementing #11, staff will commit to storing templates of these work products for use on newly formed working groups or other efforts launched by the GNSO Council. They will also be deployed for in-flight groups where it makes practical sense and as determined by the working group leadership team and staff support. At a minimum, the Project Situation Report is now deployed on the GNSO Council Project List (1st edition 22 August 2019). The EPDP Phase 2 will also continue to use the full spectrum of work products as recently submitted to the GNSO Council for its consideration. I’ve attached it here for in-use reference and convenience. One final note, the last work product published in the attached catalog is the Project Change Request form. This has yet to be discussed specifically by the PDP3.0 in regards to part of Improvement #12, but it is suggested as a part of the escalation procedure in Improvement #11. Perhaps this component can also be packaged together? Absent any objections, staff will include #16 and #12 as part of a consolidated package for Improvement #11. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant
participants (2)
-
Darcy Southwell -
mail＠berrycobb.com