Please find below the details for the Joint (GNSO) Standing Committee on ICANNs Budget & Operations and (ccNSO) SOPC Planning call on Wednesday, 26 January 2022 at 14:00 UTC for 1 hour. 

For other times: https://tinyurl.com/5n7np5p4

PROPOSED AGENDA

  • Introductions to group’s leadership teams and introductory comments (7 minutes)
  • Discuss topics of interest related to FY23 draft documents (link [docs.google.com] to full agenda) (50 minutes)
    • Resources allocated for Policy Development and Advice
    • Supplemental Fund for Implementation of Community Recommendations
    • Reserve Fund
    • Operating Initiatives
  • Next steps & closing (3 minutes)


Links to Relevant Documents:

 

SCBO Schedule:

  • 15 Dec 2021 – SCBO meeting #01 @14:00 UTC to conduct initial review of draft documents
  • 05 Jan 2022 – SCBO meeting #02 @14:00 UTC
  • 07 Jan 2022 – Deadline to submit clarifying questions
  • 12 Jan 2022 – SCBO meeting #03 @14:00 UTC
  • 19 Jan 2022 – SCBO meeting #04 @14:00 UTC
  • 20 Jan 2022 – GNSO Council Meeting (update to Council)
  • 26 Jan 2022 – SCBO meeting #05 @14:00 UTC (joint session with the CCNSO’s SOPC)
  • 31 Jan 2022 – Submit draft to GNSO Council for review
  • 02 Feb 2022 – SCBO meeting #06 @14:00 UTC (as required)
  • 07 Feb 2022 – Close of public comments on FY23 draft documents; due by 23:59 UTC
  • 17 Feb 2022 – GNSO Council Meeting
  • 05 Mar 2022 – ICANN73

BACKGROUND DOCUMENT


RECORDINGS

Audio Recording

Zoom Recording

Chat Transcript

PARTICIPATION

Attendance

 

Notes/ Action Items


Welcome and Roll call 2 minutes

  • None

 

Introductions to group’s leadership teams 5 minutes

  • Sebastien has volunteered to serve as vice-chair.
  • Andreas Musielak is the new chair and Irina Danelia is the vice-chair.

 

Major Findings

Major Findings SCBO + Q&A / Major Findings SOPC + Q &A)

 

  • Shift in focus. Generally focus only on Operating Initiatives 3 and 4, which focus on policy development. and 14, which concentrates on project management. However, need to focus more on implementation, particularly for IRTs.
  • Second focus is that many of the past comments from the SCBO related to software and tools have been supported, via other functions. There is also the SFICR now, which the SCBO believes is reason to ensure ICANN is aware of the forecast of upcoming work.
  • Resource allocations – asked for increases and ICANN has delivered. Does the SOPC plan to consider? The SOPC believes it will be difficult to hire and expects the lower range of projected new hires. Not always clear how new hires will benefit the community in particular.
  • In terms of identifying upcoming work and resource intensity, GNSO created an extract of upcoming work from its program management tools. This helps make clear what work will continue and likely begin in the upcoming FY.
  • The SOPC wants have a conversation with HR to determine rationale for increases in staffing levels.
  • Q: What is specifically unclear, to help understand if HR is the right group? A: 37 new hires, but it is unclear how they are allocated across functions and it is also unclear how the community benefits. Also important to understand what factors the Org uses to determine when additional resources are needed.
  • What initiates increases in FTEs – a department/function identifies and demonstrates a need, why that work requires additional FTE, level/qualifications, how the new FTE fits in the org chart. Also requires exec approval, review from HR, and heads of finance and HR, and CEO.
  • SFICR is for implementation work spanning more than one FY and exceeds $2million. This work seemingly would have been covered by the contingency fund. The SOPC believes the answers from Org are sufficient to understand the SFICR. Noted that using the SFICR to fund the SSAD will be insufficient.
  • Support for budgeting 3 F2F meetings, even if that may not end up being the case. Believes there is a need for additional KPIs.
  • Q: Does the SCBO believe the projections for high, medium, low seem reasonable. A: Not something the SCBO has considered. Something the registries and registrars would have better understanding. In the past, the projections have been quite close. Are driven primarily by .com and .net.
  • The Operating Initiatives and Functional Activities have Targeted Outcomes. Are the additional KPIs needed relative to the Target Outcomes, or something different? KPIs were developed for IANA, which is service/transaction oriented. However, KPIs for other less operational activities (e.g., policy) is far different. There could potentially be KPIs to be considered for the community side.
  • Example of KPI that does not mean much – number of reports published in a year
  • The GNSO has focused on project management and effective planning, which helps inform comments to the budget.

 

Next Steps per group & exploring possible joint initiatives

Next Steps SCBO & initiatives + Q&A / Next Steps SOPC & Initiatives + Q&A 

  • SOPC wants to work jointly with ICANN to develop KPIs. Need to understand which projects are bringing the most benefit. Anything the GNSO can help to define the KPIs?
  • Seek to better understand factors and process for FTEs, rationale for any increases
  • Sebastien to run model on gTLD forecasting
  • Finance will seek to better account for SCBO/SOPC concerns proactively, and not just wait for public comments.
  • Share comments with other group, determine if there is any need for further discussion. SCBO will have a draft by 31 Jan.

 

AOB (2 minutes)

  • None

 

Future meetings, if any, wrap-up (5 minutes)

  • TBD, based on email exchanges?
  • Believes an additional meeting, not necessarily just jointly, to discuss headcount, would be helpful.

 

Closing

  • None


  • No labels