Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introducción a Agile y Scrum

Betabeers
February 25, 2012

Introducción a Agile y Scrum

imparte Carlos Buenosvinos @buenosvinos

Betabeers

February 25, 2012
Tweet

More Decks by Betabeers

Other Decks in Education

Transcript

  1. 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
  2. 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
  3. ¿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
  4. 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
  5. 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
  6. ¿POR QUÉ AGILE? 1. Entregar a tiempo 2. Entregar en

    presupuesto 3. Entregar con una satisfacción alta de cliente Tuesday, February 21, 2012
  7. EINSTEIN SOBRE LA LOCURA LOCURA = Hacer lo mismo una

    y otra vez y esperar resultados diferentes Tuesday, February 21, 2012
  8. VALORES DE SCRUM • Foco • Respeto • Compromiso •

    Transparencia • Coraje Tuesday, February 21, 2012
  9. ROLES DE SCRUM 1 x Scrum Master 1 x Product

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

    Owner 1 x Core Team Tuesday, February 21, 2012
  11. 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 - Define y Reporta la Productividad del Equipo Tuesday, February 21, 2012
  12. 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 Conflicto - Comunicador efectivo - Genera confianza y respeto - Entiende las dinámicas del equipo Tuesday, February 21, 2012
  13. 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 oficiales Tuesday, February 21, 2012
  14. 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
  15. 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 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
  16. 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
  17. 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
  18. 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
  19. STORY POINT AND VELOCITY Our current velocity is 200. It

    can be affected by holidays, focus of the company, new members, better especifications, etc. Tuesday, February 21, 2012
  20. COMMITMENT Scrum 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
  21. 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
  22. 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
  23. 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
  24. CONFIDENCE LEVEL Every Scrum Member says a number (1...10) showing

    his confidence level on achieving the commitment Tuesday, February 21, 2012
  25. JIRA TICKET FLOW Every JIRA ticket in the Sprint goes

    through a flow where Developer, QA and the Product Owner are involved. Tuesday, February 21, 2012
  26. TAKE CARE OF YOUR JIRAS Different ways to keep your

    eyes on your priorities Jira + Notifications Email + Jira Email Tuesday, February 21, 2012
  27. 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
  28. 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
  29. 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
  30. ... 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