INTRODUCCIÓN AAGILE Y SCRUM
Carlos Buenosvinos (@buenosvinos)[email protected]
BetaBeers.comBarcelona, Febrero 2012
Tuesday, February 21, 2012
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
DILBERT SOBRE “PROCESOS”
Tuesday, February 21, 2012
EJERCICIO!Calentando!
Tuesday, February 21, 2012
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: @buenosvinosTuesday, February 21, 2012
EJERCICIO!¿Cómo estamos de Agile y
Scrum?
Tuesday, February 21, 2012
AGILE OVERVIEW
Tuesday, February 21, 2012
DILBERT SOBRE SCRUM
Tuesday, February 21, 2012
¿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
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
¿POR QUÉ ELEGIR AGILE?
Tuesday, February 21, 2012
Tuesday, February 21, 2012
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
AGILE PRACTICES (PARAGÜAS)
Tuesday, February 21, 2012
EJERCICIO!¿Cómo os han ido los
proyectos?
Tuesday, February 21, 2012
¿POR QUÉ AGILE?
1. Entregar a tiempo
2. Entregar en presupuesto
3. Entregar con una satisfacción alta de cliente
Tuesday, February 21, 2012
EINSTEIN SOBRE LA LOCURA
LOCURA = Hacer lo mismo una y otra vez y esperar resultados diferentes
Tuesday, February 21, 2012
DEFINED APPROACH(AKA WATERFALL)
Tuesday, February 21, 2012
Tuesday, February 21, 2012
EMPIRICAL APPROACH
Tuesday, February 21, 2012
Tuesday, February 21, 2012
AGILE VS. WATERFALL
Tuesday, February 21, 2012
SCRUM FRAMEWORK
Tuesday, February 21, 2012
VALORES DE SCRUM
• Foco
• Respeto
• Compromiso
• Transparencia
• Coraje
Tuesday, February 21, 2012
EJERCICIO!Juguemos con el Foco
Tuesday, February 21, 2012
ROLES EN SCRUM
Tuesday, February 21, 2012
ROLES DE SCRUM
Tuesday, February 21, 2012
ROLES DE SCRUM
1 x Scrum Master
Tuesday, February 21, 2012
ROLES DE SCRUM
1 x Scrum Master
1 x Product Owner
Tuesday, February 21, 2012
ROLES DE SCRUM
1 x Scrum Master
1 x Product Owner
1 x Core Team
Tuesday, February 21, 2012
SCRUM MASTER1 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- Define y Reporta la Productividad del Equipo
Tuesday, February 21, 2012
SCRUM MASTER1 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 Conflicto- Comunicador efectivo- Genera confianza y respeto- Entiende las dinámicas del equipo
Tuesday, February 21, 2012
PRODUCT OWNER1 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 oficiales
Tuesday, February 21, 2012
TEAM
Objetivo: Ejecuta la Visión y el Product Backlog
Responsabilidades:- Se auto-organiza- Se compromete sobre las historias a desarollar encada 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
TEAM1 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 clarificar 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
SCRUM FRAMEWORK
Tuesday, February 21, 2012
Día a día
Tuesday, February 21, 2012
QUESTIONS
Tuesday, February 21, 2012
GETTING THINGS DONEProduct Backlog Execution in Scrum at Emagister
@buenosvinos
Tuesday, February 21, 2012
PRODUCT BACKLOGThe PB is a prioritized list. It’s created using Product Owners
priorities and every Story has a technical pre-estimation
Tuesday, February 21, 2012
OUR CALENDAREverything is schedule and time-boxed.
Tuesday, February 21, 2012
TUESDAY, DAY #1Ready? Go!
Tuesday, February 21, 2012
PLANNING MEETINGProduct 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
ESTIMATION MEETINGWe 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
STORY POINT AND VELOCITYOur current velocity is 200. It can be affected by holidays, focus
of the company, new members, better especifications, etc.
Tuesday, February 21, 2012
COMMITMENTScrum Team commits to a specific amount of Stories. It’s
communicated to the Product Owner and the Company.
Moved to Emagister_Scrum Jira Project
Tuesday, February 21, 2012
NEXT DAYSFocus, focus, focus...
Tuesday, February 21, 2012
SCRUM BOARDThere is no tool as fast and agile as colored post-its and pens.
You are invited to come and see!
Tuesday, February 21, 2012
JIRAWe 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
DAILY MORNING MEETINGEvery 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
CONFIDENCE LEVELEvery Scrum Member says a number (1...10) showing his
confidence level on achieving the commitment
Tuesday, February 21, 2012
JIRA TICKET FLOWEvery JIRA ticket in the Sprint goes through a flow where
Developer, QA and the Product Owner are involved.
Tuesday, February 21, 2012
TAKE CARE OF YOUR JIRASDifferent ways to keep your eyes on your priorities
Jira + NotificationsEmail + Jira Email
Tuesday, February 21, 2012
MONDAY, DAY #14Release Day, Restropective Meeting (Giving feedback) and Pre-
estimations
Tuesday, February 21, 2012
RELEASEWe 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
NEXT SPRINT PRE-ESTIMATIONTo make priorization easier, we roughly pre-estimate the
Product Backlog (S, M, L, XL and XXL)
Tuesday, February 21, 2012
RETROSPECTIVEBased on the feedback from each member, we propose Tasks for next Sprint to improve tools, processes and people (C.I)
Tuesday, February 21, 2012
... 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
QUESTIONS
Tuesday, February 21, 2012