<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-ppsc-wg] Your feedback requested - Section 6.2.2.3 Deliverables and Timeframes
- To: "gnso-ppsc-wg@xxxxxxxxx" <gnso-ppsc-wg@xxxxxxxxx>
- Subject: [gnso-ppsc-wg] Your feedback requested - Section 6.2.2.3 Deliverables and Timeframes
- From: Marika Konings <marika.konings@xxxxxxxxx>
- Date: Mon, 17 May 2010 07:51:17 -0700
6.2.2.3 Deliverables and Timeframes
A Charter is expected to include some, if not all, of the following elements:
potential outcomes and/or expected deliverables, key milestones, and a target
timeline. Although the identification of specific work tasks, outcomes, and
deadlines might be perceived as constraining the WG in its activities, it is
also intended to provide guidance to the WG and prevent unintentional scope
creep. It should be emphasized that the WG can always ask the CO to reconsider
any of the deliverables or renegotiate deadlines identified by providing its
rationale.
In certain WGs, such as a Policy Development Process, the milestones and
timeline might be prescribed by the ICANN Bylaws. In other situations,
sufficient thought should be given to key milestones, realistic timelines, and
ways to inform and consult the ICANN Community (such as public comment
periods). It should be noted that any changes to milestone dates incorporated
in the charter will need to be cleared wit the CO.
________________________________
Comments:
CG: It may not always be possible to set timeframes in the charter. There
likely will be situations when the WG itself will need to be tasked with
producing a list of deliverables and an estimated timeframe. It is suggested
that the wording of this paragraph be adjusted to accommodate that.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|