Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch 3 #48

Open
wants to merge 2 commits into
base: jekyll
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions pages/protocols/metaprotocols.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,3 +8,9 @@ sidebar: mydoc_sidebar
permalink: metaprotocols.html
folder: protocols
---

This page explains what a metaprotocol is and where they are used.

Metaprotocols are instructions consisting of recommendations and best practices that provide advice on how to choose what steps/tasks/modules/services to include in a project when the generic project template is being adapted for a particular project instance. The instructions may include a) how to adapt Protocols to specific cases, b) how to decide which alternative or optional tasks to include, and c) how to determine the number of iterations needed in a particular case. Metaprotocols are written for project managers to help them select the right actionable content to include in a specific project.

References to metaprotocols are found in TasCu, the generic project template/library. Contrary to Protocols, which are associated with the most detailed level of steps in TasCu, Metaprotocols are associated with steps at higher levels of granularity. There may be zero, one, or more metaprotocols associated with any specific TasCu step.