Alright, come back to my sixth class and this is the last class, proudly this will be a little bit shock to the array of course, sorry, Introduction to not good. Welcome to the sixth class of rally. And we know here we'll discuss about you know, so, this is a kind of experimental work that I have not done before, I mean, I have done before, but not in writing. Okay, so there is a jido we choose to do and so, you know, we know this, right, we have this blind track quality. So, we'll go ahead and click on this track and go to this team board. This is a new kind of thing, actually, you know.

So, this is a more of a Kanban process. Let's use some About just can bet you're not sure I can manage. I just know we'll see here pretty quick. So it's still part of a lease. Not sure why. Okay, so in ajayan agile is a methodology.

It's a framework, right? It's a framework, and you have various, you know, it's sub modules or sub modules are modules, modules and you won't have to work in one module. You know, if somebody says like what methodology your company's following, you can say Scrum. However no can man So, but that means they are working in a giant. So desert desert the part of the giant process which you see here is d adaptive software development, DevOps, development and operations. Okay, and our up Rational Unified Process comes from is more famous sense from the US.

So can men can man is also a method it's similar to Scrum. But it uses this kind of oops, I closed them to where I should not push. Let's see if I have that in history or go back to here. Oh, that's good. Okay, so the pan man supposed to be kind of like this, you know, if you see this, this is a traditional way bored, where you have this user stories here. Okay, and then you have this to do process and then in process testing, so the similar way is here, see this?

This is the traditional way of doing this work. You know, you have this bowl and you put this sticky notes and this white On this card, you know, user stories, and, you know, in process, you know, if you move this from being passes. So, you know, this developer starts the work and testers, you know, whenever testing starts in development has to be completed before testing start, so you cannot do testing before the roadmap, so it's not possible. Okay. So here actually, so instead of doing this traditional way, there is an online way of doing it. That's the whole point of this.

Okay? The point of this is the the way you're doing this in the board, I put the sticky notes move into the in progress move it instead of doing all this, you do here in online. How cool is that? Okay. So, the process is similar. I will be showing example here.

But unfortunately, this is all stuck here actually. So if I let's say, I mean, the way the JIRA is done is really good here, it's a little bit complex. But let's see here I can use instead of using the speaker you could use this right from here. So let's say if I will take an example here this is a defined process. And if I can drag it here and put it here, okay, this is in process that means my defect is in process. So this is supposed to do process and are putting in so once it's in process, it's supposed to be in always in ready.

So this is ready button and this is blocked. This will block here. Block means you're totally blocked. Okay? You know, you cannot move further. You know, from that Okay, so once you, you know, put in in progress, it's always supposed to be in Ready?

Okay? We cannot do that. If it is not ready then I mean, that's an option actually people normally don't use it, it's up to them. But it's, it's, it's an option. So, once it's done, you go ahead and progress to completed. That's when your testing is completed.

Right? Once your testing is completed, you drag that's a similar way what you do here in a giant process. So in a giant This is we're talking about Canvas process. So this is how the canvas prosumer cameras simple than Scrum. Okay, then introduce the new creating bolts. So that's the reason I want to swat it a given ID on this.

So it Stop doing that on the user story you can do this right from here okay. This needs lot of more development in this sea desert guy these guys are in beta state that means that do not have work okay, and once it's completed see the point is okay firstly this defect let's take the same example as the defect will take example as defendants in defined process and it's not ready yet three distinct already change it to back to the place okay. So this is a defect in define process and once you of course we should be moved into in progress and this is not what should change that one but I think some bunk by this okay so you're in progress You know once the defect is in progress, because the tester you're supposed to move into will progress. And let's say from the defect, and you and the developer fix the defect, and you will put in incomplete Okay, that means it is completed.

And that's the reason distinct from green color to have the thing gone off, right? In this, I don't believe that this is something to be accepted, there's nothing to accept it. But this defects are nothing to get accepted. And the only thing that is accepted is user stories. So let's say you have this user story right. This, of course, will go into in progress.

Completed completed means see once a user story goes in progress, that means the development should work. Okay, the roadmap should work and after that the testing has to be completed. And then once it's completed then this user story No, let's let's do it here. Did he go already? Oops. Thank you.

Okay, here Here it is section. So I want to move it up. So in this and I put it in red, sorry, green, so that it is in progress. Okay. And what happens here is your the globe we know, development testing should supposed to be completed for this user story. And this is a job of a product owner.

In a gel you call the product owner in waterfall you call it is as a business analyst. Right? And once you've done that, you want to move into law Matthew, Matthew four Product Owner moves that into complete Aeschylus really I'm surprised that cannot move that into completed process. That's very interesting. Um, but what? Okay, so this is what happens while it's not moving into here.

Now what I can assume this one why it's not moving because there are defects which are not close. So if there are defects which are not closed you cannot say is completed so, let's find out user story 149 Let's go here to defects. You see here the state is open. So that was my Hunter. That was my you know That was my sense that once you know if you have this open thing, you cannot actually technically move that into concrete estate is because you cannot say the requirement you cannot say the requirement is completed until the defects is fixed. So that makes sense for me.

So, that's the reason no, it was not moving further, okay. We go back here. No, this is no point because it doesn't make sense. Fair enough. Okay. The defect can be moved because the defect is you know, has nothing to do once in defects the speeds that means if this move, if it didn't move, it gets fixed.

Okay. So, that was a really good example like non moving and even this not supposed to move. It did. Because blog, right? But okay, so, so this was a little bit complex here, we don't want to go into detail of this one The reason because this is all too much of things, you know 94 this is not really properly organized the reason because this has to be done at the user story level, they have divided into project level. Let's say if I go to a different project, it shows less number, I hope.

Yeah, see this. This team would they have done based on the project level, the project level, there will be lot of user stories, a lot of child user stories and a lot of things Okay, and so that's the reason this is not appropriate completely for the reason you have to submit feedback. You know, you can go ahead and click on feedback and see, you know, what you can improve if you really extremely satisfied and say that this should be classified as the user story level, not as the project level. If you're using a project level one project can have the number of user stories. Okay. 36 zero 15.

Look at this. I mean, do those 265 Hollywood. Now, if they're like, people who are working in the beams nailing let's say they're in one project, it can be nice Giant Remember, this is not a waterfall methodology. Now when you're working in a giant if it's a big project, you divide into teams, team one, team two, team three, so you call it a scrum, okay? Scrum, one Scrum to Scrum, three Scrum, for Scrum, and so on. So when you divide this user story gets along.

So let's say for example, one steam has 10 user story, let's say 10 times 10 times 100. Right? That's the reason you have this many. Now, this is not user story. Now this has defects. This has user stories is that test cases?

The past didn't include tasks here. Good. Otherwise detailed mapping much more complex. We don't want that. So the whole point of me is using this is for me, it's, it's, it's it's kind of tomorrow. Have, it's not supposed to be divided in project level supposed to be divided into at least as a user story level, but it's okay.

If you have a project at school 65. And if you know what you're doing, that's fine. I mean, I'm not worried about it, but there are again, law wants to you have to handle all this blah, blah, blah. Okay, so all those things. So this is kind of complex complexity. This is what we'll see here in this graph process.

On this graph. You have cumulative flow, cycle time and throughput. Okay, and then you have the Sen option. R. Oh, okay. This is a read only option because you're not Remember I have to change it from administrator way. So, okay, so that's the thing so I mean this is just an introduction 14 board this was starting new.

So that's the reason I'm giving an option that So, pretty much we have completed most of things right maybe not all thing we have completed on release status we do. So, yeah, you can go ahead and see this release task status. This also this is similar to so there are added new options actually. This was not there before. Okay, so in this release task, right. So what you do here is you have this options, user stories, you know, defects, a lot of things is clogged up.

So you can change the options here, you can edit it, you can copy it, you can delete it, okay, fine. You can have this sub task, you know, inline new task. So, you know, I don't worry about this, you know of this you can also go into past working already on bugs. So yeah, you could have you have this option of news of free that the way I want to create an user story I will do from here, go to this plan option, and oh, something is not working. So I think we build some muscle. Okay, so Oh, it's not working.

Okay, good. So, yeah, we did something, we screwed up something. So the perfect so, you know, I always like to go here because it's easy and easy to work with them. It's easy and you know, you can go ahead and click on this and you can no view this. You have this option of having this pause right here. defect, you know, you can use this defect option here.

And probably my internet is very slow out there. This might be the case Yeah, no, something's happening. Okay. And so that's pretty much about granny. I mean, I agree I didn't explain all of this. I know that, uh, but you since I'm giving you access, you can go ahead and view this young children option Do we know that children option in this because if you have an you can go to this and find out the children option see here so that's how actually it works.

So um, so yeah, there is one more or one more thing I could tell you, let's say if you accidentally deleted something. Okay, let me give you some hint on this. Let's say you accidentally deleted something in this center Do you have this access, go to this Recycle Bin like you have this Recycle Bin in the windows, you have this recycle, go ahead and click on that. And if you know the user story or the task number you want to retrieve, go ahead and click on this and go ahead and restore it. So he gets a stroke but you have to know which project is when you have to know all those four, t 310. You have to know which project it is and where it is going on.

So okay, so you weren't you can go that one. So that is pretty much you can make use of it. So that's pretty much about brandy. I'll go ahead and stop this. Since I didn't explain each and everything you need to create a story but I didn't go very in detail and I already explained the admin part. The admin part is also there.

We have talked about his project So hi, yo, fellas, save this as in production in production and rally. Because I didn't cover everything I agree. Because No, I'm just six classes is not enough. Probably need more detailed information are now the single team planning session. This is new actually. This was not the year before.

So the planning session in Reno releases, how do you create release. But of course, if you have access to this, you might do it. If you don't have access, you cannot do it. So normally you don't have access if you are a tester, okay, if you're a scrum master, you can do that. If you're a developer, you can create a release by yourself. You need to check with your team Okay, If you're a tester, this is what I know you get this you display information what you couldn't have.

But if you're a product owner, then yeah, of course product owner can create a release typically. Okay? And nevertheless, even if you have a few didn't find this useful, you can go ahead click here and go to the help. Or maybe you can contact support Do you want to do that? You can contact me before contacting support. You know, most of things are there here.

But, you know, most of this, you know, complete this one. Okay. Most of time will be on the user stories, creating user stories and creating test cases executing your test cases, opening defects and reporting reports. Okay. That's all pretty much you will be doing that. Of course, it depends.

Sub project to project level I don't say that the only thing since we have this iteration part where I only showed you an example of manual, right remember, there is automation Do you can do automation but the thing is, that's where the admissions come into picture. You're done for Safari you have to do for comb you have to do for Firefox and so on and so forth. So, I will continue to explore more on that if you find useful since I'm giving you access, okay, you will be having access for this. So if you don't really you know, if you think I didn't give you enough information, you can go ahead and use it, use it. Use it only for what you want to use for don't misuse it. Okay?

This is not to misuse it. I don't want it to be misused because lot of people from all over What in the world? I don't know, I don't like people from Bulgaria or Google and and so on the people who will be using it. Okay. And so don't misuse it, lot of people will be using it. And I know you have access for this.

So, you know, I hope you like this video. And with this arena, are you in this class? Okay. And that's pretty much I remember any important topics that need to be covered when you're in a project actually. That's pretty much But of course, there are a lot of user stories, you can go ahead and view this. You know, and, yeah, I mean, that's what I remember.

And if you want to know more, go ahead, use it and just don't delete anything. We don't want to do any deletion part. Okay, if you don't, if you did something wrong, you can just ignore it. create one more. So Kay, don't care about don't delete anything. If you put somebody knows some people deleted a lot of things, so I stated on giving access, but since I didn't explain, I know, it's unfair that I didn't explain to you everything in this rally.

But that's the reason I'm giving you access. I hope you will find it useful. And I hope you know you found my tutorial useful. So I'll be just putting as an introduction introductory class because a lot of things you know, I didn't explain for you. So, you know, with this I closed this class is pretty much about rally, and look, thanks for watching and good luck.