[UA-discuss] What are the main things to do in UASG?

[Don Hollander]

And, of course, we should have enough flexibility to change structure as we move through the project.

In the letter to the ICANN Board, a very long (10 year) horizon was set.   During that ten years some progress will occur (I hope some material progress will be seen in the next twelve months)

As progress occurs, then the program should be revised from time to time to make sure that we’re focusing the right resources in the right area.

As I’ve talked to people over the past twelve months about this issue, it is clear that it is BIG but not particularly difficult.   The past four weeks of discussion has shown it is really big, but achievable.

It will be good to get some idea of what successful milestones look like.

Don


> On 17/02/2015, at 7:53 am, Ram Mohan <rmohan at afilias.info> wrote:
> 
> Yes, from my point of view, the charter etc. should provide the rationale for why we gather, and what we want to focus our attention on (ie., what problem are we solving).
>  
> #3 below, Defining the problem space, in my opinion, is to get to the next levels of detail, and to provide structure and detail so we may get to prioritizing, etc.
>  
> -Ram 
>  
> ------------------------------------------------------------------------------
> Ram Mohan
> o: +1.215.706.5700 x103; m: +1.215.431.0958; f: +1.215.706.5701
> Skype: gliderpilot30
>  
> From: Christian Dawson [mailto:dawson at i2coalition.com <mailto:dawson at i2coalition.com>] 
> Sent: Monday, February 16, 2015 12:45 PM
> To: Nelson, Nick
> Cc: Ram Mohan SMTP; UA-discuss at icann.org <mailto:UA-discuss at icann.org>
> Subject: Re: [UA-discuss] What are the main things to do in UASG?
>  
> Totally agree with the concept of needing to know why we’re here, but I saw #3 slightly differently. A charter will define a broad scope and include a definition of the broad problem set. I’m taking a crack at that broad "Mission, Purpose and Need” in the draft Charter I’m taking first draft on.
>  
> What we’ll need at stage 3 is a deep dive into the scope of the issue - it’s various components and stakeholders. I think that’s a distinctly different project and worthy of its own point. 
>  
> So ultimately I agree, but think we can cover "Mission, Purpose and Need” sufficiently in the draft Charter to get by.
>  
> C
>  
>  
>> On Feb 16, 2015, at 9:39 AM, Nelson, Nick <nicknels at amazon.com <mailto:nicknels at amazon.com>> wrote:
>>  
>> I'm coming in a bit late but that gives me good perspective and I think the total list from Ram is accurate. However, I'd argue that both Christian is right with defining structure and charger, but also first - we should define the Problem space. 
>> 
>> The problem space to me is ultimately why we're all here right. "What are we trying to solve for?" and even more so, "How is this group going to benefit the ultimate end-user?" 
>> 
>> From: ua-discuss-bounces at icann.org <mailto:ua-discuss-bounces at icann.org> [ua-discuss-bounces at icann.org <mailto:ua-discuss-bounces at icann.org>] on behalf of Christian Dawson [dawson at i2coalition.com <mailto:dawson at i2coalition.com>]
>> Sent: Monday, February 16, 2015 9:22 AM
>> To: Ram Mohan SMTP
>> Cc: UA-discuss at icann.org <mailto:UA-discuss at icann.org>
>> Subject: Re: [UA-discuss] What are the main things to do in UASG?
>> 
>> Ram,
>>  
>> I think this is a good list with one proposed change. I am 3-4 pages into a draft charter for people to look at, which proposes a structure. I’d say we need an agreed-on structure before we pick leaders to fill defined roles, so I suggest flipping 1 and 2.
>>  
>> I probably can’t get far enough along to put my draft charter up for review until tomorrow - chairing a small anti-SPAM working group on SPAM in the Cloud at M3AAWG today. (If anybody else from this group is at M3AAWG come find me and we can chat/complain about timezones together.)
>>  
>> -Christian
>>  
>>> On Feb 14, 2015, at 11:21 AM, Ram Mohan <rmohan at afilias.info <mailto:rmohan at afilias.info>> wrote:
>>>  
>>> Team,
>>> Trying to get an inventory of the main tasks in front of the UASG, in chronological order:
>>>  
>>> 1.       Group leadership
>>> 2.       Group structure and charter
>>> 3.       Definition of problem space
>>> 4.       Prioritization of problem space
>>> 5.       Definition of approach to problem spaces
>>> 6.       Delegation of work
>>> 7.       Execution of work
>>> 8.       Follow-through
>>>  
>>> Appreciate input.
>>>  
>>> -Ram
>>>  
>>> ------------------------------------------------------------------------------
>>> Ram Mohan
>>> Executive Vice President & CTO
>>> Afilias |Ireland|Canada|USA|India
>>> o: +1.215.706.5700 x103; m: +1.215.431.0958; f: +1.215.706.5701
>>> Skype: gliderpilot30

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/mailman/private/ua-discuss/attachments/20150217/568b6558/attachment.html>