Scrum es un marco ágil para el desarrollo de proyectos que utiliza equipos multidisciplinarios auto-organizados. Los roles clave son el Product Owner, que define las historias de usuario; el Scrum Master, que ayuda al equipo a aplicar Scrum; y el Equipo de Desarrollo. El proceso se compone de Sprints cortos donde se seleccionan historias de usuario, se estiman tareas, se desarrolla el software incrementalmente, y se revisa el progreso diariamente. Al final del Sprint se obtiene un incremento potencialmente ent
Understanding the Agile Release and Sprint Planning Process John Derrico
How to easily understand the agile release and sprint planning process. Simple diagrams based on six sigma principles to clearly convey the goals of the planning process including the understanding of the customers as well as the inputs and outputs required for Agile Release and Sprint Planning ant tactics for success.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Understanding the Agile Release and Sprint Planning Process John Derrico
How to easily understand the agile release and sprint planning process. Simple diagrams based on six sigma principles to clearly convey the goals of the planning process including the understanding of the customers as well as the inputs and outputs required for Agile Release and Sprint Planning ant tactics for success.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
A. Kamran's DoD and DoR: Definition of Done and Definition of Ready in ScrumArman Kamran
Definition of what constitutes as a "Ready" PBI (Product Backlog Item) for the Development team to pull into a Sprint, and what makes that PBI considered as "Done" for the Product Owner to review and accept or reject, is a vital factor in building and maintaining a functional and ever improving relationship between PO and the Dev Team.
Here he look at best practices in doing so!
This is a presentation I put together for a conference in 2011. It gives a fast, high level view of where Agile Software Development came from, its core values and principles, and its core practices. It is structured as 7 PechaKucha decks in a row, with short breaks in between, which requires high energy, intensity, and a sense of humor. :)
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.
Learn more about the most popular Agile framework - Scrum. This training should be paired with the pre-training learning materials in Trello. Learn more about the Scrum artifacts (product backlog, sprint backlog, etc.), Scrum roles (Scrum Master, Product Owner, and the team), and the Sprint.
I had to explain Scrum in just 5 slides to the executives. Think of it as an elevator pitch to get them interested and buy the idea. Feel free to use it. Send me any feedback about your experience.
Presentation we did to a group of project managers who had not had any exposure to using Agile methodologies. Gives a basic overview of Agile with a User Centered design approach.
Kanban tool is used for handling agile project management methods, right? No – Kanban in project management can do a lot more. Here is a list of how it works and how it helps your team communicate and collaborate more efficiently on project tasks, even if you are not using agile methods.
A. Kamran's DoD and DoR: Definition of Done and Definition of Ready in ScrumArman Kamran
Definition of what constitutes as a "Ready" PBI (Product Backlog Item) for the Development team to pull into a Sprint, and what makes that PBI considered as "Done" for the Product Owner to review and accept or reject, is a vital factor in building and maintaining a functional and ever improving relationship between PO and the Dev Team.
Here he look at best practices in doing so!
This is a presentation I put together for a conference in 2011. It gives a fast, high level view of where Agile Software Development came from, its core values and principles, and its core practices. It is structured as 7 PechaKucha decks in a row, with short breaks in between, which requires high energy, intensity, and a sense of humor. :)
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.
Learn more about the most popular Agile framework - Scrum. This training should be paired with the pre-training learning materials in Trello. Learn more about the Scrum artifacts (product backlog, sprint backlog, etc.), Scrum roles (Scrum Master, Product Owner, and the team), and the Sprint.
I had to explain Scrum in just 5 slides to the executives. Think of it as an elevator pitch to get them interested and buy the idea. Feel free to use it. Send me any feedback about your experience.
Presentation we did to a group of project managers who had not had any exposure to using Agile methodologies. Gives a basic overview of Agile with a User Centered design approach.
Kanban tool is used for handling agile project management methods, right? No – Kanban in project management can do a lot more. Here is a list of how it works and how it helps your team communicate and collaborate more efficiently on project tasks, even if you are not using agile methods.
Esta presentación incluye una introducción de Scrum en Proyectos que hemos realizado en tecnología Microsoft. Usando herramientas que nos permite llevar todo el ciclo de vida del proyecto con la metodología ágil como SCRUM. Herramientas como Visual Studio Team Services (VSTS) permiten facilitar el trabajo del equipo desde la planeación del sprint hasta la entrega del producto.
Agenda:
1. Manifiesto Ágil
2. Scrum
3. Valores Scrum
4. Roles Scrum
5. Actividades Scrum
6. Logros Scrum en iTS y proximos pasos
Curso introducción a Scrum, unión de diversas experiencias, wiki y otros cursos para conocer en detalle la metodología Scrum.
- Donde se ubica Scrum dentro de las metodologías agiles
- ¿Qué es Scrum?
- Roles en scrum
- Procesos en Scrum
- Ceremonias
Charla de SCRUM impartida por el Ing. Jhon Alexander Holguín Barrera a los estudiantes de Ingeniería del Software de la Universidad Católica de Pereira, 2011.
3. Introducción
• Scrum entrega un marco de desarrollo ágil e incremental en
el que se aplican de manera regular un conjunto de buenas
practicas para trabajar colaborativamente, en equipo, y
obtener el mejor resultado posible de un proyecto.
• El modelo de proceso comenzó a forjarse con un articulo
publicado en Harvard Business Review en 1986 sobre los
modelos de desarrollo de producto utilizados por la industria
Japonesa.
• El articulo utiliza metáforas del juego de rugby, como scrum
(Melé).
• En la década de los 90, Jeff Sutherland y Ken Schwaber
desarrollan el proceso Scrum para desarrollo de sistemas de
software.
4. Características
• Scrum como metodología, esta indicada para proyectos o
entornos complejos donde se deben obtener resultados en
forma temprana, donde los requisitos son cambiantes o poco
definidos.
• En Scrum se planifican y se realizan entregas parciales del
producto final priorizadas por el beneficio que aportan al
receptor o riesgo, según una lista de requisitos priorizada y en
plazos cortos y fijos.
• Equipo Multidisciplinario, Motivado y auto-organizado.
• Planificación adaptativa.
• Feedback del producto y del proceso en cada iteración.
• Cada entrega contiene un conjunto de características
completas que pueden ponerse en producción.
5. Equipo de trabajo, Roles
• El proceso Scrum es desarrollado por un equipo de trabajo
multidisciplinario y auto-organizado, el cual tiene una
estructura fija basada en roles:
6. Equipo de trabajo, Roles
• Product Owner:
o Responsable de la Visión del producto.
o Nexo de conexión entre el equipo de desarrollo y los
stakeholders (clientes y usuarios).
o Decide que características y funcionalidades (Historias de
Usuario) ha de tener el sistema en desarrollo y el orden en
que deben ser implementadas (Product Backlog) y las
valida.
o Participa activamente en el equipo scrum.
7. Equipo de trabajo, Roles
• Scrum Master:
o Ayuda a los miembros del Equipos a aplicar los principios,
valores y practicas de Scrum.
o Ayuda en la organización en la adopción del proceso
Scrum.
o Lidera al equipo de desarrollo (no dirige ni gestiona), es un
facilitador.
o Es el responsable del proceso Scrum y esta la servicio de
los miembros del equipo de desarrollo para facilitar su
aplicación.
o Debe asegurarse de que se cumplan todas las etapas y
reglas de Scrum.
8. Equipo de trabajo, Roles
• El Equipo de Desarrollo:
o Responsables del diseño, implementación y verificación del
sistema en desarrollo.
o El equipo se auto-organiza para llevar a cabo los objetivos
fijados por el product owner.
o En conjunto deben tener todos los conocimientos y
capacidades para producir software funcional de buena
calidad. Conocimientos transversales y con profundidad.
o Tamaño Típico es de 5 a 9 personas.
10. Actividades y artefactos
Tipo Actividad /
Artefacto
Descripción Responsables /
Participantes
Duración
Artefacto BackLog de
Producto
Lista de características (Historias de
Usuario) priorizadas (por valor de
negocio o riesgo) del producto.
(R) Product Owner
Scrum Master
4 hrs.
Artefacto Release
RoadMap
Es un Plan de alto nivel que indica lo
que vamos a estar entregando y
cuando (cantidad de releases y
tiempo).
Product Owner
Scrum Master
Equipo de Desarrollo
Actividad Planificación
del Sprint
Se seleccionan las características a
implementar en un sprint, se estima
tiempo y esfuerzo (planning poker) y
se adquiere el compromiso de
realizarlo.
(R) Product Owner
Equipo de Desarrollo
Scrum Master
4 Hrs.
Selección y 4
Hrs.
Estimación
Artefacto Sprint BackLog Es una lista de tareas estimada de cada
característica a implementar, cada
tarea tiene un dificultad (Fibonacci) y
una duración.
(R) Equipo de Desarrollo
Actividad Ejecución del
Sprint
Tareas necesarias para implementar
las características del Sprint.
(R)Equipo de Desarrollo
Product Owner
4 semanas
máximo por
Sprint
Actividad Daily Scrum Es una Reunión diaria de revisión de la
ejecución de las tareas
(R)Scrum Master
Product Owner
Development Team
10 a 15
minutos por
día
11. Actividades y artefactos
Tipo Actividad /
Artefacto
Descripción Responsables /
Participantes
Duración
Artefacto Incremento del
Producto
Al finalizar la ejecución del sprint se
obtiene una mejora o incremento del
producto que es potencialmente
entregable al cliente
(R) Development Team
Actividad Sprint Review El equipo y los stakeholders revisan el
producto entregado y se recoge el
feedback
Development Team
Product Owner
Scrum Master
StakeHolders
4 Hrs.
Máximo
Actividad Sprint
Retrospective
Acá se revisa el proceso Scrum con la
finalidad de mejorar el proceso en si
Development Team
Product Owner
Scrum Master
3 Hrs.
Máximo
Artefacto Entrega del
Producto Final
Tras una serie de Sprints se finaliza la
implementación del producto
Development Team
Product Owner
Scrum Master
12. Burndown Chart
• El BurnDown chart, es un grafico que sirve para conocer el
estado actual de un proyecto Scrum y poder predecir cuando
va a estar terminado un Sprint.
• Se utilizan como bases para el grafico, las horas estimadas
restantes V/S las horas reales restantes .
•
Línea Ideal, Cuanto nos
va a tomar
desarrollar las tareas
El progreso Real, por
debajo de la línea ideal
indica que vamos
acorde a los plazos
El progreso Real, por
encima de la línea ideal
indica que vamos
atrasados