Post on 27-Jun-2015
SCRUM
Sergio Acosta - Junio 2009
HABLANDO EN
1
SCRUM
Sergio Acosta - Junio 2009
POR QUÉ
NO FUNCIONA
1
QUÉ ES SCRUM?(TODOS EN EL “MISMO CANAL”)
2
1986
TAKEUCHI
NONAKA
3
4
4
NUEVO PARADIGMA
5
NUEVO PARADIGMA
5
NUEVO PARADIGMA
5
CARACTERISTICAS
Built-in instability
Self-organizing teams
Overlapping phases
“multilearning”
Subtle control
Organizational transfer of learning
6
1993
7
AT&T: SORPRENDIDOS
1 Millón LOC
31 Meses
8 Personas
Retando A Excel Y Lotus 1-2-3
8
PRODUCTIVITY INDEX
9
AT&T: FINDINGS
Mejor comunicación que el 98% de los procesos
Excelencia e integridad de las personas
Multi-disciplinarios, pero especializados
Prototipado intensivo
Juntas de diseño constantes
Introspección constante acerca del proceso
QA es una actividad central del desarrollo
10
LEAN MANUFACTURING
The Toyota Production System
11
IRON TRIANGLE
COST TIME
FEATURES
ÁREA = IMPORTANCIA
12
IRON TRIANGLE
COSTTIME
FEATURES
“más funcionalidad”
“más barato”
“más tiempo”
13
IRON TRIANGLE
COSTTIME
FEATURES
“más funcionalidad”
“más caro”
“menos tiempo”
14
REAL IRON TRIANGLE
COST TIME
FEATURES
QUALITY
15
REAL IRON TRIANGLE
COST TIME
FEATURES
QUALITY
“es que todo es prioridad uno”
16
REAL IRON TRIANGLE
この牛の最高なんだよ!! *
17
REAL IRON TRIANGLE
この牛の最高なんだよ!! *
* BULLSHIT!!
17
18
“THE TOYOTA WAY”
1. We place the highest value on actual implementation and taking action.
2. There are many things one doesn’t understand therefore, we ask them why you don’t just go ahead and take action?
3. You realize how little you know and you face your own failures and redo it again and at the second trial you realize another mistake ... so you can redo it once again.
4. So by constant improvement ... one can rise to the higher level of practice and knowledge.
19
LA VARIABLE FALTANTE
COST TIME
FEATURES
QUALITY
20
LA VARIABLE FALTANTE
COST TIME
FEATURES
QUALITY
WASTE
WASTE
20
COST TIME
FEATURES
QUALITY
21
PRINCIPIOS
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
2. Build Quality In vs The job of QA is to find defects
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
2. Build Quality In vs The job of QA is to find defects
3. Create Knowledge vs Predictions create predictability
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
2. Build Quality In vs The job of QA is to find defects
3. Create Knowledge vs Predictions create predictability
4. Defer Commitment vs Planning is commitment
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
2. Build Quality In vs The job of QA is to find defects
3. Create Knowledge vs Predictions create predictability
4. Defer Commitment vs Planning is commitment
5. Deliver Fast vs Haste makes waste
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
2. Build Quality In vs The job of QA is to find defects
3. Create Knowledge vs Predictions create predictability
4. Defer Commitment vs Planning is commitment
5. Deliver Fast vs Haste makes waste
6. Respect People vs here is One Best Way
22
PRINCIPIOS
1. Eliminate Waste vs Early specification reduces waste
2. Build Quality In vs The job of QA is to find defects
3. Create Knowledge vs Predictions create predictability
4. Defer Commitment vs Planning is commitment
5. Deliver Fast vs Haste makes waste
6. Respect People vs here is One Best Way
7. Optimize the Whole vs Optimize by decomposition
22
WASTE REDUCTION MENTALLITY
Mura: Just-In-Time: supplying the production process with the right part, at the right time, in the right amount, and first-in, first out component flow
Muri: unreasonable work that management imposes on workers and machines because of poor organization
Muda: rework, overproduction, transportation, inventory, motion, danger, breakdown, ...
23
改善
24
改善
KAI
ZEN
24
改善
KAI
ZEN
CAMBIAR PARA CORREGIR
CAMINO
24
1995
SCRUM SOFTWAREDEVELOPMENTPROCESS
OOPSLA´95
Jeff Sutherland Ken Schwaber
25
Reglas del juego
26
Personas
• Scrum Team (pigs)
• Product Owner
• Scrum Master
• Development Team
• Team Community (chickens)
• Todos los demás
27
Time Boxes (proceso)• Sprint (4 semanas)
ReleaseRelease
Sprint Sprint Sprint Sprint Sprint
28
Time Boxes (proceso)• Sprint (4 semanas)
4 semanas
Daily Scrum
Sprint Planning
1 día
Product Review
4 horas
Retrospective
4 horas
1 día 1 día 1 día
Sprint
28
Time Boxes (proceso)• Sprint (4 semanas)
4 semanas
Daily Scrum
Sprint Planning
1 día
Product Review
4 horas
Retrospective
4 horas
1 día 1 día 1 día
Sprint
• Sprint Planning (4 + 4 horas)
28
Time Boxes (proceso)• Sprint (4 semanas)
4 semanas
Daily Scrum
Sprint Planning
1 día
Product Review
4 horas
Retrospective
4 horas
1 día 1 día 1 día
Sprint
• Sprint Planning (4 + 4 horas)
• Daily Scrum (15 minutos)
28
Time Boxes (proceso)• Sprint (4 semanas)
4 semanas
Daily Scrum
Sprint Planning
1 día
Product Review
4 horas
Retrospective
4 horas
1 día 1 día 1 día
Sprint
• Sprint Planning (4 + 4 horas)
• Daily Scrum (15 minutos)
• Product Review (4 horas)
28
Time Boxes (proceso)• Sprint (4 semanas)
4 semanas
Daily Scrum
Sprint Planning
1 día
Product Review
4 horas
Retrospective
4 horas
1 día 1 día 1 día
Sprint
• Sprint Planning (4 + 4 horas)
• Daily Scrum (15 minutos)
• Product Review (4 horas)
• Sprint Retrospective(4 horas)
28
Entregables
29
Entregables
• Potentially Shippable Product Increment (cada sprint)
29
Entregables
• Potentially Shippable Product Increment (cada sprint)
• Completo (ej. manuales, capacitación)
29
Herramientas
30
Herramientas
• Product Backlog
30
Herramientas
• Product Backlog
• Sprint Backlog
30
Herramientas
• Product Backlog
• Sprint Backlog
• Definition of “Done”
30
Herramientas
• Product Backlog
• Sprint Backlog
• Definition of “Done”
30
Herramientas
• Product Backlog
• Sprint Backlog
• Definition of “Done”
• Release Plan
30
Herramientas
• Product Backlog
• Sprint Backlog
• Definition of “Done”
• Release Plan
• Impediment Backlog
30
Métricas
• Burndown
• Velocity
31
SCRUM SI FUNCIONA
32
33
SOURCE: JEFF SUTHERLAND, “THE ROOTS OF SCRUM”
34
35
36
37
¿POR QUÉ
SCRUM NO FUNCIONA?
(CUANDO NO FUNCIONA)
38
EL ENEMIGO
De los primeros “Management consultants”
“Scientific Management” (1911)
Progressive Era: Edison, Ford, ...Hitler☺
Frederick Taylor(1856 - 1915)
39
PRINCIPIO 1
“Replace rule-of-thumb work methods with methods based on a scientific study of the tasks.”
40
PRINCIPIO 2
“Scientifically select, train, and develop each employee rather than passively leaving them to train themselves.”
41
PRINCIPIO 3
“Provide detailed instruction and supervision of each worker in the performance of that worker's discrete task”
42
PRINCIPIO 4
“Divide work nearly equally between managers and workers, so that the managers apply scientific management principles to planning the work and the workers actually perform the tasks.”
43
TAYLORISM
“The science of handling pig-iron is so great that the man who is physically able to handle pig-iron and is sufficiently phlegmatic and stupid to choose this for his occupation is rarely able to comprehend the science of handling pig-iron.”
44
TAYLORISM
“It is only through enforced standardization of methods, enforced adoption of the best implements and working conditions, and enforced cooperation that this faster work can be assured. And the duty of enforcing the adoption of standards and enforcing this cooperation rests with management alone.”
45
YA NO ESTAMOS EN LA ERA INDUSTRIAL
46
DISEÑO PRODUCCIÓN
“EL QUE SABE” “LOS QUE EJECUTAN INSTRUCCIONES”
47
DISEÑO PRODUCCIÓN
“EL QUE SABE” “LOS QUE EJECUTAN INSTRUCCIONES”
48
49
SCRUM
49
DISEÑO PRODUCCIÓN
“LOS QUE SABEN” “LOS QUE EJECUTAN INSTRUCCIONES”
50
Complex Complicated
Chaos Simple
C-E: ENTENDIBLE
C-E: ENTENDIDA
C-E: COHERENTE EN RETROSPECTIVA
C-E: NO DISCERNIBLE
RELACIÓN CAUSA-EFECTO
51
Complex Complicated
Chaos Simple
C-E: ENTENDIBLE
C-E: ENTENDIDA
C-E: COHERENTE EN RETROSPECTIVA
C-E: NO DISCERNIBLE
RELACIÓN CAUSA-EFECTO
AQUI ESTA UD.
51
Complex Complicated
Chaos Simple
C-E: ENTENDIBLE
C-E: ENTENDIDA
C-E: COHERENTE EN RETROSPECTIVA
C-E: NO DISCERNIBLE
RELACIÓN CAUSA-EFECTO
AQUI ESTA UD.
AQUI ESTA TU PROJECT MANAGER
51
CULTURAS
The Reengineering alternative (1999)
Las organizaciones son organismos vivos
Cada organización tiene una cultura particular
William Schneider, Ph.D.
52
CULTURAS
53
CULTURAS
SCRUM
53
CULTURAS
SCRUM
AQUI ESTA UD.
53
SCRUM AND MANAGERS
54
HIERARCHICAL LEADERSHIP
ORGANIZACIÓN
55
HIERARCHICAL LEADERSHIP
ORGANIZACIÓN
CEO
55
HIERARCHICAL LEADERSHIP
ORGANIZACIÓN
CEO
LOS QUE PRODUCEN
55
HIERARCHICAL LEADERSHIP
ORGANIZACIÓN
CEO
EL QUE MANDA A LOS QUE MANDAN
LOS QUE PRODUCEN
55
SERVANT LEADERSHIP
56
SERVANT LEADERSHIP
56
SERVANT LEADERSHIP
CEO
56
SERVANT LEADERSHIP
CEO
LOS QUE PRODUCEN
56
SERVANT LEADERSHIP
CEO
EL QUE SIRVE A LOS QUE SIRVEN
LOS QUE PRODUCEN
56
CÓMO HACER QUE
SCRUM FUNCIONE
(GUÍAS DE ADOPCIÓN)
57
TO BE OR NOT TO BE (AGILE)
¿NECESITO? ¿QUIERO?
OLVIDALO ADELANTE!
SI
SI
SI
NONO
58
¿ NECESITO ?
Waterfall no siempre es inadecuado
59
SPACE SHUTTLE
“If the software isn't perfect, some of the people we go to meetings with might die”
Cada línea de código diseñada, verificada, antes de ser escrita
Especificación funcional: 40,000 páginas
1 bug x cada 420,000 LOC
17 bugs en las últimas 11 versiones
“People ask, doesn't this process stifle creativity? The answer is, yes, that is precisely the point.”
60
¿ QUIERO ? (DIFICULTADES)
Práctica Contracultura
Poder implica responsabilidad
Disciplina total
Colaboración, Transparencia, Confianza, Iniciativa, Retrospectiva, Aceptar errores, Coraje, Trabajo duro.
Luchar por cambiar el status-quo
Fricción con otras personas y áreas
Volver a aprender muchas cosas
¿ Te interesa entregar valor ?
61
PREDICCIÓN
Sólo el 30% de las organizaciones van a ser exitosas en adoptar Scrum/Agil
El resto se va a ver obligado a permanecer competitivas con Outsorcing/Offshoring
Ken SchwaberCon el riesgo que esto implica en la calidad
62
PASOS PARA ADOPTAR SCRUM
63
PASOS PARA ADOPTAR SCRUM
MUAHAHAHA!!
63
4 semanas
Daily Scrum
Sprint Planning
1 día
Product Review
4 horas
Retrospective
4 horas
1 día 1 día 1 día
Sprint
ReleaseRelease
Sprint Sprint Sprint Sprint Sprint
64
RECOMENDACIONES
65
http://www.infoq.com/presentations/Fail-Scrum-Henrik-Kniberg
66
http://www.infoq.com/presentations/10-tips-for-agile-transitions
67
http://www.infoq.com/presentations/Agile-Transitioning-Mike-Cohn
68
CONCLUSIONES
69
SCRUM NO HACE NADA
70
SCRUM NO HACE NADA
SOLO HACE EVIDENTES LAS DISFUNCIONALIDADES
70
GRACIAS
71
COMUNIDAD
http://comunidadscrum.wordpress.com/
http://groups.google.com/group/comunidad-scrum-mexico
twitter: @comunidadscrum
sergio.acosta@gmail.com
twitter: @scasware
72