Page History
The Project Management Institute (PMI)
ICANN worked closely with the ATRT2 throughout 2013, laying down a foundation to ensure the implementation of the recommendations would be timely and effective. An implementation methodology was designed based on the global standards of The Project Management Institute - rules, guidelines, and characteristics for the project and development of a management portfolio. The PMI standards are widely accepted with a goal towards achieving professional excellence. Benefits include a clear scope definition, company-wide resource planning, monitoring against timelines and consistent reporting.
ICANN’s commitment to accountability and transparency, in the interest of Internet users globally, was formalized and documented in 2009 in the Affirmation of Commitments (AoC) agreement with the U.S. Government. It set a course for ongoing evolution and improvement in ICANN’s accountability. ICANN views the implementation methodology it chose as the means of ensuring an organization-wide commitment to continuous improvement.
The method of implementing the ATRT2’s recommendations will serve as a pilot. ICANN will refine the approach to apply consistently to AoC and other review efforts.
Roles & Responsibilities
Reporting
With the experience of two previous Accountability and Transparency reviews, ICANN understands the importance of timely and effective communications. In fact, one of the ATRT2 recommendations specifically addresses implementation reporting. Updates on the progress of implementing the recommendations will be posted and reported each trimester through multiple communication channels and at ICANN meetings, beginning with ICANN51 in Los Angeles. A public session ATRT2 Implementation Update will take place on Wednesday, 15 October 2014 at 10:30 – 11:45. Additionally, webinars on the recommendations will be offered periodically to provide ICANN stakeholders an opportunity to interact with the implementation teams.
At this time, projects implementing all 12 ATRT2 recommendations
have been initiated with several teams executing their initial implementation steps. With 51 distinct recommendation components to develop, the timeframe for implementation will vary depending on the complexity of the recommendation and its key dependencies. These elements will be addressed in the Implementation Summaries provided for each recommendation.