process for publishing best practices and lessons learned martin yapur, noaa
DESCRIPTION
Process for Publishing Best Practices and Lessons Learned Martin Yapur, NOAA. WGISS – 29 May 17, 2010 Bonn, Germany. Outline. Purpose/Background WGISS Lessons Learned WGISS Projects and Interest Groups WGISS Best Practices Definitions Process: When, What, Where, Who Current Resources - PowerPoint PPT PresentationTRANSCRIPT
Process for Publishing Best Practices and Lessons Learned
Martin Yapur, NOAA
WGISS – 29May 17, 2010
Bonn, Germany
Outline
• Purpose/Background• WGISS Lessons Learned
– WGISS Projects and Interest Groups• WGISS Best Practices
– Definitions– Process: When, What, Where, Who
• Current Resources• WGISS-GEO Support Information
Purpose/Background
• Desired decision(s)– When, What, Where, Who
• Applicable tasking
Action Item from WGISS-Exec:
"Develop a plan to post Best Practices/Lessons Learned/other items on the WGISS website when it has been redesigned. Establish the requirements for internal and external lessons learned, best practices, and WGISS-GEO support information."
WGISS Descriptions on Web SiteRecommendation: Include a section in the new WGISS website for WGISS projects and interest areas:
• Title of IG or Project• Purpose (goals and
scope)• Background (optional)• Approach and
Milestones• Expected Results
(outputs and benefits)• POC• Members
Best Practices
WGISS Internal Lessons LearnedFollowing WGISS-like formats, Interest Groups and Projects are using collaborative websites
WGISS Best Practices
• Provides an open forum for converging on best practice recommendations and reviews
• Reaches out to a broad community• Flexible structure can be easily adapted using lessons
learned• Not all activities will necessarily produce Best Practices.
Best Practices will be a clear contribution of WGISS to the global community
WGISS should establish an “editor” that would review the lessons learned from the WGISS projects and interest groups and determine the appropriate material post as a best practice on the GEOSS wiki
What is a best practice?• Best practices are broad – they can be in
outreach and capacity building, observation techniques or models and analysis
• They can be very simple or complex
• They can be local, regional or global
• They can (and should) be determined by peer acceptance
Ruth Duerr NSIDC, IEEReport to GEO Committees
September, 2008
Process
WGISS EXEC
Technology Subgroup
ApplicationsSubgroup
WISP
Identify Best
Practice
WGISS Discussion
Editor Review
Best Practice
Published
1 2 3 4
1 1
3
4
2
Schedule
Best Practice
WGISS Discussion
Editor Review
BP Published
Apr May Jun Jul Aug Sep Oct Nov Dec
Best Practice WGISS Discussion
Editor Review
BP Published
Identified best practice undergoes an open peer review process within a month from the last meeting
Proposed best practice undergoes an extensive open peer review process and upon concurrence is submitted to GEOSS best practices
Resources• Plans for documenting Best Practices are still being considered
– We need to make a decision
• At conclusion of WGISS IG or Project assess– Title– POC, Date– Keywords– Best Practices List (short statements)
• Finding 1• Finding 2
– Links to relevant files and web sites (details)
Where do you recommend we host the WGISS Best Practices?
Editor Activities• review newly submitted practices for applicability to their subject areas and to
address any erroneous or malicious entries• periodically review and respond to comments on practices in their area that are
in the review process• solicit comments on proposed practices from their communities• solicit proposed practices from their communities if needed• annotate conflicts between practices in the wiki in the hopes of eliciting further
review and comments leading to resolution of the conflict• keep their communities informed about the status of the practices that have
been proposed in their area• correspond with submitters to keep them informed of the status of their
submittal (this may be automated)• examine need for and if needed develop processes to accept or approve
submitted best practices• collaborate with other members of the “editorial” team and participate in
“team” activities including periodic telecoms, etc.
Editor would ensure that WGISS developed best practices were appropriately “tagged” on the GEOSS wiki
WGISS-GEO Support Information• Create a section on the WGISS website to capture information
about WGISS coordination and support to GEO tasks. • The WGISS Vice chair will be responsible for the content of
this area and can coordinate with the WGISS reps who provide support for the different GEO tasks.
• Much of what is already posted in the GEOSS Best Practices wiki already comes form the CEOS interoperability handbook
The guidelines are similar and consistent with the WGISS lessons learned information identified so translation of material from the WGISS website to the GEOSS Best Practices wiki should be straightforward
GEOSS Best Practices Web Site
WGISS StructureWGISS
Pakorn Apaphant, GISTDA, Chair Lorant Czaran, UN, Co-User Vice ChairSatoko Miura, JAXA, Vice Chair Chuang Liu, NRSCC, Co-User Vice Chair
Technology SubgroupNatalia Kussul, , NASU, Chair
Terence Van Zyl, CSIR, Vice Chair
Web Services (IG) Lyn Oleson, USGSGrid (IG) Andrii Shelestov, SRISensor Web (IG) Terence van Zyl, CSIRWADC Project Ken McDonald, NOAA
Yonsook Enloe, SGT/NASA
Applications SubgroupKaren Moe, NASA, Chair
Vacant, Vice Chair
Intl. Directory Network (IDN) (IG) Lola Olsen, NASALand Surface Imaging (IG) Lyn Oleson, USGSAtmospheric Composition (IG) Stefan Falke, NGGlobal Datasets (IG) Lorant Czaran, UNDisaster Management (IG) Lorant Czaran, UN
WGISS Infrastructure Services ProjectMartin Yapur, NOAA
As of Apr 2010
WGISS Project and Interest Group
• Allows project/interest group leads the ability to post information and track progress in their area
• Allows the ability to post or capture pertinent information about lessons learned: project or interest group, POC, date completed, keywords, lessons learned list, summary, detailed description, and links to relevant files or web sites
• Lessons learned should focus on technical issues and information that will help another user implement something
What is a best practice?A best practice is a technique, method, process, activity, incentive, or reward that is believed to be more effective at delivering a particular outcome than any other technique, method, process, etc. when applied to a particular condition or circumstance. Best practices can also be defined as the most efficient (least amount of effort) and effective (best results) way of accomplishing a task, based on repeatable procedures that have proven themselves over time for large numbers of people.
Welcome to Better Outcomes Best Practices is about doing things the right way: the most efficient, effective ways to achieve goals, distilled into adaptable, repeatable procedures you can use.
A best practice is a technique or methodology that, through experience and research, has proven to reliably lead to a desired result. A commitment to using the best practices in any field is a commitment to using all the knowledge and technology at one's disposal to ensure success
BP Concept of Operations• Individual or organization proposes a practice for
consideration as a “best” practice by submitting an entry in the wiki.
• Submitted practices undergo an open peer review process in the wiki.– Comments in the wiki are publicly accessible, facilitating a
moderated community dialog.• Editors work with their communities to encourage dialog
and submission of comments• Editors also assure that malicious insertions are eliminated.
– Original contributors should also monitor activities