Date: Tue, 19 Mar 2024 08:26:33 +0000 (UTC) Message-ID: <2075876807.1973.1710836793311@community1.lax.icann.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1972_752831453.1710836793310" ------=_Part_1972_752831453.1710836793310 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Summary of recommendation: ALAC should develop strategic and ope= rational plans (including performance criteria and cost information) as par= t of ICANN=E2=80=99s planning process.
Summary of tasks in implementation:
Rec. |
Sub-Task |
Implementation Task |
Status |
Notes |
---|---|---|---|---|
5.1 |
|
Identify barriers within ALAC process= es used to contribute to strategic planning and propose follow=E2=80=90up&n= bsp; |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the ongoing responsibility for this task will be disseminated a= mongst the ALAC Chair, the Executive Committee, the Director of At-Large, a= nd RALO leaders. |
|
5.1(a) |
Ratify the strategic planning process reflect=
ed in the flowchart titled =E2=80=9CFigure C-1: Proposed At-Large Str=
ategic Planning Process=E2=80=9D (see Appendix 2), by which the ALAC could =
contribute to ICANN=E2=80=99s strategic planning. |
Complete |
See: ALAC At-Large Policy Advice Development (PAD=
) Process Workspace |
|
5.1(b) |
Review and amend the ALAC=E2=80=99s strategic= planning process yearly, in line with annual amendments to ICANN=E2=80=99s= overall strategic planning process. |
Complete |
See: ALAC At-Large Policy Advice Development (PAD=
) Process Workspace |
|
5.1(c) |
Conduct periodic =E2=80=9CSWOT=E2=80=9D (stre=
ngths, weaknesses, opportunities and threats) analyses of the At-Large stra=
tegic planning process, in conjunction with the RALOs (as WT C did), and co=
mpare the results of these analyses to identify areas that have improved or=
deteriorated. |
Complete |
The ALAC and its Improvements Taskforce estab=
lished that the ongoing responsibility for this task will be disseminated a=
mongst ALAC Chair, the Executive Committee, the Director of At-Large, and R=
ALO leaders. |
|
5.1(d) |
Articulate ALAC=E2=80=99s and At-Large=E2=80=
=99s vision and mission. |
Substantially Complete |
See: At-Large Improvements Implementation Taskforc= e Workshop 13-03-2012 |
|
5.1(e) |
Use appropriate metrics to ensure that the AL=
Ses are diverse, effective and well-informed. |
Complete |
The ALAC and its Improvements Taskforce estab=
lished that the ongoing responsibility for the establishment and =
review of these measures is allocated to the Metrics SC and the ALAC as a w=
hole. The ALAC Metrics sub-committee will begin operation in March 201=
2. |
|
5.1(f) |
Initiate, develop and maintain an institution= al knowledge management and retention system for At-Large. |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the continuing Action Items on this sub-task will be disse= minated amongst At-Large Staff and At-Large Members as past and present Mem= bers of the ALAC and At-Large Community and will be required to integrate w= ith required future ICANN wide systems. |
|
5.1(g) |
Encourage the five RALOs to coordinate their = outreach and =E2=80=9Cinreach=E2=80=9D policies in order to facilitate the = search for new skill sets needed within At-Large. |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the ongoing responsibility for this task will be disseminated a= mongst the ALAC Chair, the Executive Committee, the Director of At-Large, a= nd RALO leaders. |
|
5.1(h) |
Continue actively pursuing At-Large growth, f=
or the overall benefit of ICANN. |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the ongoing responsibility for this task will be disseminated a= mongst the ALAC Chair, the Executive Committee, the Director of At-Large, a= nd RALO leaders. |
|
5.1(i) |
In attempting to get the ALAC=E2=80=99s outre= ach projects funded, emphasize their role not only as a strategic resource = benefiting the ALAC and RALOs but also as part of a wider ICANN legitimacy = process. |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the ongoing responsibility for this task will be disseminated a= mongst the ALAC Chair, the Executive Committee, the Director of At-Large, a= nd RALO leaders. |
|
5.1(j) |
Continue to encourage ICANN to prioritize and= increase funding for outreach activities. |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the ongoing responsibility for this task will be disseminated a= mongst the ALAC Chair, the Executive Committee, the Director of At-Large, a= nd RALO leaders. |
5.2 |
|
Identify barriers within ALAC process= es used to contribute to operational planning and propose follow=E2=80=90up= |
Substantially Complete = td> |
|
|
5.2(a) |
Ratify the operational and financial planning=
process reflected in the flowchart titled =E2=80=9CFigure C-3: Propo=
sed At-Large Operational and Financial Planning Process=E2=80=9D (see Appen=
dix 2), by which the ALAC could contribute to ICANN=E2=80=99s operational a=
nd financial planning. |
Complete |
The ALAC has determined that, for this action=
item to be effective, it must be performed on a recurring schedule. =
The item has been completed previously on February 2012, and the ALAC and I=
CANN Staff will consider when it should be next repeated by the At-Large co=
mmunity once every year in January. |
|
5.2(b) |
Acknowledge and encourage a continuation of t=
he better collaboration between the ALAC and ICANN=E2=80=99s Finance staff =
seen in preparing the FY2012 Budget. |
Complete |
|
|
5.2(c) |
Conduct periodic =E2=80=9CSWOT=E2=80=9D (stre=
ngths, weaknesses, opportunities and threats) analyses of the At-Large oper=
ational and financial planning process, in conjunction with the RALOs (as W=
T C did), and compare the results of these analyses to identify areas that =
have improved or deteriorated. |
Complete |
|
|
5.2(d) |
Formalize the process by which the ALAC colle= cts operational demands from the RALOs and includes them in its operational= plans. |
Complete |
See: ALAC At-Large Policy Advice Development (PAD= ) Process Workspace |
|
5.2(e) |
Clearly estimate and document the time requir= ed for the ALAC=E2=80=99s operational processes (e.g., responding to a call= for Public Comments) and use these estimates to formalize its operational = processes. |
Substantially Complete |
This sub-task is in progress, but its co= mpletion will depend on current changess in ICANN processes. |
|
5.2(f) |
Continue requesting face-to-face funded gener= al assemblies (GAs) for each RALO every three years and an At-Large Summit.= |
Substantially Complete |
See: At-Large Event Roadmap&n=
bsp; |
|
5.2(g) |
Continue to assist the RALOs in completing th= eir annual ICANN requests for funding, as needed, in terms of writing, pack= aging and advocacy. |
Complete |
The ALAC has determined that, for this action= item to be effective, it must be performed on a recurring schedule. = The item has been completed previously on February 2012, and the ALAC and I= CANN Staff will consider when it should be next repeated by the At-Large co= mmunity once every year in January. |
5.3 |
|
Review ongoing At=E2=80=90Large staff= support levels and budget allocations in FY2009=E2=80=9010 and increase su= pport as provided throughout this project, consistent with recommendations = in Final Report |
Complete |
The ALAC and its Improvements Taskforce estab= lished that the ongoing responsibility for this task will be disseminated a= mongst ALAC Chair and the Director of At-Large. |
|
5.3(a) |
Continue to monitor its level of needed staff=
support and ICANN=E2=80=99s commitment to and progress in filling open sta=
ff positions. |
Complete |
|
|
5.3(b) |
ALAC and staff should develop an annual suppo= rt agreement |
Withdrawn |
This task is no longer relevant due to the fo= llowing changes within ICANN in recent years (i.e., since submission of the= ALAC Review Final Report):* An increase in staff resources dedicated to At= -Large (as of September 2011, all allotted At-Large staff positions had bee= n filled);
|