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:

Desafío de Estimaciones en SCRUM

Yes or No

(5)
Played 182

About this activity

Quiz rápido sobre estimaciones SCRUM.

Created by

Colombia

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
Desafío de Estimaciones en SCRUM
 

Desafío de Estimaciones en SCRUMOnline version

Quiz rápido sobre estimaciones SCRUM.

by Marvin Sanchez
1

El Product Owner es el único responsable de estimar cada historia.

2

La estimación se realiza por todo el equipo de desarrollo, usando Planning Poker.

3

La estimación es relativa: se compara una historia con otras para asignar puntos.

4

Los puntos de historia miden el tiempo de ejecución real de cada tarea.

5

Durante Planning Poker, se promedia automáticamente los puntos propuestos por cada miembro.

6

La velocidad (velocity) se obtiene sumando los puntos de las historias completadas en un sprint.

7

Una vez estimada una historia, su estimación nunca debe actualizarse.

8

En SCRUM, las estimaciones se expresan típicamente en puntos de historia y no en horas.

9

Las estimaciones deben hacerse en horas exactas y nunca deben cambiar.

10

Las estimaciones ayudan a prever cuántas historias puede completar el equipo en un sprint.

Are you sure you want to leave the page?

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