Received: from PMBX112-E1-CA-1.pexch112.icann.org (64.78.40.26) by PMBX112-E1-VA-2.pexch112.icann.org (162.216.194.26) with Microsoft SMTP Server (TLS) id 15.0.1178.4 via Mailbox Transport; Mon, 10 Jul 2017 07:49:32 -0700 Received: from PFE112-CA-2.pexch112.icann.org (64.78.40.27) by PMBX112-E1-CA-1.pexch112.icann.org (64.78.40.26) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 10 Jul 2017 07:49:29 -0700 Received: from ppa3.lax.icann.org (192.0.33.78) by PFE112-CA-2.pexch112.icann.org (64.78.40.12) with Microsoft SMTP Server (TLS) id 15.0.1178.4 via Frontend Transport; Mon, 10 Jul 2017 07:49:29 -0700 Received: from pps.reinject (ppa3.lax.icann.org [127.0.0.1]) by ppa3.lax.icann.org (8.16.0.20/8.16.0.20) with ESMTPS id v6AEnTh4032586 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 10 Jul 2017 14:49:29 GMT Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [127.0.0.1]) by pps.reinject (8.16.0.20/8.16.0.20) with SMTP id v6AEnT5g032577 for ; Mon, 10 Jul 2017 14:49:29 GMT Received: from pechora1.lax.icann.org (pechora1.icann.org [192.0.33.71]) by ppa3.lax.icann.org with ESMTP id v6AEnSJi032576 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Jul 2017 14:49:28 +0000 Received: from smtp01.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id 5F0181E00F6; Mon, 10 Jul 2017 14:49:28 +0000 (UTC) Received: from mm.icann.org (mm.icann.org [192.0.32.100]) by smtp01.icann.org (Postfix) with ESMTP id 959D4E0444; Mon, 10 Jul 2017 14:49:27 +0000 (UTC) Received: from mm.icann.org (localhost [127.0.0.1]) by mm.icann.org (Postfix) with ESMTP id 5BBAF610AD0; Mon, 10 Jul 2017 14:49:27 +0000 (UTC) Received: from pechora1.lax.icann.org (pechora1.icann.org [192.0.33.71]) by mm.icann.org (Postfix) with ESMTP id 01CEA603A5C for ; Sat, 8 Jul 2017 23:26:04 +0000 (UTC) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:110:201::52]) by pechora1.lax.icann.org (Postfix) with ESMTP id C3C251E018C; Sat, 8 Jul 2017 23:26:03 +0000 (UTC) Received: by smtp2.arin.net (Postfix, from userid 323) id 860643992; Sat, 8 Jul 2017 19:25:43 -0400 (EDT) Received: from ASHEDGE02.corp.arin.net (ashedge02.corp.arin.net [199.43.0.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTPS id F4237112; Sat, 8 Jul 2017 19:25:42 -0400 (EDT) Received: from CAS01ASH.corp.arin.net (10.4.30.62) by ASHEDGE02.corp.arin.net (199.43.0.123) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sat, 8 Jul 2017 19:25:25 -0400 Received: from CAS01ASH.corp.arin.net (10.4.30.62) by CAS01ASH.corp.arin.net (10.4.30.62) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 8 Jul 2017 19:25:36 -0400 Received: from CAS01ASH.corp.arin.net ([fe80::4803:bd5b:dc93:20f6]) by CAS01ASH.corp.arin.net ([fe80::4803:bd5b:dc93:20f6%18]) with mapi id 15.00.1210.000; Sat, 8 Jul 2017 19:25:36 -0400 From: Cathy Handley To: Karen Mulberry CC: "ssr2-coordination@icann.org" , James Gannon Subject: Re: [Ssr2-coordination] Action Item #44 Draft Statement of Work for the SSR2-RT Technical Writer Thread-Topic: [Ssr2-coordination] Action Item #44 Draft Statement of Work for the SSR2-RT Technical Writer Thread-Index: AQHS93ERbNZCFSQPw0WqMZp/fclzV6JKlB7V Sender: "ssr2-coordination-bounces@icann.org" X-MS-Exchange-MessageSentRepresentingType: 2 Date: Sun, 9 Jul 2017 00:25:35 +0100 Message-ID: <9F5CDC9D-54A6-40F5-8648-294425883419@arin.net> References: <16461D23-583D-43EC-808D-03CC1AFD0AEA@icann.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <16461D23-583D-43EC-808D-03CC1AFD0AEA@icann.org> Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthSource: PFE112-CA-2.pexch112.icann.org X-MS-Has-Attach: yes X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: Content-Type: multipart/mixed; boundary="_004_9F5CDC9D54A640F58648294425883419arinnet_" MIME-Version: 1.0 --_004_9F5CDC9D54A640F58648294425883419arinnet_ Content-Type: multipart/alternative; boundary="_000_9F5CDC9D54A640F58648294425883419arinnet_" --_000_9F5CDC9D54A640F58648294425883419arinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Karen, Thanks for this, I think it will come in handy as we move forward. As I di= scussed with Larissa in Johannesburg I don't see a rush on this item. We a= re just now getting our sub team work started and that should be our focus.= As our work progresses it should help clarify our needs, however I can't = imagine that we will be at that point until later this year. Perhaps this = is something we should tee up for Abu Dhabi. Thanks again for sending this out. Have a nice weekend, Cathy Cathy Handley Executive Director Government Affairs American Registry for Internet Numbers (ARIN) PO Box 232290 Centrevile, VA 20120 Mobile: +1 703 341 7996 Email: chandley@arin.net On Jul 7, 2017, at 6:34 PM, Karen Mulberry > wrote: Here are some thoughts on the Statement of Work for the SSR2-RT Technica= l Writer that you requested for Action Item # 44 - Draft SSR2 Statement of = Work for specialist technical writer. Objective: Develop a Statement of Work to identify a writer who has the = ability to capture and make the SSR2-RT highly technical content uniform an= d understandable for the RT final report The Review Team will need to decide on the particulars of the scope of w= ork, i.e. materials and documents to be developed from content prepared by = the Review Team and a summary of the skills and expertise required by the R= eview Team. Here are some thoughts that might assist the Review Team in determining = the scope of work and skills they are seeking from the Technical Writer the= y want to hire. Reflections for the Review Team on the SSR2 Technical Writer * Does the writer need to grasp the overall concept of ICANN=92s SSR = remit? * Does the writer need to have some familiarity with security, the DN= S and the internet identifiers that ICANN is responsible for? * How does the Review Team want the writer to gather information and = content to use throughout the project? * How does the Review Team want the writer to organize the materials = and content? * What organizational skills are required by the Review Team to make = the process smoother? * How does the Review Team want the writer to handle problems when th= ey arise? * How should the writer obtain further clarification on existing cont= ent or for content that is missing in order to proceed to complete the assi= gnment? The Technical Writer Statement of Work (SOW) should include the followin= g: * A clear, specific project title * A concise description of the work, including a thorough project ove= rview with identification of the challenge to be addressed and documented b= y the writer * List of clear objectives with measurements to determine progress to= wards completion and including, if possible, some descriptive examples of w= hat is expected * A description of required skills, including identifying other revie= w team requirements and needs * A detailed list of particular qualifications, i.e. DNS understandin= g, security expertise * The desired skill level, including specific skills and desired desi= gn style * Concrete timelines and specifications for deliverables, including m= ilestones and measureable outcomes * Helpful links and references to explain desired style * Consider if there a need for some specific questions for candidates= to respond to in their proposal to review writing style * Any additional information needed to be added for the project requi= rements and specifications Example from ATRT2 scope of work for a technical writer for the ATRT2 re= port is as follows: Review text and footnotes of the 68-page (approx.) ATRT2 draft report fo= r general copy editing, including: language fluidity, grammar, spelling, pu= nctuation, typographical errors, formatting, date styles, acronym accuracy = and adherence to ICANN style book. Review the executive summary of the ATRT2 draft report to determine what= can be done to =93make it easier for people who don=92t read the whole rep= ort.=94 Serve as point person for all input and changes to draft ATRT2 report, i= ncluding feedback and edits from: =B7 ATRT2 members =B7 ICANN staff =B7 public comments Evaluate draft report sections and align with report recommendations. Prepare final ATRT2 report for publication, including editing to polish = and refine text. Examples of resources to be used: =B7 ATRT2 Draft Report[icann.org] =B7 ATRT2 Draft Report Public Comment Forum =B7 ATRT 2 Wiki[community.icann.org] =B7 summary report of public comments[icann.org] Working deadline for the ATRT2 report project is December 20, 2013. ICANN Procurement Process to hire Technical Writer (See attached process= diagram) The results of the scope and skills identified by the SSR2 Review Team w= ill inform which procurement path ICANN will need to follow (RFP or no RFP)= . Either way, the procurement process entails 1. Search for a contractor that meets the specified criteria (conducte= d by ICANN procurement & MSSI, based on specs from the RT) a. Communications team can provide names of several people wh= o are familiar with ICANN and have done good work in the past; if RT has in= dividuals that they feel are well qualified, they should send the contact d= etails to ICANN for consideration. 2. Evaluation of each candidate relative to the specified criteria (co= nducted by ICANN procurement & MSSI, based on specs from the RT) 3. Negotiation of terms, contracting =96 ICANN procurement & MSSI I hope that this will assist your discussions on the Statement of Work. Karen Mulberry Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745 --_000_9F5CDC9D54A640F58648294425883419arinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
Karen,

Thanks for this, I think it will come in han= dy as we move forward.  As I discussed with Larissa in Johannesburg I = don't see a rush on this item.  We are just now getting our sub team w= ork started and that should be our focus.  As our work progresses it should help clarify our needs, however I can't imag= ine that we will be at that point until later this year.  Perhaps this= is something we should tee up for Abu Dhabi.

Thanks again for sending this out.

Have a nice weekend,

Cathy


Cathy Handley
Executive Director Government Affairs<= /span>
American Registry for Internet Numbers (ARI= N)
PO Box 232290
Centrevile, VA 20120


On Jul 7, 2017, at 6:34 PM, Karen Mulberry <karen.mulberry@icann.org> wrote:

Here are some thoughts on the Statement of Work for t= he SSR2-RT Technical Writer that you requested for Action Item # 44 - Draft SSR2 Statement of Work for specialist technical= writer.

 

Objective: Develop a Statement of Work to identify a writer who has the ability to capture and make the SSR2= -RT highly technical content uniform and understandable for the RT final re= port

 

The Review Team will need to decide on the particular= s of the scope of work, i.e. materials and documents to be developed from c= ontent prepared by the Review Team and a summary of the skills and expertise required by the Review Team.  =

 

Here are some thoughts that might assist the Review T= eam in determining the scope of work and skills they are seeking from the T= echnical Writer they want to hire.

 

Reflections for the Review Team on the SSR2 Techni= cal Writer

 

  • Does the writ= er need to grasp the overall concept of ICANN=92s SSR remit?
  • Does the writ= er need to have some familiarity with security, the DNS and the internet id= entifiers that ICANN is responsible for?
  • How does the = Review Team want the writer to gather information and content to use throug= hout the project?
  • How does the = Review Team want the writer to organize the materials and content?
  • What organiza= tional skills are required by the Review Team to make the process smoother?=
  • How does the = Review Team want the writer to handle problems when they arise?
  • How should th= e writer obtain further clarification on existing content or for content th= at is missing in order to proceed to complete the assignment?

 

The Technical Writer Statement of Work (SOW) shoul= d include the following:

 

  • A clear, spec= ific project title
  • A concise des= cription of the work, including a thorough project overview with identifica= tion of the challenge to be addressed and documented by the writer
  • List of clear= objectives with measurements to determine progress towards completion and = including, if possible, some descriptive examples of what is expected<= /o:p>
  • A description= of required skills, including identifying other review team requirements a= nd needs
  • A detailed li= st of particular qualifications, i.e. DNS understanding, security expertise
  • The desired s= kill level, including specific skills and desired design style
  • Concrete time= lines and specifications for deliverables, including milestones and measure= able outcomes
  • Helpful links= and references to explain desired style
  • Consider if t= here a need for some specific questions for candidates to respond to in the= ir proposal to review writing style
  • Any additiona= l information needed to be added for the project requirements and specifica= tions

         = ;  

Example from ATRT2 scope of work for a t= echnical writer for the ATRT2 report is as follows:

 

Review text and footnotes of the 68-page (approx.) AT= RT2 draft report for general copy editing, including: language fluidity, gr= ammar, spelling, punctuation, typographical errors, formatting, date styles, acronym accuracy and adherence to ICANN style boo= k.

 

Review the executive summary of the ATRT2 draft repor= t to determine what can be done to =93make it easier for people who don=92t= read the whole report.=94 

 

Serve as point person for all input and changes to dr= aft ATRT2 report, including feedback and edits from:

=B7        AT= RT2 members

=B7        IC= ANN staff

=B7        pu= blic comments

 

Evaluate draft report sections and align with report = recommendations.

 

Prepare final ATRT2 report for publication, including= editing to polish and refine text.

 

Examples of resources to be used:

=B7        ATRT2 Draft Report[icann.org]

=B7        AT= RT2 Draft Report Public Comment Forum

=B7        ATRT 2 Wiki[community.icann.org]

=B7        summary report of public comments[icann.org]

 

Working deadline for the ATRT2 report project is Dece= mber 20, 2013.

 

 

 

ICANN Procurement Process to hire Technical Writer= (See attached process diagram)

 

The results of the scope and skills identified by the= SSR2 Review Team will inform which procurement path ICANN will need to fol= low (RFP or no RFP).

 

Either way, the procurement process entails

  1. Search for a = contractor that meets the specified criteria (conducted by ICANN procuremen= t & MSSI, based on specs from the RT)
    1.  Communi= cations team can provide names of several people who are familiar with ICAN= N and have done good work in the past; if RT has individuals that they= feel are well qualified, they should send the contact details to ICANN for consideration.
  2. Evaluation of= each candidate relative to the specified criteria (conducted by ICANN proc= urement & MSSI, based on specs from the RT)
  3. Negotiation o= f terms, contracting =96 ICANN procurement & MSSI

  

I hope that this will assist your discussions on the = Statement of Work.

&n= bsp;

Karen Mulberry

Directo= r, Multistakeholder Strategy and Strategic Initiatives (MSSI)

ICANN

12025 W= aterfront Dr., Suite 300

Los Ang= eles, CA 90094

Phone: = +1 424 353 9745

 

<SSR2 Tech Writer Procurement.pptx>
--_000_9F5CDC9D54A640F58648294425883419arinnet_-- --_004_9F5CDC9D54A640F58648294425883419arinnet_ Content-Type: text/plain; name="ATT00001.txt" Content-Description: ATT00001.txt Content-Disposition: attachment; filename="ATT00001.txt"; size=481; creation-date="Mon, 10 Jul 2017 14:49:32 GMT"; modification-date="Mon, 10 Jul 2017 14:49:32 GMT" Content-ID: <698411FEA9B5954E83CF8FACD679E5E0@pexch112.icann.org> Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnNzcjItY29v cmRpbmF0aW9uIG1haWxpbmcgbGlzdA0Kc3NyMi1jb29yZGluYXRpb25AaWNhbm4ub3JnDQpodHRw czovL21tLmljYW5uLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NzcjItY29vcmRpbmF0aW9uDQo= --_004_9F5CDC9D54A640F58648294425883419arinnet_--