1. Kaizen
A continual improvement process, also often
called a continuous improvement process
(abbreviated as CIP or CI), is an ongoing effort to
improve products, services, or processes.
Kai (“cambio”) zen(“bueno”)

2. Kaizen
• Deming: es una estrategia de mejora continua de la calidad en cuatro pasos.
Plan, Do, Check, Act (Planificar, Hacer, Verificar, Actuar).
Los resultados de la implementación de este ciclo permiten a las empresas una
mejora integral de la competitividad, de los productos y servicios, mejorando
continuamente la calidad, reduciendo los costes, optimizando la
productividad, reduciendo los precios, incrementando la participación del
mercado y aumentando la rentabilidad de la empresa u organización.
• Kaisen: “mejora continua que involucra a todos”. Es pues un sistema integral y
sistémico destinado a mejorar tanto a las empresas, como a los procesos y
actividades que las conforman, y a los individuos que son los que las hacen
realidad. El objetivo primero y fundamental es mejorar para dar al cliente o
consumidor el mayor valor agregado.
• Katas: Código Kata es un intento de llevar este elemento de la práctica para el
desarrollo de software que ayuda a un programador a perfeccionar sus habilidades
a través de la práctica y la repetición.
Un kata es un ejercicio de karate en la que repites una forma muchas, muchas
veces, haciendo pequeñas mejoras en cada uno. La intención detrás de código kata
es similar y el objetivo es la práctica, no la solución.

3. Deming. PDCA (plan–do–check–act )
3) CHECK Study the actual results (“DO”) and compare against the expected results
("PLAN"). Look for deviation in implementation from the plan and also look for the
appropriateness and completeness of the plan to enable the execution.
4) ACT Request corrective action on significant differences between actual and
planned results. Analyze the differences to determine their root causes. Determine
where to apply changes that will include improvement of the process or product.
1) PLAN Establish the
objectives and processes
necessary to deliver results
in accordance with the
expected output
2) DO Implement the plan,
make the product. Collect
data for charting and
analysis in the following
steps.

4. Lean.- 5S
Seiri (Sort – Separar, ordenar).
Seiton (Set in order –
Almacenar, simplicar).
Seiso (Shine – Fregar, barrer).
Seiketsu (Standardize – Estandarizar).
Shitshuke (Sustain – Sistematizar, auto-
disciplina).

5. Kaizen aplicado al sw

6. Kaizen aplicado al sw: deming

7. Kaizen aplicado al SW: entrega
continua

8. Kaizen aplicado al SW: continuous
testing

9. Kaizen aplicado al SW: lean
programming
• Lean programming is a concept that emphasizes optimizing
efficiency and minimizing waste in the development of a computer
program. The concept is that efficiencies can be applied and waste
managed at all levels: each individual, every
department, interdepartmental operations, the organization as a
whole, and the relationships of the organization with customers
and suppliers.
• Lean programming is based on rules that were developed by several
corporations in the 1980s. The rules have an upbeat and positive
tenor. For example, waste and intermediate artifacts should be kept
to a minimum. Documentation should be concise, and should cover
generalities without getting lost in details. Individual workers, as
well as customers, should be consulted frequently, and their views
and opinions taken seriously. A primary goal is continuous
improvement at all levels and in all phases of the operation.

10. Kaizen aplicado al SW: kanban in sw
development. Kanban boards

11. Kaizen aplicado al SW: refactoring
• Code refactoring is the process of restructuring existing computer
code.
• Refactoring improves nonfunctional attributes of the software.
Advantages include improved code readability and reduced
complexity to improve source code maintainability, and create a
more expressive internal architecture or object model to improve
extensibility.

12. Resources
• http://continuations.com/post/60704032/kaiz
en-for-developers-the-centrality-of-quality
• http://www.codeforlife.org/2009/07/5s-
kaizen-in-software-engineering-part.html
• Refactoring. Improving the Design of Existing
Code by Martin Fowler
• Most images from Wikimedia Commons, the
free media repository