10
Scrum (software development) Nombre : junihor lopez tema : scrum

Scrum (software development)

Embed Size (px)

Citation preview

Page 1: Scrum (software development)

Scrum (software development)Nombre : junihor lopez tema : scrum

Page 2: Scrum (software development)

Scrum (software development) Scrum is an iterative and incremental agile software

development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach"to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project.

Page 3: Scrum (software development)

Roles There are three core roles in the scrum

framework. These core roles are collocated to deliver Potentially Shippable Increment (PSI) by adopting scrum framework—they are the ones producing the product (objective of the project). They represent the scrum team. Although other roles may be encountered in real projects, scrum does not define any team roles other than those described below.

Page 4: Scrum (software development)

Scrum (software development)

Page 5: Scrum (software development)

History

Scrum was first defined as "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as opposed to a "traditional, sequential approach" in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka in the New Product Development Game

Page 6: Scrum (software development)

Scrum

Page 7: Scrum (software development)

Product backlog The product backlog comprises an ordered

list of requirements that a scrum team maintains for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever must be done to successfully deliver a viable product. The product owner orders the product backlog items (PBIs) based on considerations such as risk, business value, dependencies, and date needed.

Page 8: Scrum (software development)

Visión general de Scrum Scrum es un marco de trabajo de procesos que

ha sido usado para gestionar el desarrollo de productos complejos desde principios de los años

90. Scrum no es un proceso o una técnica para construir productos; en lugar de eso, es un marco

de trabajo dentro del cual se pueden emplear varias técnicas y procesos. Scrum muestra la

eficacia relativa de las prácticas de gestión de producto y las prácticas de desarrollo, de modo

que podamos mejorar.

Page 9: Scrum (software development)

Teoría de scrum Scrum se basa en la teoría de control de

procesos empírica o empirismo. El empirismo asegura

que el conocimiento procede de la experiencia y de tomar decisiones basándose en lo que se

conoce. Scrum emplea un enfoque iterativo e incremental para optimizar la predictibilidad y el

control del riesgo.

Page 10: Scrum (software development)

scrum