Exposición de Gestión de Calidad

2. No veo este arreglo como un problema. esta es la
forma en que siempre es benéfica y parece ser la
forma más lógica de hacerlo. fue establecido por
el director de operaciones de TI y no quiero
mover el barco.
el proceso de lanzamiento es el problema de otra
persona y haré el mínimo indispensable en
preparación para eso - estoy demasiado ocupado
escribiendo software
Temo cada lanzamiento. Cada lanzamiento es el
mismo, nunca va sin problemas, y paso muchas
horas trabajando en ello y días después
arreglando el desastre.

3. Elephant in the room
Exhibición Barely legal 2006 los Ángeles
Elefante en la habitación
Autor: Banksy

4. Including (almost) everyone
Identifying the key
people
One tip when compiling the list of
participants is to try and identify
the key people within the process.
These key people might not
be obvious at first, however, asking
simple questions such as who should I
ensure I invite to this? or who do you
normally talk to if there's a problem? of
a number of different people from
different parts of the business will give
you some indications.
Too many cooks
As you build your list of participants,
you might encounter a positive
problem—you have too many people
who want to be involved in the
investigation. In some respects, this is
a good thing; oversubscription is a nice
problem to have. If this is the case,
you should consider running multiple
sessions rather than drop people off
the list.

5. Openness, transparency, and honesty
To truly get to the bottom of a given
problem, you need to gather as much
information and data about it as
possible so that you can collectively
analyze and agree the best way to
overcome or address it—you need to
know how big the elephant truly is
before you expose it and then
remove it. The natural reaction of
most management "Stans" will be to
run a closed session investigation
and invite a selected few to take part.

6. Value stream
mapping