So tomorrow we can do like real vision. So we'll be explaining more to have explained so just one hour I'm not tied to cover water most important aspect of our know for job actually nobody's done actually know to, to how to open a defects that's what we need right I mean not necessary but you know, the one of the most important aspect which is to be you know, which you will be doing other than that, you know, theoretical play you can you know, either eat by yourself or you know, you can know by you know, interacting with each other and stuff. But other than that we have completed most turn to I'll be explaining today so completely okay, so I forgot to explain this RTM requirement traceability matrix. Yeah, let me know if I've missed anything. So this is Like your syllabus, what actually I am, I know what I have learned from it and what I'm actually trying to explain.

If you know more, no, you want me to explain more like, you know, I can do that just let me know what what are the other competitors to make sure like they have to come cover in time. So I'd also make no make sure that you know, we will cover that on. So other than that, I think we are good. So tomorrow a quick revision, Western or in case someone has missed my classes and you know, don't want to take classes or just when you want to have one class. You can just take Okay, so let's go to so all these documentaries or whatever documents is there, right? So what I'm trying to explain is everything in is there in Google Drive for everyone.

I hope everyone has access to the Google Drive. Don't have request me You can, you know, you can, can just email me or you know, call me. I'm not available. You can email me. Okay? Mostly email, email and sender.

Do the access if it is Gmail is to give the URL click and access. Okay. So, AJ, so what's an API today Okay, so Watson Ah, I don't even I treat you an incremental process. Okay. So it can process it. No, it's the we have learned about agency in a software development cycle and then we have learned about waterfall model, you know, just like just one way only one way waterfall is a one way if you're stuck somewhere start from scratch.

But that's not what we want, right? We don't get stuck I'm going to fix that. We don't go out in orange start climbing again requirements and get started things for doing nothing. So that's a waterfall. And then we we talked about various methodologies like no spiral. And it wanted this and disadvantages are all those ways in which AI is like, you know, a Chinese company.

Which is new, okay. So there is always development in Asia. So there are so many developments going on in the agenda they keep on coming with new new, new new components and, you know, various modules into AI. Okay, so let's see. Let's start with rules, okay, what are the rules and who gets to you know, start a dialogue with terminology. So Scrum teams, so teams in Agile is in team, right?

Because the reason right? If you have big projects, if you're big projects, huge projects, you cannot do one. One team will not enough you divide the work so you're always in a giant divide. You cannot do everything in one shot. So that's not buddy waterfall, you do that, you know, whatever you do one shot one big project. Much one year one year project keep on going nobody will know nobody cares.

But imagine it's not that doesn't work that way right? In a judge you need to know you need to divide the work because you need to be you know if it's one year then you say no six months we are one year product more due in six months. We don't want to waste money your company don't want to waste money on irrelevant tasks. Okay? We won't take care of our quality right? And AJ quality gets screwed up big time.

Okay, but in waterfall the quality is good. So we have learned right? So but no company wants to know doesn't care about the quality now they want to care about the money how much money they're spending, they want to spend much money so they want to move the edge and so now you have to divide the work you cannot do just like that you know you need to do it. So that teams okay scrum team one scrum team Two's Company Three's Company comm team for so on and so forth and on making the world different today. So that So, that's the scrum team Scrum. What is this comes from is like something I try to do an incremental process.

Okay? They're like, you know, teams probably the team is called Scrum. Okay. Okay, so you have lead, right? Like, okay, that's not that different that surely concept is gone, but Okay, so somebody asked, right, so we're, whether the ETL clusters comes in this Agile process. I'm gonna be going to explain that actually.

So, testers will be no part of the team. Okay, testers will be the part of the team. So this is like methodology data metrology. It's a process. It's a process. It's kinda like a software notice to the word explain that to That's it done.

No, this is a management perspective. So more of a management perspective, like, you know, how many team members are there, you know, they're there to see how the work is going on, you know, usually it's more of a management but between the management perspective, like, you know, testers, developers, Java developers, web developers, HTML developer, whatever, you know, all developers, architects, web architects, and all those people coming to this team, they might be one team or another team or any part of the team. They're like teams, okay, so they will be a part of the team. So even the tester will be a part of the team. Okay. So scrum team who's counting consists of one product owner Scrum Master and development team, okay, who is the product owner product owner is business analyst where we call him waterfall business analyst right ba ba we will call ba ba.

So that is product or terminology is different, same guy. No, not at all. is not something new. No. Nobody needed something new. Same same person business analyst is called product owner in a row somebody that product owner okay conclusion just a business analyst Scrum Master Scrum Master is project manager.

Okay whoever you know in whatever methodology project manager recall there's nothing called scrum master in waterfall, right? Nobody you know knows what is called master but in a giant, you know makaras project manager that project manager forgets the name Scrum Master again, you know, we have again, different distinct skates more and more developed and more and more sophisticated. I've seen like, you know, in Scrum directed for nothing like that, but because he was that guy is working in markets, right? The guy was actually handling world Scrum masters actually. He was a boss of all Scrum Master. That guy was eckstrom.

Director kind of. Okay, so yeah, there's nothing like that. I mean, there's officially There is no name and there are just you know, since all star muscle reporting them, so that is like scamming or something. Okay, so Okay, so Scrum Master and development team, okay. And then so Okay, so let's go product owner so this is you know, you know product owner is responsible for maintaining product backlogs. Okay, we'll come to that okay product backlogs and production Scrum Master because you notice who actually is responsible for the scrum process.

So okay, who exactly is grandma's see as my personal experience scammer, sir I'd say he or she is a bridge between the developers and testers Okay. Why because if you get any issues so see desert will come up with all these kind of issues right much more issues. Big Issue or complex issue or something where now you go to a president developer saying that, Hey, I got this issue either he doesn't care. It's working fine. magista Why are you bothering working? Somebody?

You know, it's an issue in Asia issue. If that goes into production, you know, you will be get caught, you know, and then next to your manager when you know, behind the dollar, the team members to say, What's up with this defect? Why went to the production, right was not tested. So you know, it's an issue. Now, developer don't want to fix it, right? He doesn't care.

So you know, nobody cares, right? Nobody cares about your work. You have to care about your work. That's very important, right? Nobody cares about anyone. So now you know that's an issue and you found out an issue but the lumber doesn't get but then in that case, you need to approach the scrum master saying that okay.

Now you have to give an explanation to commercial saying that, hey, this is the issue. If this goes into production, know what kind of epics does it happen to the production team or will not get caught Seamus gets affected with that and all those kinds of issues. So, so is this, like, you know, what we have to do is durable? Is it not a business critical issue? Or is it? No, it's not an issue at this point of time or what is it all about?

Okay. So you know, then, you know, calculus camasta day you know, he has crashed the issue. Okay. Yeah, it's an issue. Yeah, of course, it's an issue. Take me to the permanent effect and we check with that.

Okay. So that's how so as my personal experience you can master is a bridge between the developer thanks and testers is supposed to be see when you go into project right. Ada is still people don't know what to do the scrum master he whenever he has to escalate the issue. So Stacy will say why you are giving issues to commercial commercial don't do anything then watch the use of commercial right The year the division says there's a problem making sure everything is correct and maximizing the benefit, then you get your question from the boss. So why are you giving issues to the Scrum Master, you have to give issues to me no manager doesn't care about issues is care only about firing and hiring people. That's it.

Don't worry about anything else. So then you have to say like, you know, Scrum Master is a person who will be making sure that, you know, that issue is exists or not, they don't agree with you. So if you are, tell them, this is what it created, then, you know, the next time they will not even, you know, ask any question. Okay. So people don't know, because, you know, in Agile, people are still developing and they don't know motion things they don't know. They don't know.

Get familiar with the terminology. So that's how that's how they will know. Okay, so that's commercial. So we know development development team, you know, we have so many development Look at your web developer, Java developer can learn JavaScript developers, radial developers, all those things. So all these two don't have to be everything in one team you can request from other t. c, for example. We can have web UI yet.

We can have a team of one web developer. Okay, one Java developer. And, okay, let's say two Java developer, one web developer one, you know, JavaScript developer, awesome. Okay. And one tester, okay. So now that the okay one Scrum Master, okay.

So that that constitutes it, but now you are doing ETL process and you are stuck with these. Two, what you can do is like, you know, you might not have immediate developer ETL developer, that team, so in that case, you know, talk to some contact person next promotion and check with the other team who is working actually in that issue. Okay, so there might be easier. issue that might be so that that guy might be in a different team than you committed like that need to talk to some other team that okay. The other team is not actually in our team. So, you know, you need to communicate with them and make fixations.

Okay, so not everything will be readily available. That's what I mean. Not everything will be readily available, you need to find out okay, that's your job. That's what your job is to find out and make sure your work is completed, okay. You need to make sure you all the defects has been fixed. Okay, then we have sprint burndown chart.

Okay, getting burndown chart, how does it look like? So let's see an example. Okay, so this is a no burndown chart. So this is prepared by the scrum master you This graph is plotted between the days and the remaining hours. Okay, these many days are left and so ideally the green color is the exact know how the work should be done in the green color line Can you see that there is ideal burndown Okay, so that's how the no that's how that should be. But okay, of course not always ideal things don't work, right?

We were like, you know, you shoot somebody, you know, it took more time to fix an issue or there was some issue with the development some guy left a project or something from the end that case the best thing was ups and downs. So that's how, you know those are ups and downs in this ideally, it should be like a green light, no, always Greenland, but that doesn't happen, which never happens. Okay? Even if it happens only one two times that changes by like two times. Okay, so this is like, you know, sample burndown chart and then you have Okay then you have various other okay release burndown product BAM burndown okay. So these are the chart.

So let's come up with okay so there are other terms which will which are new, okay. I have not heard of this, we can go through it and you know understand this so there is no traceability task or task we know. Okay so let's go to sprint. Okay, what is sprint? sprint? is a tight it's a nice it's a tight okay.

So in which normally Okay, so let's say you are a project Okay, look we are working on some project and it's divided okay. chuggin divided into some part. Now that Did pretty big long dividing Sprint's with sprint one sprint to sprint three let's say sprint one is one month project so we don't say product anymore sprint no one month papes okay every you know month so we have four Sprint's because it's divided into four times the four Sprint's it ended up completing end into for four months okay for sprint so that's our sprint it's a time period which are time taken to complete that right you can set module to no better technical point of view you can sell print. So you can understand that the module but you need to be professional right in addition you can you have to know and see talk as a sprint so it says print module is like you know a little bit different because that is more like in a software level.

This is little bit different than that. Okay, then you have product backlog, let's talk about the product backlog okay. So we have so many we have so many here features right like okay we have product backlog so that means okay so this is like you know huge okay one is like ocean itself okay? So just like most deadly comes from the CFO. Okay, this is this much product backlog and they let's say you have like, one product backlog consists of like, I don't know, let's take for for the simplification will take like 50 applications, so 50% Patients that means 534 20 that means 200 applications you need to test Okay. Now you know we have figured out what is what Okay, this is management perspective, we know a technical point of view.

Now we understood like, you need to test under luck, okay, both develop and test 200 applications. So now we only done one right we took so much time to know, just to test one application to know but you need to test 200 applications How would you do that? Now, what they do now that divide the work the divided So, that's a no product backlog. So, you have one product backlog, let's say one product backlog. Okay 20 applications, let's say in one product backlog to 20 applications that you know, let's take in is a simplification question 20 applications need to be developed test it. Now that product backlog 20 application is still a great number no euro you cannot go and just test 20 application just like that right?

You know that takes time that takes time that takes resources that takes no formal development. It might be Java development, immediate development, you know, well, too much everything. Okay, so now again the divide into sprint backlog so let's say that noted on the lesson 20 Okay, 20 applications, okay. Now you need some time that is divided into four months, okay, now 20 additional this testing is good now. Okay, now we figure it out. Now you have 200 application altogether, but we don't care about all 200 let's worry about 20 application.

Okay. Now 20 million should be completed in four months just like you know sprint backlog. So here there should pull backs right 1234. Now, four months, you have time to complete our 20 application. Now, each Okay, no whoever we can design like, you know, by four months, you can have like, okay, you will not bring only the one thing only this thing might be so many things we just talked about one trial remedy plenty of Alabama. We're just about a simplification process now I'm trying to understand, okay.

And then for like, you know, you have for that is four months, let's take four months, three or four months, you take 20 and then you each print so this is about me, each printer takes 30 days and then you deliver to, so this is how, like, you know, this is how the Agile works. Okay? And then let's go to technical terms. Okay, so here's the thing the product backlog competitors requirements so requirements right so that's the requirement product backlog is a requirement okay. So we know requirement right what is the requirement right your requirement that it should be completed to that the product backlog okay. So you can check it out this one in waterfall you call it the requirement and in in Agile corridas product backlog, okay, you can take it that okay.

And what does it consist of? Like a no we know right features bug fixes non functional requirements or defects you know, whatever you see sometimes right that defects will get no defects. If they don't fix it, that becomes a requirement. Now you have to know that's a big project that you're going to be no user story and you know, you need to work on that. Okay. So that is product backlog, linear spring blacktop open seem like you know how much taken time to next sprint?

Okay so that is sprint backlog okay so now you have planning sprint planning okay there's also grooming sessions presuming okay that's not know officially is doing is this but as pre planned so what are we doing the sprint planning in the sprint planning so name it's already planned What do you plan how many user stories we need to put into one sprint? We know what is the sprint sprint is a like 30 days of time you have 30 days of course you take weekend Okay, so sprint planning is like you know you will need to decide how many user stories we are going to implement in this sprint from That's what No, that's what that's what it means. Okay? And you and who are know who are invited. So most of the team is invited except managers unless manager is technical. Okay?

So, everyone Scrum Master Scrum Master, who's that? Okay is Scrum directors and of course they will not they will use them. Okay, Scrum Master. And then developers testers don't guys are very important they have to be their vision must okay you cannot miss sprint planning you may miss them you don't know anything whole project going on. Okay. And then we're in technical okay Product Owner of course product owner should be there if any issues with the guy has to say to the consistent No, that meeting last for like, you know, three to four hours.

Why? Because all that so let's say you have 10 user stories. Okay, if you're walking into two separate teams, okay, what was one, two or but if you're working with Two Three things when you're able to figure it out what you are trying to do and two, three things all in chaos, then you know, like three to four hours trying to figure it out what we have to do. Okay, so that's what this planning sprint planning is like one more thing agonist grooming where you actually that's the same thing. Similar thing then planning what do you do is like no accommodate, no try to figure it out what are the in the backlog? How many user stories we need to know put in the backlog?

So this backlog is again you know, that's a high level term right? Then you have actually again user story that is more specific, you're going a little bit more specifically map locking like not too much backdrop for one background, everything is better okay. requirements, what requirements only company has its own requirements, what are you talking about? So that is like more about high level user stories you company specific to that, okay, which user stories related to which, which is backlog. So when you have the user stories, Okay, so it's being specific. Even user story is a requirement product backlog is also a requirement.

Product. backlog is a high level term. You cannot you don't use every time just to explain the amount you can do that. But you will be more specific the user story, which user story and what is a story that is more specific as a requirement. That's also called a requirement, but it's being specific than being more high level. Okay.

So you do sprint planning and spring grooming, okay. Now you have daily Scrum. So, daily Scrum is called stand up meeting. So how does it know it looks like? So you have like, you know everyone in the team, I call the tester Scrum Master and who is a scrum master here in the holding but Scrum Master developers, testers Norlander And the testers will be the tip it's like no this is how to be like okay. So there will be like enough people.

So, what do we do in this come over what do you do in that daily Scrum? Okay to reach a daily 15 minutes you normally it is like 15 minutes. So, what we talked about, we talked about what you have done today what you know what you like, what have you done yesterday, what are you doing today and what are you going to do tomorrow? So, these three things are important. Okay, this is what it is CMT. Okay, so what have you done yesterday?

What are you doing today and what are you actually going to do tomorrow to this day thing, and also you could discuss any impediments. So this is the technical term an impediment impediment says. You can say is a defect not exactly a defect, but it can you know, since they want to eliminate those defects and optics of the thing implement that which what is stopping you to do your job that means, there might be issues from the other team that know that is blocking you are they can be issues from you know, your team itself know, if the development is not done or you know, coordination is not done something right. So, that's called implement, you can date as a defect, okay. But not exactly a defect. Okay.

Similar to defect. Because typically, like documented work, right? Video candidate, yeah, when you look at them for employment, they don't have any document. Okay, what do you implement your demand number? No, nobody says that. Right.

So that's our choice like you know, not in a document in prospective employment is more often what is stopping you to do the work? Okay, so these four things will be discussed in the committee which our stand up meeting. What have you done yesterday? What are you doing today? And what are you going to do tomorrow? And what are the impediments that is stopping you to do your job?

Okay, that is dead is that that's what you discuss in this committee. Okay, always. And this will be daily 15 minutes about sea trip in 15 minutes. He should not go no more than beyond and then you're doing something wrong. If it goes more than like, you know, okay, can go 30 minutes, but I have personally never seen a scrum lashing for one hour. So that's not doing good in it.

You're wasting time. You cannot waste every day, one hour just to force committee. Those 15 minutes good, sharp colors, be specific to the water issue and know cut up the tissue and we can coordinate that later whenever you're working. Okay. today that is Scrum. And then Then you have Sprint Retrospective okay.

So in this print retrospective right what do we do so, this is the end of the sprint. So, once you are reaching to the end of the sprint you know you discuss about what have you know what good was there in this sprint know what didn't go well in the sprint and what we can improve about that. It is very important thing what what good it was what not good and how can we improve on this? How to make it good. Okay. Before everything there will be something that will be something of the norm.

Requirements do come up in timely manner or no, the developer is no more at our time to pick that issue because the issue was something you know, related to the other team and another team guy is not there and nobody was responding to that some issue or you know, some issue comes up. So you need to talk about in the Sprint Retrospective. Okay, so that is Sprint Retrospective. So in every sprint, we'll be having, what went good, what didn't go good, and what? What needs to be improved. Okay, three important things.

And then you have that so that's all about, okay. So, let's see, okay, how will that feel you have user stories. So let's say you have the user story, and this is a user So, what are the requirements? Okay? requirement but that's a more high level term, we don't know much in high level. So this isn't like traditional method of doing the very traditional storage.

So personally I don't know I mean, I don't like to say too much because like you're working in the Stone Age but in rally when you see the rally rate that has although maybe daddy's gone Okay, let's not worry about dinner. Okay. So in the right when you go into that, okay, we will be having all of the documented so it will be Everything will be done. Online. So all this will not be like this similar way. But okay, this is more of a traditional method of doing it.

Okay, so what do you have? This is a user story. So let's say you have a user stories 10 user stories, okay? Then you have the developers working on it. So you cannot start. No, you cannot start testing until the development is completed, right?

You can only start testing once the development is completed. So yeah, there are sticky notes, there will be using sticky notes. Are there various colors, red, blue, alone, all this stuff. So let's say once the development is completed, so I know that we'll have time right so let's say one user story to this owner decided into the sprint planning session. How much time will one user story take, let's say developer says five. Know how much why we take $5 million fat some reason explaining that No, no to take five because we need to coordinate with other teams, this is no different issue altogether.

So no. So that includes testing and development. So the developer will have a plan on this, because they know what's going on. Right. So they know that the developers they're developing this as a tester will not be much more mature, knowledgeable about the applications are knowledgeable about what's going on. Okay, moving forward, no one get more into that you will be knowing even as good as developer but to start with no numbers, we'll be having more knowledge than that because they will be developing the applications and what are they they know what are the issues, okay.

So, so there will be saying like, fight, okay, so somebody has to support that right Wi Fi. Now this technical No, the technical guy will say no, no, this is because fine, because, like so many issues. Okay, so three days for development, two days for testing. So once they are done, right, so three days, they'll put like three to three internets. And then strike and then one month one day is when it that remove that three and put in it and so on. Okay?

And then once the development is done then you start testing okay two days testing so that's what the columns are right here the user stories to do for this next time how much time it's doing in progress. So in progress okay in progress is like, you know, how much the developer and how much testers are doing. Okay. And the how much Okay, so that is like, you know, what is the project? No, oh, yeah, proceeding and testing, economic testing and misprinted. So that is completely different.

And once the sprint ends so, the Scrum Master, supposed to be bed, Sprint burndown jack right. Bala technology so we are completed so this table post was on the you know, traditional way I'm saying about traditional way now i don't think everyone is thinking everyone has become online so everyone does it on purpose Okay, so but we'll be posting one thing that okay this is an everyone looks at it Okay, this is how it's going. So that's right. Okay. And then so gyms agile is pretty much new new incense like of course came in more than eight years but there still need to improve a lot because in a game you need to be quick everything because they are Bass Hope everyone knows what it means right? development does some work, right?

Okay, it does in the development environment. And he submits that. Okay, that code, okay, whatever the code, he has logged in, he submits that code and No. puts into that for a minute, but they have some kind of mini waiting, let's take an immediate exit. They're like mini waiting, and the good checks in these checks in actually the proper ballistics. He checks in the code, okay.

And then once he checks in the code, it goes to the middle value and those builds the process, the base builds incense, that code from the development goes into the testing environment. Okay. So that's how fast the question goes to the developer to know they make sure that it's working in development. Okay, then let's move to the testing room and then let's move into the production environment. So there are to move that code into destined moment there are bits, that means, okay that means let's say let's say there they will do that job so it's kind of work right so somebody else some other team will be working on that. So let's enter w four bills in a day.

That means 9am and No. pm 3pm 4pm Okay, let's say 9am 9am does one build well pm day one movie 2pm and 4pm Okay, so now whenever you find an issue, you need to fix it right away like this right whenever you found an issue and it should be fixed right away. So now developer Hey, this is an issue but why does the developer do is writing a book Okay, so today is a bit of a you know, checking in my court the exempt so you will able to test it after 4pm Since you're walking at festival o'clock two o'clock with a bill but I know I'm I have to work on that so I cannot no go ahead and work on that it takes some time. So double checking the code after 2pm so that goes into 4pm now when the 4pm build is ready now you do start your test so that's how like one day you're actually trying to fix that issue one day that's it no you're not no more you know waiting for days together to distribution issue in these some of these cases right?

They don't even want to open a defect. They say no, no, just talk to the apprentice issue we don't want any more defects and some companies are also doing that they're not opening defects okay and then so that selection of basically a base if you know base so that in a gender using leather pretty fast Okay, middle You want to fix that as soon as possible okay. So, any questions in this just check with one document we just refer that any questions a terminology you want to know see these terminologies right? This is something okay you can go ahead and read okay. This might be their interpret might not be there okay. Okay task task is done we have seen these tasks right in rally we have created tasks, right.

So that is you know that kind of thing you can say task is like a user story you can it's not exactly user story, but you know, you can take it as whenever you What are you working on right now? You can say okay, I'm working on three shirts. Okay. So that but to be specific task now you can learn rally sentence since I showed you right how do you create the task so we can create a task. Okay. Okay, any questions in this?

Okay, so let's go to this document there are many methods for identity Okay, Scrum Extreme Programming adaptive software diviner. Okay, so meeting sort of your dynamic system. So are more involved on the scrum. So there's a scrum team right. So that is more famous than all these extreme programming okay there might be some, you know, be working on to be similar on this. But the concept would be similar unless you know the concept for that will be similar writing on you will be working on the Scrum and below you'll be doing Extreme Programming.

So, what is in Scrum for years when they have given before indication Scrum is an agile lightweight process. It's also an NPI iterative and incremental process. So it's also an iterative and incremental process. So this team or whatever today, in a giant right major, does all management perspective. Only thing is beginning to understand. You You may not understand what I'm seeing you think because you're not a software software is easy.

Distributors often as I will show you, the technical view, will show you that rocker. Okay, this is how it looks like. Okay, so that's easy. But this AJ is a process. So this is not like something to show this is something to work on it. You know, you need to work on that.

Because this is more from a management perspective, not a technical point of view. technical point of view is good, no, it's easy. Okay. Okay, we use but this is a complete Agile process, right? It's a management perspective. Yeah, so I read you is like no sight reading is like, you know, it's more iterations right one after the other, you will be doing one after the other one after this one.

Okay, and implemented incrementally making a coupon increasing. Okay, so that's like, you know, combination. The Botox, like I told you, and incremental. Okay, let's check it out. I'm not familiar with the exact definition of that. Yeah, it's a process, right?

So I introduced like, no, the iterations, like you have one iteration to iteration So, so like, let's say, you know, when you are running something and say you're running some scripts, okay, so that's like, you know, goals one after this, you know, automatically automatically goes to the another, another script again, it automatically so that iteration, increment or Miss, it's increasing, always increasing process. That is it when implemented. Like a loop. It is like a loop, your proof you're doing, but that loop is incremental. Okay. And this is like, you know, advantages.

So but, you know, personally, I don't like a giant because everything he why the reason because managers wants to know the boss will always want to do the job right now. It's not even right now right now right now. So you need to know fix that issue as soon as possible. They don't want to issues. See, as a boss No, see, they want you to work, but they don't want the issues. But if you always can take out issues, how can the How is it possible, right?

Not bad. So, but once the issues are open, they want you to fix right away. So that's not possible, right? It takes time. So in EDL, it's much more harder to do bigger. Why?

Because Because there's like so many people are involved in ETL okay ETL no you cannot just because there is a data loading and the data mismatch then you have to work with the data team and if it is some other issue then the architecture has to fix that okay. Some architecture defect, no an organization Okay, how are they possible? Then the document effect okay the document against Scrum Master has to work on that again I'm sorry, Product Owner product owner has to work or no he's not interested in architecture has to go through all this too many things are going on right. So it becomes actually hard to the to fix that issues. Quick, it will take time. Okay.

So that's the reason in NHL is ETL process will get a bit slow, but still works. Okay. You can still you know, you can make it forcefully to work Monday then we This is how what explained right now what are the functionalities of the scrum? The reason I explained on the scrum master see this is your main job is to remove impediments to make sure you know whenever you go to the sea you see your boss always want to argue with you right? So is you know, whatever you want to do see always be prepared for questions and answer them professionally. Always answer the question professionally and they want to know make sure to do or don't want to know they don't know some of the things you see only person will be knowing more knowledgeable is you not in anyone not my a basketball don't do anything.

All only knows to. Are you doing work not at all worried about even if you are doing what they want to see, okay, you're not being dissuaded. So they want to question you. Okay, so Okay. Why are you like you see, I got a question from When I was a teenager, I got a question. Why are you like no submitting defects to Scrum Master?

I'm like, So who am I supposed to submit to go? Look, I don't even bother about it. Okay, so then I know, my boss are meeting, okay, why are you submitting? So I then I told him that, okay, as my experience of Scrum Master job is to remove, you know, there's a bridge between the developers and testers because not all defects, you know, are understandable by the developers. Okay? Because from Australia, they're much more experienced and he is supposed to do the development work and then used to be, you know, that portion when it comes, okay.

So they know more about testing and development. So that's the reason you know, you we used to get the Scrum Master, because this is no, I'm getting this issue. But developer is not agreeing with that. I want to escalate that issue to some master saying that, hey, this is the issue. And no, this man is to be fixed. So that's what it is the right main job is to remove the debate concerning impediments.

That you have to remember that, okay, so we should remove that. And even if the walls are you know, we'll see my was also argued on that No, no. Scrum Master is not. No. He's not. He's not responsible for no team pretty much.

No, you can go ahead and show them you know. So here's a thing. So they never ask you question again. Okay. Okay, so scrum team, okay. So this is what we read from things commonly like five to 10 people cross functional.

And I told you, right, so everyone, that is QA programmers, UI designers, etc, architectures and so on so forth, whoever they want to be. Okay this is not supposed to be you know members could be a full time not necessary to be self organizing Not really. Because in AGI see idle everyone has to follow some procedures right? But that doesn't happen in ages since it is new everyone is learning, right. So it's not actually because of the Sprint Retrospective right you can say the team is self organizing, but everything should be in proper way then only know you can say that. Remember should continually the product owner we talk about the product owner, he is a business analyst.

Okay. And the process, okay, we talk about this sprint planning sprint daily Scrum sprint review meeting and then we have to totally read SQL our sprint planning meeting takes about eight hours. I mean, don't have to be eight hours No, that's like painful, you don't have to be that long. Okay, each state has like, you know, three hours or something or two hours. I mean, one hour is more than enough, but there is she the issues are no the one the issues are convoluted and you know, a lot of complex issues, then no, of course, it takes time because then they want other team to be you know, come into our, our team and try to understand that one, and then they won't implement their own style and we want to do that for it takes more time. Right?

So, whole League, it's just for meeting. These are like part two, the planning and then you have Fear is no damn given specifically no outside influence can interfere with the scrum during a sprint. No one is supposed to come into the team. But there is another version of that. Okay? They can work out too.

It's up to the to them because it's up to them to decide like who do they want anyone or to work on the team, or they just want this team to be self organizing and self sustained for that, you know, we can work each other to get over things done. Not we don't need any help from the other team. This is more more, being more civilized. You know, you have to work with your own team and get things where you don't want to waste more time to just call the other team and just work on it. Okay, so that's how to what is daily Scrum. Every team member should answer on the three questions.

That's what I said right. What did you do since yesterday What being in too much stopping you to get the work done? So this is Sprint Retrospective. This is what product backlog for explain why this this is like high level requirements, we can take it as high level requirements and estimation correct backlog is used for forecasting that that's a very good question. Yeah Chicken and pigs, right? You got the garden clearly good Darren.

Like this one, so she can pick. So they actually didn't like saying, you know, Why did the chicken do and pigs could sit idle no like there is like saying but chicken you know when you know you cut the chicken and you take it as a meat right, but the pigs don't do anything of ingesting it. So that's what chicken means that the whole work the whole work who does in the team and the pigs don't do any work sit idle. Um Yeah, so it's kind of yeah that way. But Scrum mastery is like a big undermining of People are like a chicken who does a whole work to a chicken does the whole work and you know, pig just but I mean that's not like specific to be Yeah, it's not like being specific like you know the chickens is like an old team and you know pieces like Scrum Master know, Scrum masters are too busy, okay, sometimes commercial deserver of the development of because he is a developer x commercial developer, so he doesn't fit all right, because he has his own work, no application of burndown charts, no burndown charts and he work around you the issues if there are issues.

So there is there are many testers and then he coordinates with our other team. Okay, so Okay. You know, he also has some work to do, but not always, oh, that's what it means chicken and pigs, chicken wings, all the rest of our team and pigments. The person who doesn't do what and then you have sprint backlog are some strict rules you know, should not be more than 100 tasks, I've never come across more than 20 So, if you have 20 then it becomes more too much of work to it it gets one month he cannot 20 task is good they cannot go beyond that. Okay because it becomes harder and you know it's time consuming and everything we can think out right you need to be in order everything should run in orderly right so. So then burndown charts like this by actual remaining effort.

And then you have so it's actually it's not a straight line. Who am another burndown chart release burndown chart in addition to which have Y axis you will be having two charts where you see two the more number of charts and even more number of work okay? So so much no you need to work more. Okay Scrum Master notes permission on anyone who will be working on but no one manjaro is good burndown chart very is one more release burndown chart if you want to put then then you have by access pass to and native and then x axis okay Texan we've been a model based support that will be Mr. Mister that we believe the typical scrum team in about six to 10 people yeah there should not be no more than 10 people it becomes then you will Need to get into another team?

No You cannot work more than 10 people in a day okay. So this is no part of that is what it is and disadvantages. So you see normally AJ for me like you know AJ, when you have small projects HR is good when you have big projects waterfall methodology is good but now things are changing even if it is big projects Now you also know using agile and distributing our error I know breaking up the work and dividing the task and then you're distributing the duties. Okay, so now even big no big project you're still doing into the object. Okay. Okay, so it's already one.

Okay. Any questions? So everyone has this document right? Go ahead and you can read the document also I will be giving homework on this agent. Okay. Depends so Depends on the project how you want to work on the project.

So it's like whole company level right companies it's like completely science how many more teams we need if they are work, see everything might be in agile and some will be in waterfall. So if it's in a time when we have like 10 Scrum teams, okay, let's work on 10 Scrum teams and in agile and then the remaining waterfall. Then if they perform well, that term 10 Scrum teams, you know, perform well then Okay, we can move that, you know, in another 10 teams. So individual is, you know, it's a process. It's a company who has to decide, okay, okay, so any more questions? Any more questions?

Okay, so if everyone are good, can we close class? Okay, yeah, thanks