Agile and Scrum Introduction

Slide 1

Slide 1 text

INTRODUCCIÓN A AGILE Y SCRUM Carlos Buenosvinos (@buenosvinos) [email protected] BetaBeers.com Barcelona, Febrero 2012 Tuesday, February 21, 2012

Slide 2

Slide 2 text

EL ORIGEN DE LAS ESPECIES La especie que sobrevive no es la más fuerte ni la más inteligente, sino la que mejor se adapta. Charles Darwin, The Origin of Species Tuesday, February 21, 2012

Slide 3

Slide 3 text

DILBERT SOBRE “PROCESOS” Tuesday, February 21, 2012

Slide 4

Slide 4 text

EJERCICIO! Calentando! Tuesday, February 21, 2012

Slide 5

Slide 5 text

CARLOS BUENOSVINOS • Certified Scrum Master (CSM) • Certified Scrum Professional (in progress...) • Certified Scrum Trainer (in progress...) • Miembro del comité técnico y Scrum Master en Emagister.com • +10 años de experiencia en el Desarrollo Web y Móviles • Consultor Ágil, Speaker y Development Coach • Email: [email protected] • Twitter: @buenosvinos Tuesday, February 21, 2012

Slide 6

Slide 6 text

EJERCICIO! ¿Cómo estamos de Agile y Scrum? Tuesday, February 21, 2012

Slide 7

Slide 7 text

AGILE OVERVIEW Tuesday, February 21, 2012

Slide 8

Slide 8 text

DILBERT SOBRE SCRUM Tuesday, February 21, 2012

Slide 9

Slide 9 text

¿QUÉ ES AGILE? • Un conjunto de Valores y Principios (The Manifesto) • Un conjunto de Prácticas (The Methods) • Lo más importante, Agile es una forma de pensar y una forma diferente de trabajar para aportar valor de negocio antes. Tuesday, February 21, 2012

Slide 10

Slide 10 text

AGILE MANIFESTO (2001) • We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan • That is, while there is value in the items on the right, we value the items on the left more. • Authors: Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland and Dave Thomas Tuesday, February 21, 2012

Slide 11

Slide 11 text

¿POR QUÉ ELEGIR AGILE? Tuesday, February 21, 2012

Slide 12

Slide 12 text

Tuesday, February 21, 2012

Slide 13

Slide 13 text

EL PRINCIPIO DE PARETO • 80% del valor del producto proviene del 20% de las funcionalides. • 60% de las funcionalidades entregadas en proyectos que salen bien se usan en poquísimas ocasiones. • Preguntaos cuál es el incremento de valor que aporta una nueva funcionalidad sobre otra Tuesday, February 21, 2012

Slide 14

Slide 14 text

AGILE PRACTICES (PARAGÜAS) Tuesday, February 21, 2012

Slide 15

Slide 15 text

EJERCICIO! ¿Cómo os han ido los proyectos? Tuesday, February 21, 2012

Slide 16

Slide 16 text

¿POR QUÉ AGILE? 1. Entregar a tiempo 2. Entregar en presupuesto 3. Entregar con una satisfacción alta de cliente Tuesday, February 21, 2012

Slide 17

Slide 17 text

EINSTEIN SOBRE LA LOCURA LOCURA = Hacer lo mismo una y otra vez y esperar resultados diferentes Tuesday, February 21, 2012

Slide 18

Slide 18 text

DEFINED APPROACH (AKA WATERFALL) Tuesday, February 21, 2012

Slide 19

Slide 19 text

Tuesday, February 21, 2012

Slide 20

Slide 20 text

EMPIRICAL APPROACH Tuesday, February 21, 2012

Slide 21

Slide 21 text

Tuesday, February 21, 2012

Slide 22

Slide 22 text

AGILE VS. WATERFALL Tuesday, February 21, 2012

Slide 23

Slide 23 text

SCRUM FRAMEWORK Tuesday, February 21, 2012

Slide 24

Slide 24 text

VALORES DE SCRUM • Foco • Respeto • Compromiso • Transparencia • Coraje Tuesday, February 21, 2012

Slide 25

Slide 25 text

EJERCICIO! Juguemos con el Foco Tuesday, February 21, 2012

Slide 26

Slide 26 text

ROLES EN SCRUM Tuesday, February 21, 2012

Slide 27

Slide 27 text

ROLES DE SCRUM Tuesday, February 21, 2012

Slide 28

Slide 28 text

ROLES DE SCRUM 1 x Scrum Master Tuesday, February 21, 2012

Slide 29

Slide 29 text

ROLES DE SCRUM 1 x Scrum Master 1 x Product Owner Tuesday, February 21, 2012

Slide 30

Slide 30 text

ROLES DE SCRUM 1 x Scrum Master 1 x Product Owner 1 x Core Team Tuesday, February 21, 2012

Slide 31

Slide 31 text

SCRUM MASTER 1 x Scrum Master Objetivo: Mantener un equipo saludable (Protección, Guía, Liderazgo y Resolución de Obstáculos) Responsabilidades - Daily Scrum - Elimina Blockers - Coordina el tiempo del Equipo (reuniones) - Asegura que los Valores de Scrum no se violan - Deﬁne y Reporta la Productividad del Equipo Tuesday, February 21, 2012

Slide 32

Slide 32 text

SCRUM MASTER 1 x Scrum Master Facilitador para que el equipo alcance sus compromisos, pero no toma decisiones ni se compromete a nada Habilidades - Leer comunicación no verbal - Cómodo con el Conﬂicto - Comunicador efectivo - Genera conﬁanza y respeto - Entiende las dinámicas del equipo Tuesday, February 21, 2012

Slide 33

Slide 33 text

PRODUCT OWNER 1 x Product Owner Objetivo: Guía el Negocio hacia la Visión Responsabilidades: - Representa al Cliente - Es propietario del Product Backlog - Establece, Gestiona y Comunica la Visión - Monitorea el ROI del proyecto - Decide cuándo se hacen entregas oﬁciales Tuesday, February 21, 2012

Slide 34

Slide 34 text

TEAM Objetivo: Ejecuta la Visión y el Product Backlog Responsabilidades: - Se auto-organiza - Se compromete sobre las historias a desarollar en cada Sprint - Se organiza el propio trabajo a desarrollar - Se organizan para alcanzar sus compromisos - Cross functional (Dev., Maq., QA., SEO, etc.) - Desarrolla las historias más importartes (prioridad) del Product Backlog 1 x Core Team Tuesday, February 21, 2012

Slide 35

Slide 35 text

TEAM 1 x Core Team - Tienen las manos en el Teclado - Se comprometen en el Sprint - Hacen las estimaciones - Planean el trabajo - Tiene autoridad para decidir lo que se necesita - Confían en el Scrum Master para resolver Blockers - Confían en el Product Owner para clariﬁcar dudas al respecto del Producto - 6 personas ideal (sin contar SM ni PO) - El Core Team crece en Equipos, no en tamaño Tuesday, February 21, 2012

Slide 36

Slide 36 text

SCRUM FRAMEWORK Tuesday, February 21, 2012

Slide 37

Slide 37 text

Día a día Tuesday, February 21, 2012

Slide 38

Slide 38 text

QUESTIONS Tuesday, February 21, 2012

Slide 39

Slide 39 text

GETTING THINGS DONE Product Backlog Execution in Scrum at Emagister @buenosvinos Tuesday, February 21, 2012

Slide 40

Slide 40 text

PRODUCT BACKLOG The PB is a prioritized list. It’s created using Product Owners priorities and every Story has a technical pre-estimation Tuesday, February 21, 2012

Slide 41

Slide 41 text

OUR CALENDAR Everything is schedule and time-boxed. Tuesday, February 21, 2012

Slide 42

Slide 42 text

TUESDAY, DAY #1 Ready? Go! Tuesday, February 21, 2012

Slide 43

Slide 43 text

PLANNING MEETING Product Owner explains to the Core Team the goal of the Sprint and the detail of every User Story on the Backlog. 10:00 - 12:00 Tuesday, February 21, 2012

Slide 44

Slide 44 text

ESTIMATION MEETING We split the Core Team in two Scrum Teams. Each of the those estimates a subset of the Product Backlog using Story Points 12:00 - 14:00 Tuesday, February 21, 2012

Slide 45

Slide 45 text

STORY POINT AND VELOCITY Our current velocity is 200. It can be affected by holidays, focus of the company, new members, better especiﬁcations, etc. Tuesday, February 21, 2012

Slide 46

Slide 46 text

COMMITMENT Scrum Team commits to a speciﬁc amount of Stories. It’s communicated to the Product Owner and the Company. Moved to Emagister_Scrum Jira Project Tuesday, February 21, 2012

Slide 47

Slide 47 text

NEXT DAYS Focus, focus, focus... Tuesday, February 21, 2012

Slide 48

Slide 48 text

SCRUM BOARD There is no tool as fast and agile as colored post-its and pens. You are invited to come and see! Tuesday, February 21, 2012

Slide 49

Slide 49 text

JIRA We also love JIRA. It gives visibility, especially for people that is not here with us. We’ve created Public Dashboards to help you Tuesday, February 21, 2012

Slide 50

Slide 50 text

DAILY MORNING MEETING Every Scrum Team runs their daily morning meeting in order to keep things under control on a daily basis (15 min. max.) Tuesday, February 21, 2012

Slide 51

Slide 51 text

CONFIDENCE LEVEL Every Scrum Member says a number (1...10) showing his conﬁdence level on achieving the commitment Tuesday, February 21, 2012

Slide 52

Slide 52 text

JIRA TICKET FLOW Every JIRA ticket in the Sprint goes through a ﬂow where Developer, QA and the Product Owner are involved. Tuesday, February 21, 2012

Slide 53

Slide 53 text

TAKE CARE OF YOUR JIRAS Different ways to keep your eyes on your priorities Jira + Notiﬁcations Email + Jira Email Tuesday, February 21, 2012

Slide 54

Slide 54 text

MONDAY, DAY #14 Release Day, Restropective Meeting (Giving feedback) and Pre- estimations Tuesday, February 21, 2012

Slide 55

Slide 55 text

RELEASE We check that all JIRA tickets are Delivered and we launch our automated release process and then we run a sanity check Tuesday, February 21, 2012

Slide 56

Slide 56 text

NEXT SPRINT PRE-ESTIMATION To make priorization easier, we roughly pre-estimate the Product Backlog (S, M, L, XL and XXL) Tuesday, February 21, 2012

Slide 57

Slide 57 text

RETROSPECTIVE Based on the feedback from each member, we propose Tasks for next Sprint to improve tools, processes and people (C.I) Tuesday, February 21, 2012

Slide 58

Slide 58 text

... AND DO IT AGAIN... ...and again... ...and again... ...and again... ...and again... ...and again... ...and again... ...and again... ...and again... ...and again... ... Tuesday, February 21, 2012

Slide 59

Slide 59 text

QUESTIONS Tuesday, February 21, 2012