In this lesson we are going to talk about an agile story. As a story is basically the fundamental or the foundation of Agile as a whole. If you love stories, nothing more than basically a piece of requirement. Regarding the regarding the product, it is the building block of the product backlog. We In this lesson, we're just going to talk about what the story contains what it provides, if you will, in future lessons, we are going to be expanding more on estimating the story and prioritizing the story etc, if you will. So let's get into it.

An agile story provides as the who, what and why. So let's kind of understand, you know what, how it provides these if you will. So this is a format of the Agile story as a type of user Who is going to be using this requirement? This is the who part of it if you will, I want some goal, this is the what what is the requirement? What is the requirement? So that's the The second piece of it.

And then the last piece is so that some reason why do I want this approval? So that's kind of the format off the stone as a user, I want some goal. So that some reason so let's look at an example to kind of understand this better as a student. So who is this requirement for the student? So this is the home part part of the whole female? I want to purchase a parking decal our parking permit, if you know this is the requirement, so that I can drive to school and this is the reason why I want this if you will, so it is for the who is a student The Wat is to purchase the parking decal so that the Why is the student can drive to school.

So that's kind of basically one example if you will now, obviously this is kind of a summary so that you know story just kind of provides a high level summary. So now you you probably the team would need to get some more details than I wanted. So in the there's a comment section in the product backlog where basically you can provide you can collect the you know, screenshots, details about the story, maybe whiteboard pictures, you know, related to the story, etc. Nothing formal, but just kind of enough to provide the people who are actually building the product details about you know, this this story, if you will. So next we're going to look at some guidelines what the story is, needs to be based on if you will score in West guideline Invest because AI stands for independent, the story needs to be independent of each other, on others, it needs to be able to stand by itself negotiable.

So, it doesn't need to be specific contract for features, it can be between the product owner as well as the development fee, it can be negotiated as far as you know, what features this has etc you know the details of it if you know, v is for valuable are also stands for vertical that means basically that other stories can be bought built on the story is for estimable meaning that you're able to provide an approximation, effort, approximation, as it is for small or it needs to be small enough to be able to fit in a single iteration or a single sprint a female, next is testable. That is, it needs to be able to be able to be tested, if you will. So that's that's kind of what in S stands for that's what your story needs to be based on, if you will. Now, as we talked about agile, doesn't focus too much on documentation, but rather it basically focus to get the gist of it, if you will, or the formalities of the documentation, I should say.

So you can build this series on, you know, you can write these stories on index cards, you know, put it on a wall, or you know, there's other tools like in JIRA, or even Excel, you can, you know, so you can use whatever tools in order to get the information if you will. So we're going to see an example next of an agile story that's done on an index card, if you will. So, as you can see, it's it's handwritten, very, you know, informally written, if you will, the same example that we saw earlier as a student I want to purchase parking decal so so that I can drive to school. And then the back of the index cards can have the details for the story. fuel, right? So that's you know, this is just one example if you will, again you can put it on the wall, the Kanban board etc.

As the team builds this if you will, as a product owner business and the team is is questioning to get more details etc and female so this is an index card, you know, you can obviously use, like I said that other tools like JIRA Excel, etc, etc as well. So hope this gives you some information about the story again stories is one of the fundamental building blocks of product backlog as well as you know, hence, for agile as well. So let's make sure that you know, we understand that we are going to be in the next few lessons we are going to be talking more about the story and you know, seeing that you know how we can best estimate a story how we prioritize a story except for a few more