Métodos Ágiles

  

o   SCRUM: es una metodología ágil para desarrollar productos y servicios.

§  Allows rapid exploration and feedback.

§  Provides a balanced approach to design, which includes some design up front combined with a just-in-time design.

§  Demands cross-functional work.

§  Encourages daily synchronization.

o   Beneficios SCRUM:

§  Delighted costumers

§  Improved return on investment

§  Reduced costs

§  Fast results

§  Confidence to succeed in a complex world

§  More joy

o   SCRUM framework:

§  SCRUM is a framework for organizing and managing work (not a standardized process)

§  The SCRUM framework is based on a set of values, principles and practices that provide the foundation to which an organization will add its unique implementation of relevant engineering practices and your specific approaches for realizing the SRUM practices.

§  SCRUM is refreshingly simple, people-centric framework based on the values of honesty, openness, courage, respect, focus, trust, empowerment and collaboration.

o   SCRUM roles:

§  Equipo SCRUM: dueño del producto, SCRUMmaster y equipo de desarrollo.

·      Dueño: responsable de qué se producirá y en qué orden. Comunica la visión del objetivo. Su obligación es que el trabajo importante se realice. Colabora activamente con los otros miembros del equipo y debe estar disponible para resolver dudas.

·      SCRUM máster: es el responsable de guiar el quipo a crear y seguir su propio proceso basado en el framework de SCRUM. Ayuda a incorporar los valores, principios y prácticas de SCRUM. Ayuda a resolver problemas y a mejorar el sistema SCRUM. Su función es de líder no de gerente.

·      Equipo de desarrollo: es diverso, multifuncional y son responsables de diseñar, construir y probar el producto deseado. Se organiza solo. Entre 5 y 9 personas con las habilidades necesarias.

o   SCRUM activities: 

§  Product backlog: 

·      Important work first.

·      On new product development the product backlog items are features required to meet the product owner’s vision

·      On ongoing product development, it can also contain new features, defect, improvements, etc.

·      The backlog is constantly evolving

§  Sprints:

·      Set up a calendar with sprints of the same duration.

·      The work created in each sprint should create something tangible

·      No goal changes or people changes during the sprint

§  Sprint planning

§  Sprint execution:

·      The development team guided by the master performs all the task-level work necessary to get the features done

·      “Done” means that there is a high degree of confidence that all the work necessary for producing good quality features has been completed

·      Nobody tells the development team in what order or how to do the task-level work

§  Daily SCRUM:

·      15 min meeting

·      Questions:

o   What did I accomplish since the last daily SCRUM?

o   What do I plan to work on by the next daily SCUM?

o   What are the obstacles or impediments that are preventing me form making progress?

·      The daily SCRUM is essential for the long the development team manage the fast, flexible flow of work

·      The daily SCRUM is not a problem-solving activity

·      The daily SCRUM is not a traditional status meeting

·      The daily SCRUM is mainly an inspection and adaptive daily planning activity that helps a self-organizing team do its job better

§  Done:

·      Sprint results: potentially shippable product increment

·      Slice of product functionality that is usable to generate feedback.

§  Sprint review:

·      Inspect and adapt the product

·      Evaluation

§  Sprint retrospective:

·      Before the sprint planning 

·      Opportunity to inspect and adapt the process

·      The team comes together to check what is working

·      Commitments to change the process

o   SCRUM is not a magic cure

§  Good for complex product development 

§  It is simple but not easy

§  Provides visibility to the work processes

o   SCRUM for interrupted work: Kanban

§  Kanban: an approach that is overlaid on an existing process (instead of a stand-alone process solution) and advocates that you:

·      Visualize how the work flows through the system

·      Limit the work in progress at each step to ensure that you are not doing more work than you have the capacity to do

·      Measure and optimize the flow of the work through the system to make continuous improvement