Agile Workshop
Agenda
â—Ź Team
● What’s Agile
● What’s Scrum
● What’s Kanban
● Let’s practice
â—Ź Scrum vs Kanban
â—Ź Takeaways
Gerardo tiene más de 10 años de experiencia y 8 certificaciones en tecnología y
metodologĂ­as. Gerardo ha colaborado como partner tecnolĂłgico de desarrollo y
mentor con startups en Wayra México, adicional a esto Gerardo se desempeñó
como learning coach de la materia Computer Science (CS50) en el MBT de
Collective Academy para JĂłvenes con Alto Potencial.
https://www.linkedin.com/in/gerardovg520/
Raúl tiene más de 6 años de experiencia en el manejo de equipos de gran
escala en áreas como Recursos Humanos e industrias Bancarias basados en
tecnologĂ­as web y mĂłviles. RaĂşl ha colaborado como partner tecnolĂłgico de
desarrollo en Wayra en apoyo a las startups. Raúl se ha desempeñado como
docente de tecnologĂ­as web en la UNAM. https://www.linkedin.com/in/rverah/
Andrés tiene más de 6 años de experiencia en auditoría financiera dentro de
distintas instituciones, especializándose en procesos de Tecnologías de la
Información bajo los estándares internacionales de auditoría.
LinkedIn:https://goo.gl/Ji8QEw
El equipo
What’s Agile
What’s Agile
Agile approaches help teams respond to unpredictability through
incremental, iterative work cadences and empirical feedback.
Agilists propose alternatives to waterfall, or traditional sequential
development.
Scrum in a
nutshell
Scrum
Scrum is an Agile framework for completing complex projects.
Scrum originally was formalized for software development
projects, but it works well for any complex, innovative scope of
work. The possibilities are endless. The Scrum framework is
deceptively simple.
Scrum Manifesto and Principles
http://agilemanifesto.org/principles.html
When to use Scrum
Scrum
Scrum
Scrum
Scrum roles
Scrum backlog
Scrum ceremonies
Velocity is a measure used to identify the number of Story Points developed
during a Sprint. The velocity usually starts poorly during first sprints but after 4
sprint should be increased and should be maintained during time
Scrum Metrics
How to start with Scrum
â—Ź Read more about scrum. Scrum Guide
â—Ź Define the roles within your organization
â—Ź Define an entity by discussing your values and principles as a team and
organization
â—Ź Create your backlog and create a visual dashboard
â—Ź Plan your sprint
â—Ź Implement ceremonies
â—Ź Review your work and results
â—Ź Repeat and learn from experience
Kanban in a
nutshell
Kanban
Kanban is a method for visualizing the flow of work, in order to balance
demand with available capacity and spot bottlenecks. Work items are
visualized to give participants a view of progress and process, from start to
finish. Team members pull work as capacity permits, rather than work
being pushed into the process when requested.
Kanban Foundations and Principles
â—Ź Start with what you do now
â—Ź Agree to pursue incremental, evolutionary change
â—Ź Respect the current process, roles, responsibilities & titles
â—Ź Visualize the workflow
â—Ź Limit WIP
â—Ź Measure and Improve Collaboratively
How to start with Kanban
â—Ź Read more about Kanban. Getting started
â—Ź Understand the current process of your organization
â—Ź Create your kanban board. Examples
â—Ź Limit your Work In Progress (WIP)
â—Ź Create your backlog
â—Ź Visualize your flow
â—Ź Implement some ceremonies (Daily, Retrospective)
â—Ź Review your work and results and learn from experience
Let’s practice
Scrum
Let’s practice Scrum
Situation
â—Ź You are the dev leader for an important startup and the CEO has requested
you to deliver incremental functional products to validate in the market and
get users feedback. The CEO wants to release a new version every month so
you need to work with the team in order to accomplish that.
Product
â—Ź The new product is an fabulous drone that need to accomplish several
requirements from business.
Let’s practice Scrum
Requirements
â—Ź The drone must look stylish and sophisticated
â—Ź The drone must be able to fly during at least 4 seconds
â—Ź The drone should have a camera
â—Ź The drone must be managed remotely
â—Ź The drone should have a GPS
â—Ź The drone must be assembled in parts
â—Ź The drone should have the option to carry another time
Rules
â—Ź You should deliver a functional product every sprint (15 mins) and the Product Owner should approve the product
Kanban vs Scrum
Kanban vs Scrum
â—Ź http://agilemanifesto.org/
â—Ź http://scrumtrainingseries.com/
● Steve Blank’s second commandment in his Manifesto for Customer Development
â—Ź https://leankit.com/learn/kanban/what-is-kanban/
â—Ź https://medium.com/swlh/make-agile-work-startups-e196d7cd2d28
References
THANKS!
Email: gvelazquez@epmsoluciones.com
gerardovg520@gmail.com
Tel: (52) 55 4044 1217
Email: rvera@epmsoluciones.com
vera.h.raul@gmail.com
Tel: (52) 55 3996 7923

Agile Presentation

  • 1.
  • 2.
    Agenda ● Team ● What’sAgile ● What’s Scrum ● What’s Kanban ● Let’s practice ● Scrum vs Kanban ● Takeaways
  • 3.
    Gerardo tiene másde 10 años de experiencia y 8 certificaciones en tecnología y metodologías. Gerardo ha colaborado como partner tecnológico de desarrollo y mentor con startups en Wayra México, adicional a esto Gerardo se desempeñó como learning coach de la materia Computer Science (CS50) en el MBT de Collective Academy para Jóvenes con Alto Potencial. https://www.linkedin.com/in/gerardovg520/ Raúl tiene más de 6 años de experiencia en el manejo de equipos de gran escala en áreas como Recursos Humanos e industrias Bancarias basados en tecnologías web y móviles. Raúl ha colaborado como partner tecnológico de desarrollo en Wayra en apoyo a las startups. Raúl se ha desempeñado como docente de tecnologías web en la UNAM. https://www.linkedin.com/in/rverah/ Andrés tiene más de 6 años de experiencia en auditoría financiera dentro de distintas instituciones, especializándose en procesos de Tecnologías de la Información bajo los estándares internacionales de auditoría. LinkedIn:https://goo.gl/Ji8QEw El equipo
  • 4.
  • 5.
    What’s Agile Agile approacheshelp teams respond to unpredictability through incremental, iterative work cadences and empirical feedback. Agilists propose alternatives to waterfall, or traditional sequential development.
  • 6.
  • 7.
    Scrum Scrum is anAgile framework for completing complex projects. Scrum originally was formalized for software development projects, but it works well for any complex, innovative scope of work. The possibilities are endless. The Scrum framework is deceptively simple.
  • 8.
    Scrum Manifesto andPrinciples http://agilemanifesto.org/principles.html
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
  • 14.
  • 15.
  • 16.
    Velocity is ameasure used to identify the number of Story Points developed during a Sprint. The velocity usually starts poorly during first sprints but after 4 sprint should be increased and should be maintained during time Scrum Metrics
  • 17.
    How to startwith Scrum â—Ź Read more about scrum. Scrum Guide â—Ź Define the roles within your organization â—Ź Define an entity by discussing your values and principles as a team and organization â—Ź Create your backlog and create a visual dashboard â—Ź Plan your sprint â—Ź Implement ceremonies â—Ź Review your work and results â—Ź Repeat and learn from experience
  • 18.
  • 19.
    Kanban Kanban is amethod for visualizing the flow of work, in order to balance demand with available capacity and spot bottlenecks. Work items are visualized to give participants a view of progress and process, from start to finish. Team members pull work as capacity permits, rather than work being pushed into the process when requested.
  • 20.
    Kanban Foundations andPrinciples â—Ź Start with what you do now â—Ź Agree to pursue incremental, evolutionary change â—Ź Respect the current process, roles, responsibilities & titles â—Ź Visualize the workflow â—Ź Limit WIP â—Ź Measure and Improve Collaboratively
  • 21.
    How to startwith Kanban â—Ź Read more about Kanban. Getting started â—Ź Understand the current process of your organization â—Ź Create your kanban board. Examples â—Ź Limit your Work In Progress (WIP) â—Ź Create your backlog â—Ź Visualize your flow â—Ź Implement some ceremonies (Daily, Retrospective) â—Ź Review your work and results and learn from experience
  • 22.
  • 23.
    Let’s practice Scrum Situation ●You are the dev leader for an important startup and the CEO has requested you to deliver incremental functional products to validate in the market and get users feedback. The CEO wants to release a new version every month so you need to work with the team in order to accomplish that. Product ● The new product is an fabulous drone that need to accomplish several requirements from business.
  • 24.
    Let’s practice Scrum Requirements ●The drone must look stylish and sophisticated ● The drone must be able to fly during at least 4 seconds ● The drone should have a camera ● The drone must be managed remotely ● The drone should have a GPS ● The drone must be assembled in parts ● The drone should have the option to carry another time Rules ● You should deliver a functional product every sprint (15 mins) and the Product Owner should approve the product
  • 25.
  • 26.
  • 27.
    ● http://agilemanifesto.org/ ● http://scrumtrainingseries.com/ ●Steve Blank’s second commandment in his Manifesto for Customer Development ● https://leankit.com/learn/kanban/what-is-kanban/ ● https://medium.com/swlh/make-agile-work-startups-e196d7cd2d28 References
  • 28.
    THANKS! Email: gvelazquez@epmsoluciones.com gerardovg520@gmail.com Tel: (52)55 4044 1217 Email: rvera@epmsoluciones.com vera.h.raul@gmail.com Tel: (52) 55 3996 7923

Editor's Notes

  • #4 Somos una empresa de consultorĂ­a en DirecciĂłn de Proyectos e implementaciĂłn de sistemas integrada por un equipo de expertos con amplia trayectoria en proyectos de TI y negocios de gran escala
  • #7 Importante entender el manifesto y los principios
  • #9 Importante entender el manifesto y los 12 principios
  • #11 Analysis Done - Design Done - so on Suppose to work if we had a perfect knowledge no changes and adaptability
  • #12 In Scrum all phases in a blender Fix length iteration called Sprint Since First Sprint, a shippable product is delivered More feedback
  • #13 Iterative no incremental Cross functional team Small amounts of redesigning and modifications on every Sprint Applying Scrum is hard and requires a lot of commitment and effort If is not disrupting your organization then is not Scrum
  • #14 Product Owner Es el responsable de determinar quĂ© es lo importante para el negocio Tiene la visiĂłn y prioridades del producto y negocio Tiene la capacidad y autoridad de tomar decisiones Scrum Dev Team Cross functional team Tiene la capacidad de construir un producto entregable Sabe cĂłmo colaborar, es autĂłnomo y se auto organiza Scrum Master Facilitador Sirve de barrera para no distraer al equipo Promueve las mejores prácticas y se encarga de la salud del equipo No tiene autoridad como manager. el Project Manager regularmente no es por definiciĂłn el SM El tamaño del equipo no debe ser mayor de 9 personas y en caso contrario nuevos equipos deben ser creados con la menor dependencia
  • #15 Product Backlog Features generadas por el PO. El PO debe priorizar. Puede ser en forma de User Story/Requerimiento Sprint Backlog Features que el equipo va a trabajar durante un Sprint y que vienen del Product Backlog
  • #16 Sprint Planning - All team to review which items to deliver Daily Scrum - What I did yesterday, What I’m going to do today and What blockers do I have Sprint Review (Demo) - All team + stakeholders Retrospective - What went well + What could be improved
  • #17 Sprint Planning - All team to review which items to deliver Daily Scrum - What I did yesterday, What I’m going to do today and What blockers do I have Sprint Review (Demo) - All team + stakeholders Retrospective - What went well + What could be improved
  • #18 Sprint Planning - All team to review which items to deliver Daily Scrum - What I did yesterday, What I’m going to do today and What blockers do I have Sprint Review (Demo) - All team + stakeholders Retrospective - What went well + What could be improved
  • #19 Importante entender el manifesto y los principios
  • #20 Product Backlog Features generadas por el PO. El PO debe priorizar. Puede ser en forma de User Story/Requerimiento Sprint Backlog Features que el equipo va a trabajar durante un Sprint y que vienen del Product Backlog
  • #21 Start with what you do now - No hay una forma concreta de ejecutar el mĂ©todo. Si ya posees un flujo de trabajo determinado, puedes adaptarlo a Kanban. Los cambios no son radicales desde el inicio. Agree to pursue incremental, evolutionary change - Kanban está diseñado para evitar roces con tu flujo de trabajo actual. Los cambios radicales se desaconsejan por el hecho de que pueden provocar que pierdas el sentido de lo que haces. En cambio, se centra en hacer pequeños cambios, más que en reinventar la rueda. Respect the current process, roles, responsibilities & titles - Tu modelo actual de trabajo puede no ser del todo malo, y eso es lo mejor de Kanban, que reconoce las ventajas de tu modelo y trata de mejorarlas evolutivamente. Es tu misiĂłn detectar quĂ© se puede mejorar en cada fase del desarrollo del producto. Visualize the work - Siempre ten visible el trabajo, divide el trabajo en piezas, usa columnas para identificar en que estatus esta cada tarea Limit the WIP - Asigna lĂ­mites en cada columna de trabajo acorde a la capacidad del equipo Measure the flow - Tiempo promedio para completar una item completo