New game
Download
Get Academic Plan
Share game
Integrate it into your platform

You can integrate the game into an LMS compatible with LTI 1.1 or LTI 1.3 such as Canvas, Moodle, or Blackboard. This way, the scores will be automatically saved into the platform’s gradebook.
Download
You have exceeded the maximum number of games you can integrate into Google Classroom with your current Plan.

To integrate as many games as you want in Google Classroom, you need an Academic Plan or a Commercial Plan.

You have exceeded the maximum number of games you can integrate into Microsoft Teams with your current Plan.

To integrate as many games as you want in Microsoft Teams, you need an Academic Plan or a Commercial Plan.

Downloading games is an exclusive feature for users with an Academic Plan or a Commercial Plan.

Get your Academic Plan or your Commercial Plan now and start integrating your games into your LMS, website or blog.

If you wish, you can download a demo game here and test its integration:

Operaciones ante un fallo tecnológico

Yes or No

Played 0

About this activity

Evaluación rápida de manejo de incidencias

Created by

Mexico

Download the paper version to play

Make your own free game from our game creator
Compete against your friends to see who gets the best score in this game

Top Games

%
Anonymous
Anonymous
%
%
%
You have exceeded the maximum number of games you can print with your current Plan.

To print as many games as you want, you need an Academic Plan or a Commercial Plan.

Print your game
Operaciones ante un fallo tecnológico
 

Operaciones ante un fallo tecnológicoOnline version

Evaluación rápida de manejo de incidencias

by Ingrid Romina
1

Reproducir el fallo para entender cuándo ocurre.

2

Cambiar la pieza defectuosa sin confirmar la causa.

3

No recoger detalles del problema y pedir solo soluciones genéricas.

4

Revisar logs y registros para identificar errores.

5

Priorizar la seguridad de datos realizando respaldos antes de cambios.

6

Desactivar sistemas de respaldo para acelerar la reparación.

7

Esperar a que el usuario dé la solución para continuar.

8

Aislar la causa probando componentes de forma incremental.

9

Ejecutar cambios sin planificar ni evaluar riesgos.

10

Documentar el plan de reparación y los pasos ejecutados.

Are you sure you want to leave the page?

If you leave the page, you will lose your game progress.