Category: Agile


Estimation In software development, an «estimate» is the evaluation of the effort necessary to carry out a given development task; this is most often expressed in terms of duration. Estimación En el desarrollo de software, una «estimación» es la evaluación del esfuerzo necesario para llevar a cabo una tarea de desarrollo determinada; esto se expresa…
Leer más

Given When Then

Given When Then The Given-When-Then formula is a template intended to guide the writing of acceptance tests for a User Story: (Given) some context, (When) some action is carried out, (Then) a particular set of observable consequences should obtain.  Dado cuando entonces La fórmula Given-When-Then es una plantilla destinada a guiar la escritura de las…
Leer más

Heartbeat Retrospective

Heartbeat Retrospective The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities  for improvement. Retrospectiva del Latido del Corazón El equipo se reúne regularmente para reflexionar sobre los eventos más significativos que ocurrieron desde la reunión anterior e identificar oportunidades de mejora.

Incremental Development

Incremental Development In an Agile context, Incremental Development is when each successive version of a product is usable, and each builds upon the previous version by adding user-visible functionality. Desarrollo Incremental En un contexto ágil, el desarrollo incremental es cuando cada versión sucesiva de un producto es utilizable, y cada una se basa en la…
Leer más

Iterative Development

Iterative Development Agile projects are iterative insofar as they intentionally allow for «repeating» software development activities, and for potentially «revisiting» the same work products. El Desarrollo Iterativo, Iterative Development, es un proceso en el cual la solución en evolución, o una parte de ella, evoluciona de un concepto de alto nivel a algo con un…
Leer más

Kanban Board

Kanban Board A Kanban Board is a visual workflow tool consisting of multiple columns. Each column represents a different stage in the workflow process. Tablero Kanban Un tablero Kanban es una herramienta de flujo de trabajo visual que consta de varias columnas. Cada columna representa una etapa diferente en el proceso de flujo de trabajo.

Kano Model

Named after Noriaki Kano, a Japanese professor Kano Model is used to map what is valued by the customer by classifying the product attributes into basic, performance, and excitement categories. It can be used to determine the minimally viable product that a customer will feel satisfies his or her basic requirements.

Lead Time

Lead Time Lead Time is the time between a customer order and delivery. In software development, it can also be the time between a requirement made and its fulfillment. Tiempo de Espera El tiempo de entrega es el tiempo entre el pedido y la entrega del cliente. En el desarrollo de software, también puede ser…
Leer más

Mob Programming

Mob Programming Mob Programming is a software development approach where the whole team  works on the same thing, at the same time, in the same space, and at the same computer. Programación de la Mafia Mob Programming es un enfoque de desarrollo de software donde todo el equipo trabaja en la misma cosa, al mismo…
Leer más


This Japanese word is used for overburden, unreasonableness or absurdity. Kanban avoids Muri through standardized work. First, a standard output is defined so that there can be an effective judgment of quality. Then, the elements in each process are simplified for examination and recombination. The process is then standardized to get a standard condition.

Niko-niko Calendar

Niko-niko Calendar A Niko-niko Calendar is updated daily with each team member’s mood for that day. Over time the calendar reveals patterns of change in the moods of the team, or of individual members. Calendario Niko-niko Un calendario Niko-niko se actualiza diariamente con el estado de ánimo de cada miembro del equipo para ese día.…
Leer más

Pair Programming

Pair programming is a programming technique in which two programmers working together on a single system. This practice has been around since the 1950s. Many studies have shown that pair programmers are more than twice as efficient; in code production and especially in freedom from bugs, than one single programmer on a single system.

Planning Poker

An Agile estimation practice which is a variation of the wideband Delphi method of consensus based estimation. It is used to estimate effort or relative size of user stories by assigning story points to each user story. This technique can also be used for meetings where the team estimates risk in different modules.

Prevention vs. Inspections

Prevention is an activity that can reduce the probability of negative consequences associated with project risks whereas inspection measures to verify whether an activity, component, product, or service conforms to specified requirements. The cost of preventing mistakes is much less than the cost of correcting the mistakes found during inspection.