Top Banner
#AgileBr Resumo por Bruno Nardini
176

Agile Brazil 2013 - Resumo

Aug 20, 2015

Download

Technology

Bruno Nardini
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Agile Brazil 2013 - Resumo

#AgileBrResumo por Bruno Nardini

Page 2: Agile Brazil 2013 - Resumo

#AgileBr

1. Scrum with Kanban2. 7 Ways to Track Lead-time3. Como cultivar uma cultura Kaizen4. Métricas de Código5. Mockar ou não Mockar6. Testes legíveis, projetos felizes7. Agile: Unlocking our Human Potential8. O time de desenv. deve virar o time de marketing!9. Coragem para Empoderar

10. Valorizando a Segurança

Page 3: Agile Brazil 2013 - Resumo

#AgileBr

Baseado em fatos reais

Page 4: Agile Brazil 2013 - Resumo

Scrum with KanbanPaulo CaroliJohann Arispe

Page 5: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 6: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 7: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 8: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 9: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 10: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 11: Agile Brazil 2013 - Resumo

Scrum with Kanban

Visible Workflow

Page 12: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 13: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 14: Agile Brazil 2013 - Resumo

Scrum with Kanban

Common Kanban terms...

Page 15: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 16: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 17: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 18: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 19: Agile Brazil 2013 - Resumo

Scrum with Kanban

Kanban mechanics

Page 20: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 21: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 22: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 23: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 24: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 25: Agile Brazil 2013 - Resumo

Scrum with Kanban

Stop startingand start finishing!

Page 26: Agile Brazil 2013 - Resumo

Scrum with Kanban

A Sprint example...

Page 27: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 28: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 29: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 30: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 31: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 32: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 33: Agile Brazil 2013 - Resumo

Scrum with Kanban

Another team...

Page 34: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 35: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 36: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 37: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 38: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 39: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 40: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 41: Agile Brazil 2013 - Resumo

Scrum with Kanban

A release example...

Page 42: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 43: Agile Brazil 2013 - Resumo

Scrum with Kanban

The Product Backlog

Page 44: Agile Brazil 2013 - Resumo

Scrum with Kanban

The team has 3 pairs of engineers,and dependent Stories

(swim lanes)

Page 45: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 46: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 47: Agile Brazil 2013 - Resumo

Scrum with Kanban

Now looking at Sprints

Page 48: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 49: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 50: Agile Brazil 2013 - Resumo

Scrum with Kanban

Let's go back in timeand compare planned and actuals

Page 51: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 52: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 53: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 54: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 55: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 56: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 57: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 58: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 59: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 60: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 61: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 62: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 63: Agile Brazil 2013 - Resumo

Scrum with Kanban

Page 64: Agile Brazil 2013 - Resumo

7 Ways to Track Lead-timePaulo Caroli

Page 65: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 66: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 67: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 68: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 69: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 70: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 71: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 72: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 73: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

WIP = Throughput x Lead time

Page 74: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

12 bottles...

Page 75: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

an average of 6 bottlesper year...

Page 76: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

What is the average lead time for a bottle of whiskey?

Page 77: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

a) 2 monthsb) 3 monthsc) 6 monthsd) 1 yeare) 2 years

What is the average lead time for a bottle of whiskey?

Page 78: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

WIP = Throughput x Lead time

12b = 6b/year x Lead time

Lead time = 2 years

Page 79: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 80: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 81: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 82: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 83: Agile Brazil 2013 - Resumo

7 Ways To Track Lead-Time

Page 84: Agile Brazil 2013 - Resumo

Como cultivar umaCultura KaizenRodrigo Yoshima

Page 85: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 86: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 87: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 88: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 89: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 90: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 91: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 92: Agile Brazil 2013 - Resumo

Como cultivar uma cultura Kaizen

Page 93: Agile Brazil 2013 - Resumo

Métricas de código:Pra que te quero?Mauricio Aniche

Page 94: Agile Brazil 2013 - Resumo

Métricas de código

Page 95: Agile Brazil 2013 - Resumo

Métricas de código

Page 96: Agile Brazil 2013 - Resumo

Métricas de código

Page 97: Agile Brazil 2013 - Resumo

Métricas de código

Page 98: Agile Brazil 2013 - Resumo

Métricas de código

Page 99: Agile Brazil 2013 - Resumo

Métricas de código

Page 100: Agile Brazil 2013 - Resumo

Métricas de código

Page 101: Agile Brazil 2013 - Resumo

Métricas de código

Page 102: Agile Brazil 2013 - Resumo

Métricas de código

Visualizações podem ser úteis também!

Page 103: Agile Brazil 2013 - Resumo

Métricas de código

Page 104: Agile Brazil 2013 - Resumo

Mockar ou não mockar?Mauricio AnicheHugo Corbucci

Page 105: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Mocks para testes de integração

Page 106: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Mocks para isolar a classe testada

Page 107: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizesLuiz F. O. Corte Leal

Page 108: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Teste == Documentação

Page 109: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Orientação a Objetos

● Divisão de responsabilidades● Baixo acoplamento● Coesão

=> Código mais fácil de manter

Page 110: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Má prática: não seguir a convenção da linguagem

Boa prática: quebrar as regrasquando isso te ajudar

Page 111: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Exemplo:

public void class_is_public_not_final() { ...}

Page 112: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Espaços? Onde?

● Contexto (Given)● Ação (When)● Resultados (Then)

Page 113: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Usar as mensagens dos asserts

Page 114: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

Copiou, colou? Isolou!

Page 115: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

BUILDERS!

Page 116: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

FERRAMENTAS!

● Fixture Factory (Java)● factory_girl (Ruby)● Rosie (JS)

Page 117: Agile Brazil 2013 - Resumo

Testes legíveis, projetos felizes

RESUMO: POR QUE?

1. + fácil de ler2. + fácil de escrever3. + fácil de aprender4. + fácil de manter

Page 118: Agile Brazil 2013 - Resumo

Agile: Unlocking our Human PotentialPatrick Kua

Page 119: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 120: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 121: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 122: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 123: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 124: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 125: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 126: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 127: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 128: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 129: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 130: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 131: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 132: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 133: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 134: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 135: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 136: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 137: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 138: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 139: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 140: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 141: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 142: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 143: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 144: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 145: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 146: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 147: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 148: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 149: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 150: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 151: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 152: Agile Brazil 2013 - Resumo

Unlocking our Human Potential

Page 153: Agile Brazil 2013 - Resumo

No movimento da Agilidade - o time de desenvolvimento deve virar o time de marketing!Daniel WildtRafael Helm

Page 154: Agile Brazil 2013 - Resumo

O time de desenvolvimento deve virar o time de marketing!

Page 155: Agile Brazil 2013 - Resumo

O time de desenvolvimento deve virar o time de marketing!

Page 156: Agile Brazil 2013 - Resumo

O time de desenvolvimento deve virar o time de marketing!

DevOps é uma metodologia de desenvolvimento de software que explora a comunicação,

colaboração e integração entre desenvolvedores de software e profissionais de TI. DevOps é a

reação à interdependência entre desenvolvimento de software e operações de TI.

Pretende ajudar organizações a produzir software e serviços rapidamente.

Page 157: Agile Brazil 2013 - Resumo

O time de desenvolvimento deve virar o time de marketing!

Page 158: Agile Brazil 2013 - Resumo

O time de desenvolvimento deve virar o time de marketing!

Page 159: Agile Brazil 2013 - Resumo

O time de desenvolvimento deve virar o time de marketing!

Page 160: Agile Brazil 2013 - Resumo

Coragem para EmpoderarWagner Costa Santos - Sócio da EmphasysAlexandre Magno - Sócio da AdaptWorks

Page 161: Agile Brazil 2013 - Resumo

Coragem para Empoderar

Emphasys - IT Solutions:

● Times auto-organizáveis● Cada time possui uma maturidade, definida em

uma matriz de maturidade.● Gestão horizontal.● Cada projeto uma estrutura.● Transparência de custos, faturamento e

salários.

Page 162: Agile Brazil 2013 - Resumo

Valorizando a SegurançaRemix da palestra de Joshua Kerievskypor Alexandre Freire

Page 163: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 164: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 165: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 166: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 167: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 168: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 169: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 170: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 171: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 172: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 173: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 174: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 175: Agile Brazil 2013 - Resumo

Valorizando a Segurança

Page 176: Agile Brazil 2013 - Resumo

#AgileBr