OSE Protocol: OSE Protocol Template

From Open Source Ecology
Jump to: navigation, search

OSE Protocol: OSE Protocol Template


OSE Protocol: OSE Protocol Template

Owned by: Operations Manager

POC for collaboration: Ops@opensourceecology.org

V.6-17-13


Purpose: Use this section to support the protocol’s purpose. Protocols, approved by the Executive Director, ensure that 1) complex operations function harmoniously, 2) processes are accessible for open source collaboration for the purpose of optimizing efficiency, and 3) turnover of processes are simple and comprehensive.

Scope: Use this section to define the protocol’s scope. Protocols can cover an entire operation or a single task. Complex operations must be broken up into multiple protocols.

Responsibilities: Use this section to define responsibilities.

  • Protocol Creator – The Protocol Creator is responsible for creating protocols for which s/he is responsible.
  • Stakeholders – Stakeholders are all persons, positions, or roles who are directly impacted should a pending protocol be approved. Stakeholders are responsible for providing feedback to the Protocol Creator in a reasonable amount of time. If Stakeholders non-concur, adequate justification is required.
  • Operations Manager – The Operations Manager is responsible for reviewing pending protocols and notifying the Executive Director to review. The Operations Manager is responsible for resolving non-concur feedback and modifying the pending protocol to support. Operations Manager is responsible for keeping an index of all protocols at Protocols page on the wiki.
  • Executive Director – The Executive Director is responsible for approving all pending protocols, taking into consideration all written responses that address non-concur feedback.

Materials and tools required to execute protocol: Use this section to list required tools and materials.

  • OSE Google Docs
  • Wiki

Step by step guide: Use this section to list steps.

  1. Protocol Creator identifies a new process
  2. Use this template by first reviewing instructions, second deleting instructions, and third inputting content, Protocol Creator documents the new process in OSE Google Docs PENDING OSE Protocols folder.
  3. Protocol Creator notifies Operations Manager (only) of pending protocol.
  4. Operations Manager emails collaborators, notifying them of the pending protocol and feedback response timeline. In this context, collaborators are Stakeholders.
  5. Stakeholders provide feedback, either by concurring or non-concurring to specific issues. Protocol Creator and Stakeholders must try to resolve all issues.
  6. Once Protocol Creator and Stakeholder issues are resolved, Operations Manager reviews protocol and submits to Executive Director.
  7. Operations Manager notifies Executive Director of pending protocol ready for approval.
  8. Executive Director notifies Operations Manager of approval or disapproval regarding the pending protocol. If disapproved, then Operations Manager notifies Protocol Creator. If approved, then Operations Manager remove PENDING from the pending protocol’s title and links to Wiki Protocols.

Exceptions: Use this section for exceptions or emergencies.

  1. In the event that Protocol Creator and Stakeholders do not agree on a pending protocol, all parties may provide a written response to the Operations Manager addressing non-concur feedback. The written response will be submitted alongside the pending protocol to the Executive Director for consideration.