Ir al contenido

Open Knowledge Protocol

De Scrum Manager BoK
Esta página es una versión traducida de la página Protocolo Open Knowledge. La traducción está completa al 100 %.
⏱ 4 min  ·  📅 2026
The Open Knowledge (OK) protocol is an assessment protocol developed by Scrum Manager for implementing the AgiLevel model step by step. It is free to use, generic in nature, and designed to be adaptable to most organizations.

The AgiLevel theoretical framework can be applied either flexibly or by following a specific protocol—a set of procedural instructions and resources that guide the assessment within a particular context, depending on the organization's size and the type of assessment. The "OK" protocol consists of a series of anonymous surveys that the evaluator weights at their own discretion; a spreadsheet and a web application (at agilevel.com) are used to record the results, prioritize items, and calculate risks. Those who wish to do so can create their own custom protocol and even have it certified for use by others.

Workflow

  1. Workshops for teams or departments to explain the purpose of the assessment, its code of ethics, and the guarantee of anonymity; surveys are conducted during these sessions, without yet referencing specific practices.
  2. Team observation and shadowing over several weeks (using a shadowing approach is effective) to verify whether the actual situation aligns with the survey responses. The raw results are then weighted—applying a subtle, moderate, or significant adjustment—based on these observations.
  3. Prioritization: Using the weighted results, focus on a maximum of two or three aspects per dimension and support area. Develop an action plan based on these findings and present it to management, without overwhelming them with the granular details from the surveys.

Evaluation Categories

  • Category 1 or team evaluation: a single team, with one or more projects.
  • Category 2 or department evaluation: several teams and projects within the same organizational unit.
  • Category 3 or company/corporation evaluation: more than one organizational unit, each with one or more teams or projects.

Types and Status of the Evaluation

  • A technical evaluation is conducted without a designated evaluator role; it follows a structured procedure and is verified using forms or software applications. Any potential lack of consistency is accounted for within the evaluation framework itself.
  • An expert evaluation is led by an individual acting in the role of an evaluator. In this case, the evaluator’s professional judgment—supported by reasoning and argumentation—takes precedence over the results generated by the standard framework.
  • An evaluation is considered official if it is issued by AgiLevel and overseen by a certified evaluator; otherwise, it is classified as independent. Official evaluators must possess at least three years of experience in management or advisory roles and have completed at least three improvement initiatives or independent evaluations through AgiLevel.
  • The level of independence (rated from 1 to 3) indicates the extent to which the evaluators have previously participated in advisory or training activities within the organization being evaluated.

Common mistake

Treating survey responses as the final evaluation result. Responses are subjective and may be distorted by the pressure of the company culture. They are raw data that help focus one’s observations; the evaluator calibrates them against what they see firsthand before drawing any conclusions.

Resources

🌐 AgiLevel — Official WebsiteDocumentation and resources for the model

📄AgiLevel syllabusFree download · Scrum Manager

🔧 AgiLevel Radar — Assessment ToolScrum Manager · Free online assessment

🔧 AgiLevel CanvasScrum Manager · Tool

🏦 AgiLevelSkill Arena · Scrum Manager

See also