🛠 METODOLOGÍAS ÁGILES 📖 (2020) 💻

Summary

Este vídeo explica las metodologías ágiles, su importancia y origen, destacando su relevancia en la transformación digital de empresas. Se describe el cambio de enfoque desde el modelo de cascada a un enfoque ágil que prioriza la entrega continua de valor al cliente. Se introduce el Manifiesto Ágil y sus principios, y se exploran las metodologías ágiles como marcos de trabajo adaptables. Se menciona Scrum como la más popular, con roles, eventos y artefactos clave, y se invita a los espectadores a explorar más sobre Scrum en otros videos.

Takeaways

• 🌐 La transformación digital es un factor clave que ha impulsado la relevancia de las metodologías ágiles en las empresas.
• 📱 Las empresas están creando aplicaciones y servicios digitales para mejorar y adaptarse a la competencia y a las necesidades cambiantes de los clientes.
• 🏢 La necesidad de tener un equipo de trabajo interno en lugar de externalizar el desarrollo de software ha aumentado con la transformación digital.
• 📝 Antes de las metodologías ágiles, se usaba un enfoque de 'caspa de agua' donde se requería un documento detallado de requisitos y el desarrollo del software tomaba mucho tiempo.
• 📉 El enfoque 'caspa de agua' a menudo resultaba en sistemas obsoletos antes de su lanzamiento debido a los cambios rápidos en las necesidades empresariales.
• 📝 En 2001, nació el Manifiesto Ágil para mejorar las prácticas de desarrollo de software, enfocándose en la entrega continua de valor al cliente.
• 🔄 Las metodologías ágiles se centran en la iteración rápida, la colaboración con el cliente y la adaptación a los cambios para satisfacer las necesidades actuales.
• 👥 En el marco ágil, los equipos de trabajo son autónomos y se les permite tomar decisiones importantes sobre el producto.
• 🔧 Se entregan pequeñas funcionalidades o partes de código que han sido probadas para garantizar una alta calidad en el producto final.
• 🔄 Las metodologías ágiles permiten que los requisitos y la visión del producto evolucionen a medida que avanza el proyecto.
• 🚀 SCRUM es una de las metodologías ágiles más utilizadas y se compone de roles, eventos y artefactos que ayudan a estructurar el proceso de desarrollo.

Q & A

¿Qué son las metodologías ágiles y por qué son importantes?

Las metodologías ágiles son enfoques para la gestión de proyectos y desarrollo de software que promueven la entrega de valor a los clientes de manera continua y rápida. Son importantes porque permiten adaptarse a los cambios rápidos y frecuentes en las necesidades de los clientes y del mercado.

¿Cuál es la relación entre la transformación digital y la adopción de metodologías ágiles?

La transformación digital es el proceso por el cual las empresas adoptan tecnologías digitales para mejorar sus servicios y operaciones. Las metodologías ágiles son relevantes en este contexto porque facilitan la adaptación y la innovación rápida, lo que es esencial en un entorno de transformación digital.

¿Qué es el 'Manifesto Ágil' y cuáles son sus cuatro principios básicos?

El 'Manifesto Ágil' es un documento que define los valores fundamentales detrás de las metodologías ágiles. Sus cuatro principios básicos son: valorar a las personas y las interacciones sobre los procesos y herramientas, valorar el software funcionando sobre la documentación exhaustiva, priorizar el trabajo en colaboración con el cliente sobre los contratos y la documentación, y permitir que se admitan cambios en los requisitos, incluso后期中 del proyecto.

¿Cuáles son las 12 principios que acompañan al 'Manifesto Ágil'?

Los 12 principios son una desglose detallado de los cuatro valores fundamentales del 'Manifesto Ágil' y proporcionan orientación sobre cómo aplicar estas ideas en la práctica diaria del desarrollo de software.

¿Qué diferencia hay entre el enfoque de 'cascada' y las metodologías ágiles?

El enfoque de 'cascada' es un modelo de desarrollo de software donde se siguen fases lineales y secuenciales, y los cambios son difíciles de implementar una vez que se ha avanzado a la siguiente fase. En contraste, las metodologías ágiles permiten la iteración rápida y el cambio constante, facilitando la adaptación a los requisitos cambiantes.

¿Qué son las 'metodologías ágiles' y cómo se diferencian de las 'metodologías' tradicionales?

Las 'metodologías ágiles' son marcos de referencia flexibles que se adaptan y mejoran a través de un proceso empírico, en lugar de ser series de pasos inamovibles como las metodologías tradicionales.

¿Cuáles son los roles principales en Scrum y qué responsabilidades tienen?

Los roles principales en Scrum son el Product Owner, el Scrum Master y el Development Team. El Product Owner se encarga de la visión del producto y la comunicación con los stakeholders, el Scrum Master elimina los obstáculos para el progreso del equipo y promueve la metodología, y el Development Team es responsable de codificar y crear el producto.

¿Cuáles son los eventos clave en Scrum y qué ocurre en cada uno?

Los eventos clave en Scrum incluyen el Sprint (período de tiempo para entregar código funcional), la Planificación del Sprint (donde se planifican las tareas), el Daily Scrum (reunión diaria para revisar el progreso y los bloqueos), la Revisión del Sprint (presentación de lo desarrollado y retroalimentación) y la Retrospectiva del Sprint (reunión para mejorar el proceso).

¿Qué son los 'artefactos' en Scrum y cuáles son los tres principales?

Los 'artefectos' en Scrum son elementos utilizados para guiar el proceso de desarrollo. Los tres principales son el Product Backlog (lista de requisitos), el Sprint Backlog (tareas seleccionadas para un sprint) y el Product Increment (código funcional testeado entregado al final del sprint).

¿Por qué es importante la Retrospectiva del Sprint en Scrum?

La Retrospectiva del Sprint es importante porque permite al equipo reflexionar sobre su desempeño, identificar qué ha funcionado bien y qué no, y establecer acciones para mejorar continuamente, lo que lleva a un aumento en la productividad y en la calidad del trabajo.

Outlines

00:00

😀 Introducción a las metodologías ágiles

El primer párrafo introduce el tema de las metodologías ágiles y su importancia en la actualidad. Se menciona que la transformación digital que están experimentando la mayoría de las empresas es un factor clave que ha incrementado su relevancia. Se da un ejemplo de una panadería que busca innovar a través de una aplicación para notificar a los suscriptores cuando se hornea pan. Además, se discute cómo las empresas están adoptando la tecnología para mejorar sus servicios y satisfacer mejor a sus clientes. La necesidad de tener un equipo de trabajo interno en lugar de outsourcer el desarrollo de software es un punto central para la adopción de metodologías ágiles, que surgieron como respuesta a la necesidad de una mejora en la producción de soluciones rápidas y adaptativas.

05:01

📝 Origen y principios del Manifiesto Ágil

Este párrafo explora el origen del Manifiesto Ágil, un documento creado en 2001 por un grupo de profesionales que buscaban mejorar las prácticas de desarrollo de software. Se describe cómo el enfoque tradicional basado en requerimientos detallados y entregas largas (como el modelo de Cascada) resultaba en soluciones obsoletas antes de ser entregadas. En contraste, el Manifiesto Ágil promueve la entrega continua de valor al cliente, con la flexibilidad de adaptarse a los cambios y la priorización de la funcionalidad sobre la documentación exhaustiva. Se destacan los cuatro principios básicos del manifiesto: valorar a las personas y sus interacciones, la software funcional sobre la documentación, la colaboración cercana con el cliente sobre los contratos y permitir el cambio como parte del proceso.

10:04

🔄 Metodologías Ágiles y su Aplicación

El tercer párrafo profundiza en las metodologías ágiles como marcos de referencia en lugar de procedimientos fijos, y cómo difieren de las metodologías tradicionales. Se enfatiza la importancia de la iteración rápida, la colaboración con los clientes (o stakeholders) y la creación de equipos de trabajo empoderados. Además, se menciona la entrega de funciones pequeñas y probadas para garantizar una alta calidad en el producto final. Se discute cómo las necesidades y la visión del producto pueden evolucionar a lo largo del tiempo, lo que es fundamental en un mundo en constante cambio. Se presentan ejemplos de metodologías ágiles comunes como SCRUM, CRYSTAL, XP y Agile UX, destacando la popularidad de SCRUM en la industria.

15:07

🏗️ Funcionamiento Básico de SCRUM

El último párrafo se centra en SCRUM, una de las metodologías ágiles más utilizadas, y describe brevemente sus tres pilares fundamentales: roles, eventos y artefactos. Se explica que los roles principales son el Product Owner, el Scrum Master y el Equipo de Desarrollo. Los eventos incluyen el sprint, la planificación del sprint, la reunión diaria (daily scrum), la revisión del sprint y la retrospectiva del sprint. Los artefactos son el backlog del producto, el backlog del sprint y el incremento del producto. El párrafo concluye invitando al espectador a explorar más sobre SCRUM en otros videos del canal.

Keywords

💡Metodologías Ágiles

Las metodologías ágiles son un enfoque en el desarrollo de software que promueve la adaptabilidad y la colaboración entre el equipo de desarrollo y los clientes. Se centran en producir resultados de valor para el cliente de manera rápida y en iteraciones. En el guion, se menciona que estas metodologías son relevantes en la transformación digital que están experimentando muchas empresas, permitiendo a los equipos de trabajo dentro de la empresa adaptarse rápidamente a los cambios y a las necesidades del cliente.

💡Transformación Digital

La transformación digital se refiere al proceso de integrar tecnología digital en todos los aspectos de un negocio para mejorar sus operaciones y ofrecer mejores servicios a los clientes. En el guion, se utiliza el ejemplo de una panadería que decide crear una aplicación para notificar a los suscriptores cuando se produce pan, ilustrando cómo las empresas tradicionales pueden adoptar nuevas tecnologías para competir en el mercado.

💡Manifesto Ágil

El Manifesto Ágil es un documento que establece cuatro valores fundamentales para el desarrollo de software de manera ágil. En el guion, se menciona que este manifiesto nació en 2001 en Utah como una respuesta a la necesidad de mejorar las prácticas de desarrollo de software. El manifiesto promueve la entrega constante de valor al cliente, la interacción entre individuos, el software funcional y la colaboración cercana con el cliente sobre la documentación exhaustiva y los contratos.

💡Desarrollo por Cascada

El desarrollo por cascada es un modelo de desarrollo de software en el que se siguen fases lineales y secuenciales, desde la especificación hasta la implementación. En el guion, se contrasta con las metodologías ágiles, donde se enfatiza en la entrega temprana y continua de valor, en lugar de esperar hasta el final del proyecto para ver si el sistema cumple con las necesidades del cliente.

💡SCRUM

SCRUM es una de las metodologías ágiles más populares que se utiliza para gestionar proyectos y equipos de desarrollo. Se compone de roles, eventos y artefactos que facilitan la colaboración y la entrega de valor. En el guion, se menciona SCRUM como un ejemplo de cómo las metodologías ágiles pueden ser implementadas en práctica, con roles como el Product Owner, Scrum Master y el equipo de desarrollo, y eventos como la planificación de sprint, la reunión diaria, la revisión de sprint y la retrospectiva de sprint.

💡Iteración

La iteración es el proceso de repetir un ciclo de desarrollo con el objetivo de mejorar gradualmente un producto o solución. En el guion, la iteración es clave en las metodologías ágiles, donde se entregan versiones incrementales de software que se ajustan constantemente a las necesidades cambiantes del cliente.

💡Stakeholder

Un stakeholder es cualquier persona o grupo que tiene un interés en el proyecto o la empresa. En el guion, se destaca la importancia de la colaboración con los stakeholders en las metodologías ágiles, ya que su retroalimentación es esencial para asegurar que el producto desarrollado cumpla con sus expectativas y necesidades.

💡Backlog

El backlog es una lista de trabajo que se mantiene actualizada y priorizada en las metodologías ágiles. En el guion, se menciona el product backlog como una lista de requisitos y el sprint backlog como una selección de ítems del backlog que se trabajarán durante un sprint específico. Estos backlogs son fundamentales para la planificación y el enfoque en la entrega de valor.

💡Incremento de Producto

El incremento de producto en SCRUM es el conjunto de trabajo funcional y probado que se entrega al final de cada sprint. En el guion, se describe cómo este incremento de producto es una pieza clave en la metodología ágil, ya que representa el progreso tangible y verificable del proyecto que se puede mostrar a los stakeholders.

💡Desarrollo por Empleo

El desarrollo por empleo es una práctica en la que se entregan pequeñas partes del código que ya han sido probadas, garantizando que la entrega final del producto sea de alta calidad. En el guion, se menciona cómo este enfoque contrasta con el desarrollo tradicional, donde se espera hasta el final del proyecto para probar la funcionalidad completa del sistema.

Highlights

Agile methodologies are crucial for digital transformation in businesses.

Digital transformation involves using technology to improve services and customer satisfaction.

Companies are shifting from outsourcing to having in-house teams for software development.

Agile methodologies emerged to help non-tech companies manage internal software development teams.

Traditional development involved lengthy processes with detailed requirement documents.

The Agile Manifesto was created in 2001 to improve software development practices.

The Agile Manifesto emphasizes delivering value to customers quickly and iteratively.

Agile methodologies contrast with the Waterfall model, which follows a rigid, sequential process.

The Agile Manifesto is based on four fundamental values.

Agile principles prioritize individuals and interactions, functional software, and collaboration over processes and contracts.

Agile methodologies are frameworks that adapt and improve through empirical processes.

Agile encourages close collaboration with customers and quick feedback loops.

Agile methodologies focus on empowered teams, incremental deliveries, and evolving requirements.

SCRUM is a widely used Agile methodology, with over 70% of companies reportedly using it.

SCRUM has three main pillars: roles, events, and artifacts.

Roles in SCRUM include the Product Owner, Scrum Master, and Development Team.

SCRUM events include the sprint, sprint planning, daily scrum, sprint review, and retrospective.

SCRUM artifacts consist of the product backlog, sprint backlog, and product increment.

Agile methodologies allow for continuous improvement and adaptation to changing business needs.

Transcripts

Hello! In this video we'll be talking about agile methodologies,

what their importance is and how they came about. Before fully entering to what they are

it seems important to me to explain the reason why I consider

these have become relevant or valuable lately. It seems to me

that the first trigger is digital transformation that most

companies are currently experiencing. What do I mean by

digital transformation? Well, I'd like to make a video afterwards exclusively

about this topic but for now I'll give an example to understand it.

A bakery around your home. Let's say this bakery is

noticing there is a lot of competition and there are other bakeries around and wants

to get on the digital transformation ship. Something simple this bakery

could do is to create an app so that whenever bread is produced a notification is sent to

whomever subscribed to this service. As well as this

there are thousands of other examples of things that companies are doing in this

time to get into the digital transformation or to be a part of using the

technology to provide a better service or

greater satisfaction to their customers. Why do I mention this about the digital transformation?

Well, because what companies used to do was to hire

someone or a development team that would create those solutions.

Whatever the company's business is what is happening is that they are

realizing about the need to have a work team within the

company instead of doing outsourcing for the development of the

code or of improvements to systems they currently have.

That's where the importance of agile methodologies begins because once you

have your team formed, well you are not a company that is dedicated to

technology. For example, those who sell shoes have a webpage or have an

app where they sell online maybe, they have an inventory system. They have

many applications that have to do with code. What happens with that internal team

that is creating apps. How do they work? If you're not a

software developer company, How are you going to make those people work in

something for your business? Well, that's when agile methodologies are born.

What was previously done? Well, a list of requirements

was put together in a very detailed way that consisted of, let's say, 50 or 100 pages

describing exactly all the capabilities or whatever we wanted the

users could do after create the system created. So what happened?

Well, this document was handed to companies that

developed software and they would budget the service and tell you "see you in

six months with the minimum viable product". Right? With the first version of your

system. Everyone went back to their working places and got back to the

development team almost three or four months for some follow-up meeting, some

questions and at the end of six or seven months you already had a

software version. What happened then? When they gave you the

system it turns out there weren't the same categories

than those you had in the company, the person who designed the

system had already moved to another area, several processes had already changed

and the system was no longer useful for the new ones. The need arises then to

find a way to produce better solutions and so

in 2001 a group of people got together in Utah, I believe, and they started to

talk about a way to improve techniques or practices to develop

software. It's there where they came up with the agile manifesto which is a document with

four basic principles or fundamental values to create code.

If we had to define the agile manifesto in a sentence

we would simply say that the idea behind it is to constantly deliver value

to customers so in case you fail or if you are going to succeed in something

the client asked you, you do it quickly. I mean you are checking certain

hypotheses or certain stories or certain features that the client is requesting and

you deliver as you have something of value to deliver.

This approach is very different of what was previously done in the system

called waterfall where, as we discussed, a huge amount of

requirements was taken and after a very long time you knew if the system

you were designing worked or not for the client.

The four principles on which this agile manifesto

is based upon are as follows: 1. To value the

individuals more and the interactions between them

versus having the tools and the very defined processes as it was

previously done. 2. To value the functional software about the

exhaustive documentation. A piece of code that generates some value

and that works for the customer has more value than a

documentation of a hundred page system. 3. The close collaboration with the client

is more valuable about the documentation and contracts

that had been previously defined.

4. Change is allowed. You can adapt the

way as the project progresses. In the comments I will add links to

what the agile manifesto is and to the 12 principles that were also created as

part of this meeting. As you can imagine this this agile manifesto and the 12

principles for developing software are closely related. In the end, the

12 principles are more like a detailed breakdown of the four fundamental values.

Here in the comments I will put links to both documents.

Of course the above was a revolution in the industry

of software development. A lot of controversy, a lot of controversy and so...

there was a lot of controversy and so. Well then, what are the agile methodologies?

we know this manifesto was made, they had the principles and everything was

okay but how do I put it into practice with the working groups that I have?

It's then when the called agile methodologies were brought up.

Which aren't really methodologies because they improve themselves and adapt

through an empirical process then a methodology is usually a series

of steps that are unalterable or immovable and this is not what happens

with agile methodologies. Actually agile methodologies end up being

a framework which is a frame of reference. While each

of the agile methodologies that we currently have in the industry are

very different from each other, they share many similar characteristics.

For example the idea is, in all, to quickly iterate with the customer.

Being close to him and see that if a feature or something you developed is going to fail,

it happens quickly and learn. and receive feedback from the

final customer or so-called stakeholders. A stakeholder can be a user of the

system can be a manager can be some director may be the CEO.

Anyone in the company can be a stakeholder even outside

from it. There are stakeholders that can be external customers. In the end, a stakeholder

is everyone who is going to benefit from value that is being delivered with the

system. The idea, mostly, is also to generate empowered work teams

to make important decisions of the product. Another of the

most fundamental principles of these methodologies is to deliver

small functions or small pieces of code that were already tested. This

way you can guarantee that the final delivery of the product is going to be

high quality since all parts of what's being delivered

had a process for quality assurance. In these methodologies the

requirements evolve as well as the team evolves.

The vision of the product can be changeable. In fact that's the point

of these methodologies when you follow the waterfall system above is

probably because you have a system that won't change. The requirement

from the beginning to the end will be the same.

In that case agile methodologies are not very useful.

However, we know how changing the world is now. Every minute, every day

a requirement that worked yesterday or the day before may no longer work

next week. There's the value of these agile principles and of these

frameworks where you can adapt to business needs

and the vision of the product can change without punishing in the least the

good development process. Each of these environments or frameworks

has its own advantages and its own weaknesses as everything in life.

In this picture we can see the two ways of developing software

or solutions. If you take a look at the top part, we have the traditional

waterfall. We know that in the end of the project we need to have a means of

transport and we think it is a car. So we design it and start

working on the tires first, then in the middle part, then in the

bodywork. At the end of a long period of time we get to the client with

the car and we show it to him and it turns out that by that time he doesn't want

it anymore or maybe you don't need a small car but a very big one or

maybe by the time we deliver the car it's rainy season and we need

a truck, etc. This creation by parts more or less like pieces of

coming up with an agreed plan from the beginning is known as

waterfall where all the requirements were taken and people put themselves to

not work and there was no other setting of the needs or any other questions to the

customers until it was almost being delivered the minimum viable product.

If you look at the bottom, you can see an agile process of

development of the same solution as the from top. However in the bottom part

we meet and what the customer asks for is a means of

transportation. Then we deliver a skateboard and we tell him "you can

move with this". The curious thing here is to see the expression in the customer's face

because since you give him the skateboard you solve part of the

problem. He has to move to the office or wherever and if you

look at it, if you notice in the bottom part of the diagram from day one that you talk

with the client you're already trying to deliver fast value and solve the

problem. Of course, after the first few interactions with the client,

he is going to tell you the skateboards make me tired

andto be honest I need something else

for a longer distance. Is there something like a handlebar

or something to be able to turn around? Then there it results in some kind of

scooter and so you keep improving the solution and the client already

starts to see more value on needs he has.

Then the client tells you there are some potholes in the way and he needs

bigger tires or something. The point is that he needs a

way to pass the bumps as well. So, you go back to your team, develop

something like a bicycle and deliver it to the customer. The customer is

happy because you are already improving. By this time, let's assume we're

in the sixth month after we started the project. By the time

we bring the customer a bike, which is something he can alreadystart using...

On the top part we only have a body that is useless and

well there you see how it evolves after a bike we deliver a motorcycle

and finally it ends up being a car. In this illustration I would have liked that

the car was very different from the above because as it is it does not reflect

exactly what happens in real life. I assure you that the

car that we are going to deliver to the client in the agile methodology will be a lot

more attached to the customer's need that the car that we are going to design in

the top part which was under a contract that maybe happened one or

two years ago and didn't have those adjustments from the feedback with which each interaction

let us know what he needed. Some of the most common

working methodologies are SCRUM, CRYSTAL, XP, Agile UX.

I don't have the updated info but last time I checked there was more than a

70% of the companies that are using agile methodologies are using scrum

so this shows the importance this methodology has and that is why

I used it to name the channel, cause I really like scrum and it's the one I've worked with and

the one that I can share my experiences of. Before finishing the video

let's very quickly mention how scrum works. What are its

pillars and what they're about. However, I'll make an exclusive video

of how to learn scrum and a million things to say about scrum.

Scrum has three main pillars or it's basically about three things.

The first one is the roles we need to carry out scrum. The events, the

ceremonies or meetings, you can call them any way, that are

taking place to be able to develop the methodology and the third pillar are the

artifacts. It sounds a little flamboyant but not it's not more than three elements used.

There are three roles scrum is about mainly.

Product Owner, Scrum Master and Development Team. In very few words,

the Product Owner is in charge of the vision of the

product. To see where the product is going.

He must be in constant communication with stakeholders to understand what

their needs are. He also has to talk a lot with the

final users of the app being developed or app

being improved. He is in charge of transmitting what the product

will be or where the product is going to the development team so that they

can encode. The scrum master is the one in charge of

removing impediments or blockers that keep the

development team from deliver something or advance. The scrum master is also

the one in charge of promoting to the rest of the team and the company

what scrum is and what the methodology is. He knows best

what has to be done in each meeting and

what the responsibility of each member of the team is.

The developers are the ones that make the magic happen. They're the ones

that encode and those that create the product. They own the development

process of the product and encoding it as well as well as the

quality assurance of the code being delivered and its functionality.

We have five main events in scrum. The first one is the sprint. Yes. That sprint

like when you start running and then you stop. The sprint is the period

of time within which the team agrees to deliver part of the

functional code that adds value to stakeholder. The 2nd event is the

sprint planning. In this meeting happens all the planning of the stories or

the work blocks that will be taken to work during the sprint.

I missed saying the sprint may take one week two weeks three weeks or

even a month. The duration of the sprint depends a lot on

volatility or how changeable the project requirements are.

In most teams I've worked with

I've had sprints for two weeks. It seems to me like a good period.

3. The daily scrum or the stand up meeting.

Here, the scrum team gets together

Remember that it is the one that consists of

product owner, developers and scrum master and what is commented is

what they did yesterday what they're doing today or the work plan

and identify possible blockers or possible problems that are

preventing the objective of the sprint. 4.The famous sprint review.

The sprint review in my opinion is the most important meetings because it is

where they present the product that was developed during the period of time

that we had defined which we call sprint as I just mentioned. And here

there are talks with stakeholders, they are shown what was done and they

provide feedback to see if what is being delivered is on the right track or if

it needs to be readjusted. 5. Retrospective sprint.

Here, the team gathers and talk about the good, what worked,

what didn't work, what can be improved

during the sprint. Here, the most important is to get action items

in order to guarantee continuous improvement of the team becoming more productive.

We've talked about the roles, we've talked about the events and now there are the

artifacts. These are three. The first is to have a product backlog that

is nothing but a list of requirements normally sorted by importance

where we will have the list of things we have to

do to be able to develop our product. Now that we have the

product backlog, the second artifact is the backlog of the sprint.

This means, from the list we call backlog we have to

select certain items or certain stories that will help us get to

an objective which is the one we are going to commit during that sprint.

The third artifact is the product increment. That is the tested functional code

to be delivered or to be presented to stakeholders at the spring review

meeting at the end of our sprint. If you want to learn more about

scrum I invite you to see my other videos that I have here on the channel. If you

liked this video please click the like button here below

and leave me some comment with feedback, I'd love to hear what

you have to say and if you want to receive notifications every time a new

video is published, please subscribe to the channel thanks