Automation Testing Full Course 2026 [FREE] | Automation Testing Tutorial For Beginners | Simplilearn

Key Takeaways

of every webpage and see on the internet from headings and paragraphs to tables, lists, links, images, and forms. That is exactly what today's session is about. Hello everyone and welcome back to Simply Learn. In this video, we will explore the fundamentals of HTML and understand how websites are structured from the ground up. HTML is the backbone of every webpage and if you want to build strong web development skills, this is the perfect place to start. In today's session, we will cover the basic HTML document structure, heading tags, text formatting tags, tables, lists, links, image handling, and introduction to form elements. We will also see how these concepts are used in real examples so that you can understand not just the syntax, but also the purpose behind each tag. This topic is especially important because HTML is the first step towards learning front-end development, automating testing, and also modern web technologies. Once you understand HTML properly, it becomes much easier to learn CSS, JavaScript, and advanced frameworks. By the end of this video, you will know how to create a simple HTML page, how to organize content correctly, and also how different tags work together to build a complete webpage. Also, just a quick information if you're interested in building a successful career in full-stack development, don't forget to check out the AI-powered full-stack developer program. This course is designed for aspiring developers and professionals who want to master the MERN stack while leveraging the latest generative AI tools such as ChatGPT, GitHub Copilot, Amazon CodeWhisperer, and Hugging Face to enhance coding, testing, and deployment workflows. You'll gain hands-on experience through 60-plus practical projects and exercises including industry-relevant capstone projects while learning to build scalable, secure, and modern web applications from scratch. The program also includes 100-plus hours of live online training led by industry experts covering front-end development, back-end development, database management, APIs, cloud development, and AI-powered software testing. In addition, you'll receive Microsoft Learn access along with official Microsoft course completion certificate and transcripts. With the AI-powered resume building, LinkedIn profile optimization, mock interviews, and Simply Learn's job assist program, you'll have the support needed to confidently pursue full stack developer opportunities in today's competitive job market. Hurry up and enroll now. The link is given in the description box below and in the pinned comments. Now, before we move ahead, here's a quick question for you to answer. Which HTML tag is used to define a table row? Is it th, td, tr, or is it tbody? Comment your answers below. Let's get started. >> So, we'll be starting with Agile, Git. Uh did you all get this plan? Do you have Do you know about this plan? Do you know about the courses assigned to you all? So, the plan is to cover all the basics, okay? So, first plan is to uh cover the Agile, Git, MySQL, okay? And then we'll be covering HTML, basics of HTML, then basics of CSS. Okay? So, I will be uh Yeah, got to know. Yes, yes. So, I will I will be teaching all this, JavaScript, okay? And then Cypress, okay? So, all these things we have to So, there's a lot of things here, okay? So, we will be touch basing some basic uh aspects, okay? And uh the the necessary aspects for you to be uh somewhere you want to be an automation developer, right? So, for an automation developer to get I know that you all are here to get to a level where you can comfortably get uh selected in automation interviews, right? To get a role into some project where you can be an automation asset developer, QA engineer, right? Here are some There are some people who are already some about some real real-time projects also, right? Who wants to get more knowledge into these fields, right? And there are uh some some learners who have already some kind of experience and they want more experience, right? So, majority I have no experience. So, considering that, I will be starting all from the scratch as what the Bhumika I have told, right? So, going forward, the path will be to cover the Agile, get MySQL. Okay, basics of HTML, CSS, okay? And then we will be covering uh Cypress, okay? So, this is for the phase one. Phase two will be starting with uh Java, Selenium, and all those things. So, this is a plan for the phase one. And I think in the last uh weekend, we will be doing the project, okay? I will be giving you the project. And you have to do the project. As that's what the Boomika told on what will be the project and uh project details, I will be discussing with her uh maybe tomorrow, okay? So, today we are going to uh start with this Agile. And this is the course uh okay? Uh planning and automation. 80 phase planning and automation. Do you all have this course? I hope everybody have got uh Simply Learn um the all of you are on this LMS? Are you all Are you all on this LMS portal? Okay? We have Yes, if you are there on this LMS portal, okay? So, if you are on this portal, I would expect you guys to open this one. This one, phase one. Okay? So, since many of you are beginners, right? I would expect you to So, this is the course. And uh in this we're going to just click on continue learning, okay? So, here I'm going to show you where from where you're going to extract all the books, okay? I mean the contents to read. Right? So, here uh you have to go and download all these e-books. E-books are there, right? And you can download this lab guide also. There's a download icon, right? And download this practices also. Okay? So, download these three things. Okay? So, take a minute or two and please all these materials. Practices are not visible to you. Okay, it should be visible to you. Okay, practices. Because these are the things from where I have taken all the PPT and stuff. Okay, and that is what I will be referencing and from there only I will be teaching you. Okay, and this is a lab guide. All the lab things we'll be doing from here only. For Agile, we do not need to do the lab. Okay, uh but I will be showcasing you a few things on the G9 all directly. That's different. Practice option. Assisted practices. Okay. The practice um should be visible. Uh these options should be visible to you. If it is not, then please check with uh Okay, it says automation testing fundamentals. Okay. Automation testing fundamentals. Okay, so you can um contact Humeka after the session for that. Okay, as of now, please open the e-books. In the e-books, you will get uh the first e-book of uh introduction to Agile. Okay, you'll get that. Uh you can click on that. Okay, we are going to start from there. Introduction to Agile. Please click on that. There is trainer PPT also. Okay, phase and projects ones. Okay. We are going to start with Okay, I'm just going to open the PPT only. If I If I I have uh the downloaded the Yeah, e-books. Just let me download the e-books also. I have the PPT, but I have preferred e-books. So, I'm just downloading e-books. Just 1 minute. Okay. I'm just opening that. Now, I've gone downloaded it. You can unzip it and in that, you have to open the first one. Okay, so we are going to start with Agile introduction to Agile. Right? So, so you have to open this. So, I have I have opted for the PDF, not the PPT, okay? So, we are going to first start with the Agile, okay? So, basically, uh this is all about SDLC, okay? Yeah. Okay. So, now, if you go to any project in any company, right? They will be having some sort of development model which they will be following to develop the project, right? So, basically, uh there are different types of SDLC. Now, I'm going to talk about SDLC first. So, even before I talk about Agile, there is something called as software development life cycle. Right? So, any software, right? Which develops in any company. So, here there are many beginners in this room, right? So, I'm setting the context before I start into Agile at all. So, suppose tomorrow if you are selected, right? And if you go and work in any company, suppose you're working for ABC project, okay? Then, how does that project works? Definitely, that project is developing some sort of application, right? Then, you might be wondering how do they develop? What is the phases in which a software develops, right? So, the way a software development happens in any company, right? So, that is called as software development life cycle. Okay? So, just like how we the human beings are born, okay? And then we are born as an infant, then we became small child, right? And then we become teenagers, and then we became uh mid-age 40s, then we become 60s, finally we become very old and we die someday, right? So, that is a life cycle of human beings. Similarly, a software also goes through different phases. In one day, nothing have got developed, right? If you see so many applications around it, right? Okay. So, what happens is that a software, any software, let us for example, you say Spotify, right? Spotify was developed over a phase of time, okay? Through some phases. So, any software which is getting developed in any company gets developed through some phases. So, what are those phases? Let me talk about, okay? So, first phase is a requirement gathering. So, requirement gathering in that requirement gathering what happens? In requirement gathering phase, the BA, the business analyst, will be gathering the requirements. Okay? After that, once the requirements are gathered, everything is confirmed, then the system design will happen for that. And that is usually done by the system architect, okay? Then after that, the developers will do the high-level design and low-level design. So, these are some other documents which are created by the developers, okay? So, these are the phases, okay? Directly, you will not start coding. So, before coding, all these things have to be done. Then the developer will start implementation. Once these high-level design and low-level design documents are done, okay? And then, um after that, implementation starts. And once the coding is done, then the testing will start. Where your people you people will come into picture, right? So, uh then after testing, once the testing is done, you the QA will say that we have tested everything, everything looks good, then they make a decision. They means the entire engineering team makes a decision that now we are in a confident position to uh ship this software to the outside world, right? Like how every year in September, iPhone releases its new product, right? So, that is called as deployment, okay? It It is called as deployment phase. So, these are the phases in which a software development happens. Yeah, you can say launch, okay? So, these are the phases. I see, in 4 hours, okay? Very difficult to cover everything. So, what I'm trying to do is that I'm trying to be as uh you know, very choosy about what I'm I'm going to teach you. So, we'll keep it uh very short and crisp, okay? And we will try to focus on this PPTs, okay? So, um Agile is one type of SDLC model. There are different types of SDLC model. If you ask me to talk about SDLC model, I can talk about it for an hour or a two, okay? But, in this course of yours, they have specifically focused Agile because now 99.99% across the world, I think IT projects are using Agile SDLC model. And why Agile? Because Agile means being adaptable, right? So, it brings adaptability into its approach, okay? So, we'll see how does it do, okay? So, now let's get started. So, Agile is a type of SDLC model. It's one way of software development, okay? So, John has decided to choose Agile methodology for his automation testing projects. So, to complete his project, he has to learn Agile method methodologies to comprise the series of frameworks. So, Agile methodology is a way of project management in software development, okay? And it [clears throat] consists of series of frameworks. Okay? So, there are a lot of frameworks which implement Agile, okay? In Agile, what happens? We develop the product in increments. Increment means, suppose now tomorrow if I ask you to develop a login application. Okay? So, what will you do? Will you do uh will you do you develop everything at a time and give it to me? No. So, what are you going to do? So, suppose for the first 2 weeks, you're going to develop the home page login page. Next 2 weeks, you're going to develop the home page, right? So, like that, if you're going to develop something like that, login page, and after that, you're going to develop home page, okay? In the first 2 weeks if you're going to develop the login page, next 2 weeks you're going to develop the home page, right? If the development happens like that, develop means both development and testing. Okay? You're developing this functionality of login page, and next 2 weeks you're developing and testing home page, right? Like that, if you keep on developing and and and uh uh testing, you know, you are actually implementing one one feature in certain period of time, right? In certain iterations, that way of development is called as Agile, okay? You're developing something in increments. Instead of developing the entire thing at a time, you're developing in increments, okay? So, this is one uh advantage here, why? Because if uh in every in every iteration, suppose now you're developing the login page, okay? in 2 weeks. Okay? Because that's the that is the that is how uh the development happens in Agile, okay? You're going to develop in increments. So, at a time you're not going to say to the customer that, "Hey, you come after 6 months, and after 6 months you're going to see my product." Not like that, okay? So, here you create a road map. You you tell the customer that, "In first 2 weeks I'll do login, next 2 weeks I'll do home page, after that I'll create the search functionality, next add to cart, okay?" And after every 2 weeks you will tell you will showcase that to the customer that we have Okay? So, this kind of actually uh development brings uh customer feedback, okay? If you've not done something what the customer likes, he can give some suggestions which you can incorporate in the next plan. So, there is a lot of flexibility in terms of incorporating customer suggestions, right? So, that is why this is Agile, okay? And there are a lot of frameworks which implement this Agile methodology, okay? Like there is uh uh Scrum, one of the very famous framework. Okay, Scrum framework is there. Safe is there, scaled agile framework. Okay, Kanban, extreme programming, all these are there. Okay, so Joel have to work on a project where he have to learn the agile methodologies. Okay, because he's working on such project which is using agile. Okay, but for that he have to learn few concepts which he'll be learning in this lesson. Fine? So uh by the end of this lesson you will be able to describe you will be able to describe agile methodology. Okay, and um comprehend agile testing methodology classify waterfall and agile approaches. Describe Scrum roles as I told you Scrum is one type of agile framework, right? Practices and estimation. Okay, now what is agile methodology? So as I told, what is agile methodology, right? So in agile I told you, right? It is It is the the development of the product happens in iterations and increments. Okay, so it is a practice that encourages continuous development and testing throughout the project software development life cycle. Okay? So both development and testing operations are concurrent under the agile testing, right? So here what happens? You do the work in sprints, right? So this is for 2 weeks, you develop something and you deliver, right? Next to 2 weeks you develop something and you deliver. Okay, so here the development and testing will happen in parallel. Okay, so this is both is happening in parallel. Okay, so this is what it means. Then only you are delivering a feature, right? Okay, now the methodology process includes these are the high level things. Evaluation of the process and current structure of the company. Okay? So, this this methodology process, Agile methodology process includes all of these things. Okay? So, this is the entire thing which it includes. Uh suggestions for the improvements and process, okay? So, any Agile uh process uh Agile methodology, right? Nobody's going to implement it directly. You have to evaluate the process, whatever the process is happening in the company, and the structure of the company, they have to take into considerations, right? Suggestions for the improvements and process optimizations, okay? Application design together with the client. Okay? Application construction and implementation and evaluation and monitoring. So, this methodology process includes all of these things. So, there is a lot of scope for improvement, process optimization, okay? And there is a lot of collaboration and all these things which happens. So, I will tell you how these things happens. When you will go through all the other slides, you'll understand. Okay? Agile testing methodology. So, automation that is Agile testing in software development is a test automation methodology used in Agile process. The goal of Agile automation testing. So, what is automation, right? Automation means we're going to automate something which we're going to do manually, right? And why do we do that? Why do we automate? We do automate to get faster feedback, right? So, something which we are going to do manually, right? Will take ages, right? To do. Suppose now there are a lot of test cases which you need to execute. So, if you do the execution for manually, it will take a lot of time. And for you to give the feedback to the developer, it will take time. But if you have automation, automated test cases, right? You will run them and within 1 hour you can give the feedback to him. Based on that results, you can take a decision whether you're able you're going to release it or you're not going to release that software into the outside market or not. Right? So, the goal of Agile automation testing is to improve the effectiveness and efficiency of the software. Okay? Then, this are the uh manifesto. Okay? So, this manifesto is also available on the internet here. Okay? If you go to the internet, okay? And if you type Agile manifesto, okay? So, a group of four developers came together, I think in the year 2017 or something like that. Let us see. The story is already written here. Okay? So, you can see here. So, this are the manifesto for the Agile software development, okay? I hope you can see the screen, right? So, this is the manifesto, okay? For the Agile. Individuals and interactions are prioritized over processes and tools, okay? In Agile, these indi- we believe that more focus should be given to the peoples and the interactions between them over the processes and tools, okay? Working software over comprehensive documentation, okay? So, it's all prioritized. Left-hand side is prioritized more to over the more over the right-hand side. Customer collaboration over contract negotiation and responding to change over following a plan, right? So, this you will see uh you will uh you'll understand through when you will understand the Scrum, okay? The Scrum is on framework, as I told, that every sprint, right? In every 2 weeks you're developing something, correct? And in every 2 weeks you're going to get the feedback from the customer, right? So, there you're getting working software and customer is collaborating also every 2 weeks, right? And if the customer is saying that this thing they don't like in that 2 weeks they are not liking this particular thing whatever the developer have made then they can change that in the next in the next sprint or in the next upcoming week, right? That is responding to change. Okay? So this is manifesto. Same thing is here in this slide. Okay? A little in a little bit different way but same thing. You want this? I can send you the list link. There are some 12 principles also. You're interested you can see this. These are those developers some 17 developers. Okay? There are some 12 principles of Agile software also. You want you can have a look at it. So this is not this is actually not a very you know this Agile is very theoretical so I'm using this PDF. Other topics we will be directly using hands-on. So we will be using directly I'll be using my runbooks and I will be teaching through the lab. Okay? So it'll be very interesting other topics. This will be a little theoretical today. So I'll be using PDF. Other topics we'll be doing directly on the lab and I'll be having my own word doc where I'll be writing and teaching you. Okay? We might not be using all these PDFs much. Okay? You can use it to refer at the end of the class. Right? This is very theoretic right? I cannot I mean just show you through lab all these things. Right? So now there is something called as Okay, yeah. Where is it? Yeah, yeah. Agile methodology, right? Agile project management techniques involves deep communication and iterative development. I told you, right? Iterative development just now I told you I think she just asked me, right? So we develop the software in iterations. Okay? So first sprint I developed what? Login page. Second I'm talking about e-commerce application. Suppose e-commerce application I'm developing, right? And the plan is to develop something in iteration then first a sprint I develop login second sprint I develop home page third sprint I develop the two card right like that. So every sprint sprint means every two weeks I'm developing something and that is iterative development. Okay, so agile project management is based on an idea that the project can be improved continually throughout its cycle and changes can be made swiftly and appropriately. Okay, so this is what it is. So this is the brief agile project management is amongst the most widely used method because of its what? Adaptability. I told you right is the flexibility and emphasis on the client feedback right? So I told you right suppose now after after every two weeks you will give a demo to the customer and to everybody that what you have developed and are there any changes required right? You will do the changes in the next sprint. So this brings lot of adaptability, flexibility and emphasis. Here the customer is the god right? Whatever customer will say will do. Now let's talk about differences between waterfall and agile approaches. So what is waterfall? What does the waterfall looks like? Like this. Okay? So in waterfall model what used to happen? Okay? We used to follow all the phases like requirement gathering phase right? What all what all I told? These phases they are there requirement gathering. Correct? So requirement gathering was there and uh system design will be there right? And then your HLD LLD everything was there okay? And but these phases will will be happening sequentially. Okay? In requirement in the in the waterfall approach. Okay? And you cannot go back to the previous So this is a waterfall model. It looks like how water falls from a staircase like that or from waterfall right? Here all the phases are there. You can see development, uh requirement gathering, design, development, testing, then deployment, and maintenance. Okay? But here, the drawback is that you cannot go from one phase to another phase back. There is only one movement which is from up to down. Okay? So, the problem here is that if you realize that in testing phase there is some requirement which is wrong. Okay? You cannot go back to the requirement document and make changes. Okay? You have to complete all the cycle and then only you can go back. Okay? That is why we can use it only for simple projects where the requirements are simple and stable. We cannot use it for those kind of requirements where the requirements are fastly evolving and customer is fastly changing the requirements. We cannot go back because that's the nature of this model, Abhishek. That's how this model is designed, right? By virtue of its design. Okay? Every model will have its own design, right? So, this is the design of this model. You cannot go back. And you see the arrows pointing down only, right? So, this is the waterfall model. So, this model is good for small projects where requirements are stable and not changing, right? But now if But now we don't have projects like that existing in current world. Correct? Nowadays, the projects are like tomorrow if Okay, so what to is bringing this change then to give you say that I'll bring this change, right? Today if this car car if this car is bringing this change, maybe in another 1 and 1/2 months you can see that some other car is coming on the market with some other change which is better than this change, right? So, there is a brutal competition between the competitors and and the competitors in the market, right? And if they don't change their business will not grow. So, this waterfall model is no more existent. When I started my career way back in 2007, I have worked on few models which were using waterfall model and V-model approaches. Now, there are no more waterfall and V-model. Now, coming back to slide, the differences. Okay? So, the project development life cycle is split into sprints. Okay? Here it is divided into segments. It takes a step-by-step method. Waterfall technique is a method of sprint and design. Okay? Agile technique is a well-known for its adaptability. Right? So, as I told you that after every 2 weeks you can take the feedback from the customer. Okay? And you can take the changes also from the customer. And it's very flexible in Agile. On the other hand, waterfall, you know, is a structured sequential, right? Flow. Okay? It is very rigid. Rigid means anything happens in between, I told, right? It cannot change. You have to go all the way down. Right? Next one. Agile can be thought of as a collection of many projects. Right? So, here, why collection of many projects? Because you're developing in iterations. And every iteration is like a mini working software. Right? So, that is why. Next, Agile is very adaptable strategy that allows for change in project development requirements after original planning has been accomplished. Once the project development begins, there is no way to go back. So, Agile brings adaptability. Right? There is a flexibility. But here, there is no flexibility. That's it. Okay? So, please go through this. Take a minute or two. Then I'll move on to Scrum, which is a very nice Agile framework. Okay? Please go through this, guys. Take 2 to 3 minutes. Now, we are going to discuss about Scrum. Okay? So, there are different frameworks which are there in Agile. Uh Scrum is there, Kanban is there, extreme programming, safe, scaled Agile framework is there. Uh what is framework? Framework. What is framework? Framework is basically basically something which gives you some guidelines, okay? Or some rules. Like, for example, there is a there's a game football, right? We call it as football because it has some rules or it has some it has some steps to follow, right? So, yeah, you have got it rubbish it. So, this is it will give you some kind of rules or checklist, okay? So, that is framework, okay? So, Agile can be implemented by using multiple frameworks. Scrum is one of them. So, Scrum is a methodology for addressing complex adaptive changes but by producing high-value solutions in a in a productive and creative manner, okay? So, Scrum is neither a process or a technique for So, Scrum is basically neither a process it's not a process or technique. It's a framework, okay? But, it's it provides a framework for from which multiple processes and techniques can be used, okay? So, what is Scrum? Scrum displays a relative effectiveness of your product management and development techniques enabling the organizations to improve. It have given some rules that you have to do this, that, these are the different meetings, these are different roles, okay? So, we'll see what are those things in the upcoming slides. Now, in a Scrum team there are different roles. What are those roles? These are the roles. The Scrum team consists of three roles. These are the roles. Scrum Master, a product owner, and the team. Okay? So, there is a Scrum Master. Now, who is this Scrum Master? Who is this person? Scrum Master is basically a person who is a master of the Scrum as the name suggest. He is not a dictator person. He is not a very authoritative person. He is somebody who is a certified Scrum person from Scrum Master from Scrum Alliance. You can go to the Scrum Alliance website, okay? And see who is he, okay? He's not just a facilitator, actually. He is more than that, okay? He makes sure that the team is following the Agile best practices. He makes sure that the team is following the following the Scrum processes, right? And he makes sure that all the Scrum meetings, events are happening in a proper way. They are efficient, not just happening for the sake of name, right? to make sure that the team is using the Jira in a hygienic way, right? And okay. So, this is This is This is what I see some chat guys here. Just Just a sec. I would like to talk about that in a minute, okay? Okay, first let me go through that, then I will talk about the chat, okay? There is some confusion here. So, Scrum Master is basically a certified Scrum Master from the Scrum Alliance, okay? I will show you the website. This is the website. Scrum Alliance. So, this is something So, this website is something from the It's a It's an internationally accredited website, just like ISTQB in India. Uh sorry, internationally accredited organization, which gives ISTQB foundation level and so many other certifications, right? You heard about it, right? Website is not visible. So, here this is the website. In this, there are some certifications. Okay? This is the one. Okay? In many companies, what they are doing, they are making some testers, some developers and certified Scrum Masters. That is not the correct thing, okay? Okay, I'm bringing here for you guys. That is not the correct thing, okay? Scrum Master should be a certified Scrum Master from this website. I have done three certifications from here, CSM, Advanced CSM and CSPO, okay? Why? Because See, companies think that they can make any XYZ as Scrum Master. Anybody can work like a Scrum Master. It's not like that guys, okay? This Scrum Master is a servant leader. What? Servant leader. He's the person who will facilitate all the meetings. Yes, somebody said facilitator. He's correct. You're correct. Not only facilitator, he's also a coach for the team, a mentor for the team. It is his responsibility to remove all the impediments, all the blockers for the team. Right? He acts like a coach for his team, okay? He will not boss around like, "Hey, give me this. Give me that. Why didn't you do this work?" No. He have to work with that team. He makes correct processes. He makes the team cross-functional and self-organized. Right? This is the guy, self Scrum Master. He should be certified Scrum Master from the Scrum Alliance. Next time if you're going to work in any company, ask him, "Do you have the certification or not?" If you don't have any certification means go to his. Okay? Product owner is BA, business analyst. Basically, this person is from an MBA ground background who is having some special expertise in some domain like finance domain or marketing domain, whatever your project is, right? So, he's the one who will be in constant communication with the with the customer and he's the one who will be actually doing all the requirements gathering, right? And he's the one who will do taking care of creating all the meeting all the requirements in the Jira. Now, Jira is a product is a requirement is a project management tool, okay? I'm not sure if I have the Jira account with Jira account still with me. I'll just see if I have Jira one minute. Just a minute. >> Okay, so this is Jira, okay? Jira software. And you can also download you can also install it. There is no EXE. You can just it is available on the cloud. You can go to Atlassian website, okay? So this is Um there is a website Atlassian, okay? Atlassian is a uh Australian-based company, if you know. This is the company, okay? Atlassian. Just type this. You this company have got many products, okay? So many products it have. Can you see? If you go to products, okay? You can see that developers, IT and all. So it have it have it have got Jira also, okay? So you can go and download Jira, okay? So you can see explore Jira. And there is an option get it free, okay? You can click on this get it free. I have already done it. So see and continue, okay? So for me it is not showing try premium, okay? Because I'm already there on the Jira, right? So for you you can go can you see try it free, right? So like this it will come. And you can be on Jira. So maybe tomorrow, whatever time you're free you can try this, okay? Right now you can see is uh I have created one project here, e-maestro, right? So this is the this is some project which have been created. Can you see? Scrum is the framework. Jira is a project management tool which is used to handle all the project management of Agile project management, okay? So, this is Jira is a tool, okay? Scrum is the framework, right? You can see that this is the board, okay? And this is the backlog, can you see? Backlog is nothing but all your requirements will be in the backlog. So, guys, we have very less time, okay? As per the time, uh, we have to just, uh, go, okay? I'm just trying to explain you on a very high-level kind of thing, okay? So, this is, uh, where we are going to store, uh, all the all the requirements of for that particular application. And here, they're creating, they means who is creating? So, you can see, this is a ticket. This is one user story, right? Um, file login feature. So, these are all the requirements. Who creates these requirements here? On the click on the create option, the product owner, okay? So, why I came here to show you? I came here to show you because I have to explain you this one. I have to explain you this one. Where did it go? This one, product owner. So, product owner creates all the requirements on the product backlog, okay? And he keeps it updated. Next is the team. What is the team? Team is made up of developer plus QA, right? Yeah. So, now this I already explained, please go through this, okay? I already explained this, please go through the slide, take a minute. I'll keep scrolling down and you can go read this. Scrum Master is, uh, master of the Scrum, right? So, he makes sure that team is following the Scrum processes, okay? And team is aligned to the Scrum practices, okay? That's how he ensures he maintains that because he's certified Scrum Master, right? He's the master of the Scrum. For example, he knows how to conduct the sprint review in a proper way or sprint retrospective in a proper way. Now, he will make sure that the meeting is happening in a proper way. That is one example. He will make sure that the sprint planning happens in a proper way. Team knows all the different things like, you know, how to estimate the story properly and all those things. And by doing all those things, he ensures that the Scrum team maintains Scrum values that are achievable. Okay? Okay, so this is all about the product owner. Some more things, okay? So, product owner increasing the value of the work. How will he increase the value of the work? Because he knows about the requirements, right? So, by writing the story in a proper format, by adding acceptance criteria. What is acceptance criteria? These are like checklist which makes the developer and testers knows how to how to accept, right? These were the Suppose now there is a login requirement, right? In login requirement, he will write that if you enter username and correct username and password, the home page will be visible. Now, he will also write that you cannot enter If you enter wrong username and correct password, you will get an error page with this description, right? So, all these things he will add in the acceptance criteria so that the developer end knows clearly what to develop and the tester knows clearly what to test, okay? So, he will increase the value of the work like that. Setting the team's product vision, right? The team don't know what they're working for. Only the BA will tell them that this is a big picture. Okay, you're going to do this. By doing this, he will show them by discussing about the requirements, the functionality of the application, he will show the big picture to the team, okay? Ensuring that the team is focused on meeting product requirements and communicating and assessing the progress. Contacting the external stakeholders and communicating. So, he's the person who is talking with the customer, as I already told, on the on the requirements and all, right? So, ensuring that the team is focused on meeting product requirements and communicating and assessing the progress. So, he's uh he's the one who helps meeting with the team in understanding the requirements, backlog refinement meeting, and all those things. After this, I'll discuss about that going forward, okay? The team The team is cross-functional and self-organizing. And implies the team is what? The team means nothing but developer plus QA. Okay, it implies that the team will include analyst, designer. So, this is all about the team. You can go through this, okay? Okay? So, this is all about the team. What is cross-functional team means? Cross-functional means everybody knows others all the work, okay? Like no no team member is just like knowing only one skill set, right? So, that if one team member is not present tomorrow, then the other team member is able to conduct or do the other team members' work, okay? That is the cross-functionality. So, that is what the cross-functional means. Cross-functional teams have all the skills required to have all the skills required to complete the task without relying on anyone outside the team, saving time and effort. So, that is what the cross-functionality means, okay? So, that is cross-functionality. Okay? So, the term concept The team concept in Scrum is designed to enhance flexibility, innovation, and product productivity. Okay? The team is tasked to do all these things, okay? So, um what is this sprint planning? So, they do the planning together, right? So, the planning happens for the next sprint. So, the team comes together, and do the sprint planning and target setting. They contribute the knowledge to the programming design, right? The team entire team, the developers do the programming design and improvement of the product. Even the Even the testers are also a part of all the design and backlog grooming, backlog refinement sessions, okay? Kick-off feature kick-off sessions. When I'm talking about back of the requirement means the back product owner is talking about the features. Uh features or functionalities or the Jira tickets or anything you can say or the back of the requirements, okay? So, this is this this results in collaboration and the entire team works together as one agile unit, okay? To determine the best development strategies using the data. The team is uh in a position that they develop the product using the best development strategies using the data, right? So, if they have the sufficient data and based on that data driven decisions they take, they develop the uh best product, okay? Including testing product and prototype as well as other methods. Include testing products and prototypes as well as other methods. So, so the team includes testing products, right? Testing product means like some automation products or something. And prototypes. Prototype is nothing but a blueprint, okay? Or you can say like uh blueprint of some application. What is prototype? Now, suppose I'm going to develop a I'm going to develop a UI, okay? For for anything. Then what what I'll have? Suppose I'm now the real UI is not developed. So, what I will do before that? I'll create a prototype. So, that those my UI will look like this. Okay? My UI will look like this. This is login page. Then if I enter this then then the home page will look like this, okay? So, this is called as prototype, right? So, some designs you will have before in hand even before when your real project is created, right? So, that is called as prototype, okay? So, you will have including testing products and prototypes as well as other methods. So, team will be having all of these things. So, this is the road map, okay? And I told you that you are going to develop this login page in the first 2 weeks, that is the sprint uh sprint one. Next sprint next 2 weeks you're going to develop the home page. That is a sprint two, Okay, next 2 weeks you're going to develop the about page. Okay? And after that you are going to develop the payment integration, right? You're going to integrate your uh website with some payment sites, right? Like Paytm or some kind of wallet or Google Pay. That will happen in the sprint four. And the last one is the order screen, which you're going to develop in the last sprint, sprint five, and then you're going to release the product also. So, this is the road map. Okay? And this 2 weeks time in which you're going to develop and deliver some increment is called as increment is called sprint. Okay? And in most of the most of the projects and most of the companies that is 2 weeks. Okay? It's not 1 week or 3 weeks. You will ask me why it is 2 weeks. And it is always uh 2 weeks only. Whatever the projects I have worked so far, it is just 2 weeks. Okay? So, sprint one started on 8th of December. And it So, suppose now sprint one. Now, let's do it practically, right? Now, just imagine our sprint have started on Suppose on 5th of uh January. Okay? Is that fine? Sprint one started on 5th of January. 5th Jan. Okay? Then it will end on which date? 16th Jan. Okay? Does it make sense? Okay? 16th Jan. And I have to change the year also. Okay? And then this is the from 5th of Jan. Okay? 5th of Jan. Okay? I'm going to remove all of this. I will explain what are all these things. So, there is 10 working days when you will be developing and testing. The 5th of Jan till 9th of Jan will be the first half of the sprint, first week. Is that clear? 9th of Jan. Okay? Then after that, 12th. Right? 12th of Jan till what? 12th of Jan I'm removing all this. I'll explain what whatever it is. 12th of Jan to 16th of Jan will be the last, right? Is this clear to everyone? Okay, so this is my sprint. So this is how the sprint looks like, okay? So when you're going to work in a team, this is sprint you have to develop the login page. Okay? So in a sprint some meetings happens which is called as sprint ceremonies, scrum ceremonies, or meetings. Is that clear? Okay. So now what are these ceremonies or sprint events or we can say the scrum event or meetings, anything you can say, okay? So these are scrum ceremonies or events or meetings which happens, okay? Within this 2 weeks times, okay? So first is the daily standup, okay? So daily standup as the name suggests will happen every day. So this is time boxed to only 15 minutes, okay? Daily standup, it happens every day and it happens only for 15 minutes. It cannot go more than 15 minutes. And in this meeting product owner is not mandatory. Okay? Product owner is not mandatory. His presence is not mandatory. He might attend. And who facilitates? Scrum master can be there. This is also called as inspect and adapt of last 24 hours, okay? So in this meeting what happens? Basically what they will ask, what did you do yesterday? What's the plan for today? Okay? So suppose now I'm doing a daily standup between issues or blockers, right? So if she says that if she have any issues or blockers, then the scrum master's duty is to unblock her. Okay? It is his duty. Okay? Is this clear or any doubt here it is in the daily standup? So this is the first meeting which happens and this is happening every day, okay? And it happens only for 15 minutes. If anybody is going beyond 15 minutes, talking more and more, then it's the duty of Scrum Master to tell them that please take this discussion outside the meeting. Okay? It is consuming everybody's time. Okay? Okay, next is backlog refinement. Okay, next is backlog refinement. What is this backlog refinement? Okay, now I told you in this, right? Sure. This is the backlog, right? This is the Jira. So, Jira is a tool. Okay? So, now in this tool what is there? This is your project. Okay? This is your project, right? Team A's tool. This is your backlog. So, backlog is a place where entire requirements of the project will be there. Okay? So, this backlog will have all the requirements. Okay? In real time, there will be some thousand or thousand plus requirements here. Now, this is just a sample Jira, so it is just having two work items. Okay? In real time, if you go to any project where you work, you will see some 500, 600, thousand requirements based on Requirement means what the product owner will do. Okay? He will take some requirements from this backlog. Okay? And he will actually pull in some sprint. Suppose now this is sprint is sprint zero. Okay? Now, this is your upcoming sprint. So, this sprint is already going on. Sprint zero is already going on. This is your upcoming sprint. So, what he will do? He will take some 10 requirements from here. And he will pull it in this uh sprint one. Okay? How he will pull? Now, you should ask me that question also. Okay? I'm showing you what will happen in the real time. Okay? This is what you will see in your real project. I'm showing you that picture. Okay? If you have any confusion, you can ask me. So, in real time what will happen is that the product owner will take the requirements, he'll put it in the sprint backlog. So, this is the sprint backlog. This is sprint, right? So, this is the sprint. So, you can see this option, start right? So, this is the sprint option. Uh this is a sprint name. He will take whatever tickets as per the customer's priority. He will pull up those requirements. Now, for the next sprint, we need to develop the home page. We need to develop what? We need to develop home page, right? For the next sprint, we need to develop home page. So, all the home page related tickets will be pulled up by the product owner into this sprint, okay? And what he will do, he will call the team and he will start discussing with them and he will be actually uh you know, discussing every requirement one by one, okay? So, that is called as backlog requirement, okay? So, this will not be empty here. It will have some 10-15 requirements or whatever number of requirements Uh yeah, it will be drag and drop. I can show you. See, either you can right click on this Wait, right click. Can you see? Move the work item. Suppose I want to move it to some sprint one. Can you see? I just moved. Can you see? It went up. You can also drag and drop. Can you see? One more I'll just drag and drop. It just went up. Can you see? And you can create also ticket from here. See? You can create from here also and you can create from this link also, okay? To create, okay? Suppose I want to create a user story. Okay, I'll show you how to create a user story. So, I'm creating a user story, okay? So, you can see that in the task work type, you have to choose what? User story. Okay? The summary will be you can write a short summary, login feature, okay? So, in Agile, requirement is also called as user story. Story means requirement. Yes, you are correct, okay? So, there is a particular way of writing the story, okay? So, the way is like as a user, okay? As what kind of user you can write as a e-commerce user, okay? I'm just showing you a real-time thing, okay? As a e-commerce user I want to login to application. application Okay? Now what we will achieve for that I can access the page. This is my guys being the story description. Right? Every user story will have some you know, acceptance criteria also. All these things are not here in your in your PDF. I'm telling you extra because these things you will see in your you know, like it acceptance criteria will be like you know, successful login with valid credentials. Okay? These are some So, what is acceptance criteria? Acceptance criteria will tell you Okay? Yeah, you're correct Chirag Bajaj. So, in your DM coming to that, I have not come to planning and estimation. Give me some time. First I'm discussing about this only. Okay? Few things. Okay? Just give me some time. I'll teach I'll talk about story point also. Don't worry. Okay? So, acceptance criteria I'm talking about. So, successful login then Okay. Uh invalid uh login attempt must show error message. Okay? This is some criteria. Okay? So, this is about the acceptance criteria. It can maybe many other things also. Right? So, this is if you can go and create. So, I've created a story and it have come to here. Okay? So, this is how the product owner will basically create guys. Okay? And in product backlog refinement, what will happen? Suppose now the team have come up. Okay? So, what the product owner will do? He will click on this ticket. Okay? Login feature. Okay? And he will discuss about this ticket. Okay? Suppose now this ticket is there. He'll start talking about this ticket about the business value of this ticket. Okay? Why are we What will the What will be the value of this ticket? Okay? And what will the What will be the end user would be getting? Okay? After after after getting this functionality, right? The bigger picture. This is very simple thing which I did login. In your In your real-time In your real-time projects, you might get some complicated functionalities also. You must understand those functionalities even before you are ready to start to develop or test. So, during this backlog refinement sessions, the product owner will give a bigger picture of what you're going to develop or what you're going to test. If you have any doubts or confusions during the feature development, you can directly give those questions to the to the BA and to the product owner and he will clarify all your questions. Another thing which happens as a part of backlog refinement is that if the team thinks that this particular ticket, right? This particular ticket is very big. It's very huge ticket which cannot be done by the team in one in one part, then the product owner can split this ticket into multiple user stories also. Okay? Fine. So, that also is done by the product owner. Second thing is that it in the product backlog refinement, refinement is always in the sorted order. Sorted means the the ticket or the requirement which is of highest priority will be at the top. Then the medium priority ticket and then the lowest priority ticket. Fine? So, which is at the highest priority will be kept at the top of the stack, then the medium priority, then the lowest priority. Right? So, after the backlog refinement, okay? So, when backlog refinement will be done? Backlog refinement is done usually on the first half of the sprint, usually on Monday or Tuesday, okay? So, it will be done like on Monday or basically on Tuesday or Wednesday. Between Tuesday or Wednesday, first half of the sprint. Okay, BR, backlog refinement, fine? So, once this is done, the next uh, scrum event which happens is sprint planning, okay? What is sprint planning? So, in sprint planning you will be buying for the next sprint, okay? So, in the current sprint, suppose you are uh, developing the login page, okay? So, in the next sprint, what do you have to do? In the next sprint, you will be doing home page, right? So, this is one one example which I'm explaining, okay? So, in the sprint two, what do you have to do? Home page. So, for that you need to plan now. So, somebody asked me one example, right? For planning and estimation, this is that example. I'm going to discuss about sprint planning now, okay? So, now home page, we will plan about the home page in the current sprint, right? Planning is always done on sprint So, what will happen in the sprint planning? Now you are in the first sprint, you are doing development and uh, of the login page. Now what you should plan for the next sprint also, right? You will do the You should do the planning for the next sprint. In the next sprint, what is coming? Home page. So, what will happen in sprint planning? In sprint planning, you are going to do the estimation for the for the tickets which we will be handling for the home page, basically, okay? That is the sprint planning. So, the sprint planning is a event which happens in the second half of the sprint. Okay? So, most of all, understand when it happens. When do the sprint planning happens? Sprint planning happens maybe on the Wednesday or Tuesday or Wednesday. Same thing. Tuesday or Wednesday. Okay? In the next half of the sprint. So, what will happen in the sprint planning? Okay? First of all, we should have some input for the sprint planning, right? So, for sprint planning, there should be some tickets from the home page. So, this is supposed upcoming sprint, right? Suppose now I pick this and put it here. This feature ticket. Okay? Say fine. And suppose this is sprint This is sprint is going to start from uh 2 weeks and this is going to start from 19th January. Right? Clear? 18th January to 1st Feb, right? These are two tickets. Okay? So, what I will do in sprint planning, guys? Okay? What we will do? We will start estimating these tickets. Now, you will ask me how we will estimate, right? Estimate means how much time will it take to Everybody when I say estimation, they will say that estimation is always done with reference to time, right? But, you will actually wonder if I say that in Agile, we are not estimating using time. Okay? Then you will ask me, and how do we estimate? We estimate in Agile by using story point. Okay? We estimate in Agile using story point. Okay? Now, what is story point? So, suppose this is the story. Okay? I am opening this, guys. Again, I'll open this in a big screen. Can you see this? Now, I am scrolling down. Can you see this? Everybody? This is all I'm showing real time, okay? Since some of you are beginners, you have not seen Jira, right? So, this is the story point estimate. When you're doing the sprint planning, you entire team come together and you estimate the story point. You do the estimation for the tickets. Tickets means the user story, okay? So, what is the input for the sprint planning? The input for the sprint planning is first sprint backlog. So, this is a sprint level backlog, right? All the tickets in this So, this is sprint level backlog, sprint backlog. This is the product backlog, the entire backlog, right? Many students will have confusion in this. So, now what happens in the sprint planning is that, okay, the entire team will come together. Okay, entire team will come together and one by one these tickets will be discussed. Now, suppose in a team if there are five people, suppose there are five people, one, two, three, four, and five. Out of which three are developers and two QA. Okay? Now, all these three people are in some different different places, okay? First So, this sprint backlog is nothing but this one. Right? So, this is the backlog. Backlog means this tickets under this sprint, okay? This is sprint backlog. And this is the product backlog. This is the backlog for the entire product, right? That's the only thing. Okay? So, this is the sprint backlog, this is product backlog. And this is the input for your sprint planning. So, what will happen? The scrum master will open login feature. Everybody will see this feature will this is will see this ticket will see this user story and he will ask them to estimate. And what how they will estimate? They will estimate using story point. Now, what is story point? Story point is a way of estimation in Agile, okay? In which you're going to use Fibonacci numbers. 1 2 3 5 8. Okay? Story point is Fibonacci numbers. And story point does not means man days. Okay? Guys, don't be confused. Okay? Uh please there is no confusion here. I'm showing you practically here. So, this is the sprint backlog which will which is the backlog for the upcoming sprint. Right? Home page. This is the product backlog. It will be 500 600 tickets here. From here you're pulling some tickets for the upcoming sprint planning. That's a sprint backlog. Okay? Right? So, this is this they will Suppose here 10 tickets are there for the next sprint. Every ticket the Scrum Master will open and the entire ticket team will go through this ticket and they will start estimating. And Jira and and in the child we estimate through story point. Story point is not man days man days. So, in sprint in in in the Scrum we do not estimate in man days and hours or days. So, what is the story point? Story point is the combination of these three things. Please understand. This one. Please remember this. Story point is the Story point is decided on the basis of these three things. How complex is the work the story? What is the size of the story? And unknowns. Unknowns means risks. Okay? Suppose you're going to do some requirement of work for the first time. Right? That means there are a lot of unknowns in that. Right? So, that is unknowns. Okay? Complexity of the work means if if the ticket or the requirement or the user story is very complex you're going to give a story point. And story points are in Fibonacci series. 1 2 3 5 8. So, a Fibonacci series is a mathematical series. You can go back and see. Okay? Yes, story point is an is an estimate of the effort required to complete the story. Yes, but story point is not days. If I say the story point of this ticket is one story point, that does not mean one day. Story point just reflects the complexity of the work, size of the work, and unknowns. Okay? Fine. Now, the entire team will come together and they will start estimating the ticket. Okay? Now, if one developer is saying it is one story point, another one is saying it is two, somebody is saying three, another one is saying five. Okay? What will the Scrum Master will do? What will Scrum Master do now? Yeah, Fibonacci series is a mathematical series. The series is called a Fibonacci series. 1 2 1 + 2 is 3. 2 + 3 is 5. 3 + 5 is 8. So, you can go to ChatGPT and see what is Fibonacci series. Right? It is a mathematical series where it goes from numbers 1 and 2. And it will keep on adding the previous two numbers. 1 2 1 + 2 3 2 + 3 5 5 + 3 8 8 + 3 13 8 13 + 8 21 so on and so forth. Okay? That is Fibonacci series. Very easy mathematical concept. Okay? So, why Fibonacci series? Some You should ask me this question also. Right? Some students ask me, why Fibonacci series? Fibonacci because it's a very good way of representing the complexity. One is the least complex and the complexity keeps on increasing as we go right. Fine? That's the Fibonacci. Okay? So, now suppose if one if one one person have given one story point for the same login ticket, another guy have given five story point for the same ticket, then Scrum Master will ask both of them. Why you have given one and why you have given five? He will ask both the people who have given maximum and minimum. Okay? So, if another one says one, another one says five, Scrum Master will ask, why you have given one? Why you have given five? So, both these people will give their uh own thoughts. I I have given one because it is very easy for me. And here is a very experienced person and for me complexity is less. Okay, so size of the work is also less for me. And there are very less unknowns in this ticket because I have already done this work many times. Okay, so that person will have given maybe that person guy was a senior guy. Now, another guy I given five, maybe he is a junior or he is a fresher. Okay, who just joined the team. So, for him that's a very complex work, right? So, see the work is same but two different people they are giving two different rate story points, okay? So, now he will tell the entire team to talk through this, okay? Decide, okay, and re-vote again. Okay. Now, this time the entire team came together and vote for this ticket as two. Okay. So, now all of them voted for two. After all of them mutually decided that they will they are going to vote for two on a mutual consensus, okay? So, then after that he will go here with the ticket, okay, he will now write the number two. That's it. So, that is how story point estimation is done. There are different games like planning poker and all, okay? They will play. Okay, they will send those links to the different because see, nowadays no all not all the members work in the same team, right? In the same company. So, all in the same place. Okay, so this technique planning poker is used. Okay, so story point is used for estimating the story level tickets, okay? Fine? Is this clear to everyone? The scrum master will facilitate the meeting. Every user story requirement is estimated. Estimation is done using story point. Story points are nothing but Fibonacci series, okay? Now, if somebody is saying this ticket is eight story points, that means it is very complex and there are a lot of unknowns in that ticket. Means nobody have done that work. Somebody is going to do that work for the first time. Okay? So guys, I have given you some real-time example. Okay? Here I see some questions being here. We need this material man for future reference. Uh so going forward I will be running this PDF or run books only with you. No problem. So this since this was my first class, right? So and with this first class it will take some time to get used to uh means uh this is the Agile topics is theoretical concept. I have all the documents with me. Don't worry. I have a lot of content with me to give to you if you want. Okay? So I thought of teaching Agile from PDF only. But in PDF things are a little bit differently written. Okay? It's uh uh little bit differently in a way it is written is written different. No worries. I'll give this. Okay. So this is what happens in sprint planning. So at the end of the sprint planning you can see that all the tickets in the sprint backlog have been estimated, right? Everything have been estimated. So all these Now this is two. Okay? This one also estimated at the pool. One. Okay? So everything should be estimated. There should not be anything which is not estimated. Right? So this is about sprint planning. Okay? What we can predict with story points? We can predict how uh heavy is the task. Right? If you If I see that this is story is five story points, that means that ticket is pretty heavy. Right? It's more uh complex. This more uh size of the ticket is more. And it is also little more lot of uncertainties are there. There's lot of risks are there to do it. Right? If I say this story point of this ticket is one, that means it is a very easy to do the ticket. Clear? You can read this guys. Okay? Story plan sprint planning. You can read this for a minute. Okay, then we'll move to the next point. Priority severity you know it have nothing to do with the priority and severity Shivani. Priority is from the ticket side. Like how fast you want to deliver it. Okay, irrespective of the story points, will the timeline remain the same to Yes, so see if if you're taking any ticket, right? Any story in a sprint you have to complete it within the sprint. So uh user story have to be completed within the sprint, okay? So we have to plan it in such a way that suppose I'm taking uh story is user I have assigned two stories to you. You should be completing those two stories within the sprint. So if you're taking a one very heavy story, then I will assign only one very heavy story to you. Okay? So that is the thing. Whatever we have planned, right? To finish it within the sprint, we should be completing it within the sprint. That is the sprint goal, okay? Next is sprint review. Okay, what is sprint review? The sprint review is another scrum event which happens on the Okay, Amul Jadhav, story points and tickets epics or bugs will be matched with each other estimates. No, epics and bugs epics does not gets estimated. See, some some companies they are not they are estimating in story points and some companies they are estimating the epics in t-shirt sizing like excel, triple excel, medium, okay? So story point estimation is separate. Epics get estimated separate. Bugs if you want to estimate, you can estimate them separately. Okay? So all the estimations have are separate, okay? So and they are not matched. They have nothing to do with each other, okay? So this is the estimation, okay? So epics are usually estimated in excel size like medium, excel, triple excel, small, like that, okay? So next is a review which is a very important event, and it happens on the last day of the sprint, but before the lunch. Before lunch, it will happen, and it happens on the last day of the sprint. And it's a meeting where all the stakeholders are invited. So, I told you, right? So, it'll happen on the last day of the sprint. So, when it'll happen? So, it'll happen on 16th January. So, it'll happen on 16th of Jan. Okay? And what will happen on that day? You will invite all the stakeholders. Stakeholders means anybody who is a part of the project, directly or indirectly, is a stakeholder, right? Right? Stakeholder means anybody who is involved with the project directly or indirectly is a stakeholder. Okay? So, PO is a stakeholder, okay? And the customer can be a stakeholder, or the engineering head can be a stakeholder. If it is a small startup, even the CEO can be a stakeholder, right? Anybody who's coming and asking you about the project can be a stakeholder, okay? So, you can invite all of them in the last day of the sprint to showcase or demonstrate what your team have done. So, what will be happen in this? The product owner should be present. His presence is mandatory, okay? Team comes, and they will give a demo. So, for now example, uh let me see what all other parties are. Harshitha Harshitha is there, right? Harshitha and uh have developed something, okay? Or somebody have done testing also. Anything, whatever they have done. Anybody It's not like everybody who have done something, they will come and they will showcase their work, okay? And the product owner will see their work. We'll see their ticket. If they have developed their ticket as per the acceptance criteria or not. So, once they will demonstrate that and give a demo, okay? If the product owner is convinced that this is as per the requirements, this is as per whatever the things are there, okay? Then he will accept the ticket. He will say that, "Okay, fine. I'm accepting the ticket." Otherwise, he will reject the ticket. Okay? So, he will see whatever they have done. If they have done as per the whatever he have haven't given the acceptance criteria, then he will accept the ticket, otherwise he will reject. So, what will happen to the rejected tickets? So, the rejected tickets will move to the next sprint. And the assigned team members will have to work on it. Okay? So, this event achieves continuous feedback. Why? Because even they're getting the feedback from the PO, they're also getting the feedback from the customer also. Even customer can also be a part of this meeting, okay? What if the tickets become different? If tickets are not valid for this project, which will not happen, okay? I will say what I understand if you are saying that bugs get rejected, that's a different thing. No, that is not uh bugs get rejected. No, tickets will not It will not get rejected. Bugs will get rejected, that's a different thing. But here uh tickets will not get different, okay? If the requirements will change, if your question is that, right? Then those new requirements will be taken up in the upcoming sprint. And these tickets will be accepted with whatever work has been done, okay? And the tickets will not become rejected, okay? Tickets will never get because those were some requirements, right? They will close the tickets with some resolution saying that this uh functionality is going to get changed with some new modifications. And they will link these tickets to those new tickets. They will not reject the ticket like bugs, okay? Then they will close these tickets. And then they will create those new tickets. They'll mention the same thing in the ticket, and they will link those those tickets to the new tickets. They are not going to reject the work because this is not a mistake of developer, right? This is the mistake of the customer only. I mean, right? Okay. Next is Last one is sprint retrospective. Okay. One more thing, guys. I'm going to copy paste on the same document. Just give me a sec. Yeah. Okay. Same Same thing I'm going to copy paste here. So, next and the last sprint event is sprint retrospective. So, what is the purpose of this event? It's like a reflection. What What all happened in the sprint? So, in this meeting what will happen? The entire team will come together and the scrum master will create a board. If it is a virtual, then he'll create a virtual board with three columns. Okay? So, first column will be what went well. Okay? What went well? Second column will be this one. What didn't go well? The third column will be for this action items. Okay? So, you know, the Suppose there are five people in the team. So, he will create five rows. Okay? 1 2 3 4 five rows. And he will go one by one and he will ask everyone. Suppose now there is Ramesh in the team. He will ask Ramesh, can you tell what went well as per you in this sprint? What didn't go well for you in this sprint? Okay? So, he will say that, "Okay, this went well. I did good here. Okay? I got support from this team member." And all. He'll say, "Thank you." and all that. He will also mention He will also mention that one of his ticket didn't get finished because there was a dependency on the team for this test data or something. And he couldn't finish his ticket because of a dependency. Okay? So, that is something which didn't go well here. So, the scrum master along with the team member will talk about those things in particular which didn't go well. And he will come up with some kind of action item, okay? See, we cannot just leave the things like that, right? Which didn't go well. We need to come up with some kind of process improvement activities and some kind of best practices, right? So, suppose now the team have a dependency of test data from some other team. So, now it's the Scrum Master's duty to lay an intake process with that team to have those test data dependencies already have in hand before you the even test start. So, he will do that. He will keep an action item on him, okay? This is one example I'm giving. So, like this he will go every team member you will ask, okay? And he will create this board on this table, okay? So, this is all about the sprint retrospective. Any doubts here? Let me know. Okay, so I got some questions on that giving me examples on action items, okay? And how the exam action items will be implemented, okay? What improvements can be done, okay? So, I just gave one example that, for example, one of the team members is saying that he could not complete his story because the test data support. Let me give one example. Suppose the team is working on an OTT platform, okay? OTT platform. Okay? What is OTT platform? Like some like Netflix movie and all those kind of things, right? So, there you have so to you have to suppose test some HD 4K content or ultra HD 4K content, right? 4K content, 8K content, right? So, what do you need to test all those content? What do you need? You need proper content, right? If you do not have 8K HD content, correct? Then how will you test? So, suppose all those content for your team comes from another team which is CMS team, content management system teams. Okay? On the day of testing or 2 days before testing you will requesting for the data and you didn't get the data for testing or development, because of which one of the ticket couldn't get completed. Okay? And this was raised as a concern during the retrospective meeting. Okay? So, now what the Scrum Master will say that we should not be asking these type of data like that in a chat or through some call. We should have a well-defined process with the other team asking for all these things even before our our work starts. Okay? Even before we start our work, our work means even before our sprint starts, we should also we should have we we should be already be having these kind of test data with us. We should not be asking these things in between our sprint, because this can put at our work at the risk of spilling over, right? What we have committed, because they may they might be busy, they might send you. So, we should have one one kind of process in place that hey, before we should be telling that team that hey, you should not be sending through chat or through email that you want this, right? We should be raising these tickets on their board asking that we need this type of test data and we should be letting them know that we want all these things before our sprint starts, because this is very important for us. Right? So, what what what whose duty is to create this process? Whose duty is to communicate with other team? Scrum Master's duty. Okay? So, it will be the action item on whom? On the Scrum Master to create an intake process with that content management system team to deliver the testing team and development team with the necessary data. So, this is the result of doing this meeting. Okay? Improvement and continuous improvement, right? So, guys, see, Ronaldo is the best football footballer, right? Even though if he's the best footballer, he need a coach. He still need a coach. Okay? So, Scrum Master will act like a coach. He will work with the the and everybody it is his duty to make this meeting very effective. People should come and talk. If everybody comes in this meeting and do not talk, then this meeting is not going to be of any use. Okay? So, this is the This is the point of having this meeting. Let me clear this. Okay, guys. So, right now you can see that I have put some action criteria for login requirement. You can go through them. Okay. Now, issue types in Jira. So, there are many some issue types in Jira. There are some three to four. One is epic. What is epic? Okay, yeah. So, epic is a big functionality, as I have mentioned here in the picture, which can be completed in more than one sprint. Okay? So, if you go to Jira, right? And if you see create, okay? If we come to work type, these are the work types you can see, right? If you go to any project, you can be seeing these work types. Epic, task, story, feature request, right? Epic is one of them. So, epic is like a bigger piece of functionality. Now, let me give you one example. So, there you can create an epic called as account and registration. Okay, account and account and registration. So, what all can come in account and registration? All the login, okay? All the account creation, registration, all those tickets will come in this epic. Okay? So, when the epic, okay, have multiple user stories which cannot be completed in one sprint, okay? We will go and create an epic. So, epic will have lot of user stories and that can go for two to three months completion also. Okay? And it will have some bugs also, guys. Okay? Epic can have bugs also. Fine? So, I'm taking a little story so that you understand. Okay? I can talk very fast also and pauses, but uh that will make you confused, okay? So, now you understood what is epic. Epic is nothing but work item, a type of work item in Jira, okay? Which is used to create which is used to create or which is used to implement the bigger feature functionality. Okay? And it will have a lot of user stories in it. It will also have bugs in it. Okay? What is user story? Now, that is simple. Okay? So, yeah, as you can I'm slow only, dear. If I go further slow, then, you know, we will not be able to complete the entire course in just 43. You know, so I'm slow only. Okay? So, let me know if anywhere you are not able to understand. Uh last 15 minutes we'll do Q&A. Okay? Some polling and also. So, you can ask me questions, okay? I understand guys from your point of view, but there is so much information. Okay? We'll I'll be teaching you all the things which you need actually from your YouTube standpoint view. And to be completing from your basics. Okay? And uh don't worry about it, okay? Let me know anything which you are not able to understand. Okay? Rest, it's all simple theory today. Whatever is just theory only. Nothing much technical we have done, okay? So, don't worry about it. Next is user story, right? User story has already seen, right? I created one user story. You see, epic can go more than one sprint, right? It's like a bigger umbrella. So, you can remember this. So, this is the umbrella, right? This umbrella will have many user stories. Right? Right? Okay? Right? So, epic can take more than a sprint to complete. In any interview, if they ask, you have to answer this. User story is a small piece of functionality which is completed in a sprint time, right? How to write the user story like this? I have already shown you. You can see this. Okay? There you will write your user story like this. As a user story, okay? as a user I want what you want so that the benefit. Okay? So, this is the format. As a type of user, what you want to do, that is a feature, so that what is a benefit of value you're receiving. I've given some examples, please go through this and that will complete the user story format. Very simple example, as a customer I want to view my account balance so that I can know how much money I have. Right? As a e-commerce website, want to buy this so that I can do this, right? I've already written one simple one for you. Okay, I'll repeat it, no problems. Epic is a bigger piece of functionality, okay, which will have lot of user stories inside it. So, suppose something you're going to implement which you cannot implement within a sprint, so you can create an epic and you can create multiple user stories into it. For example, you can create an epic account and registration and you can create all the tickets related to account and registration and login and Okay? So, that is epic. What is user stories? User story is a small piece of functionality which is completed within a sprint time, okay? Within sprint time means 2 weeks time it will be completed. That is user story. Who can create epic? Usually the product owner will create the epic. Okay? These are the few examples of user stories I created. Okay. Next one is task, okay? So, what is task? Task is a small unit of work. So, suppose uh epic and user story were related to functionality, right? So, epic and these two, 1 minute, let me show you again, create, right? Okay. Epic and story were related to the functionality, right? A requirement. Now, task is something related to non-functional non-feature work, okay? Suppose now if you have created some KT document, okay? Or of or if you have designed an automation framework, okay? Or if you have uh you did some or you set up the test environment, uh start up the test environment for your testing, right? Anything you have done not related to the uh testing work, okay? That you can actually capture in the task, right? Okay? So, you should be capturing everything, right? In Jira. So, for that we have the task, okay? Yeah. So, this is the task. This is the practical thing about the task. Okay? And that is what I have mentioned here in the book, also. A task is a small unit of work. For example, setting up test environment for performance testing, test data, getting KT, etc. Okay? And bug Bug is nothing but defect. So, bug is nothing but if you get any issues or defects in your application, you're going to create a bug for it. Fine? Okay? So, guys, this is all about the Scrum. Okay? Now, I have completed this. So, there is uh uh demo here to create a Jira account, okay? I'll show you how to create a Jira account. Okay? And uh there is some practice here creating a backlog, creating new issues, editing the sprint. That I'll show you how to do, and you can do it tomorrow. So, let me show you how to create So, for that I have told you, right? Go to Atlassian. Jira Premium, right? So, this is the website. Pinging you all. Okay? So, you have to click on try it free. So, I will say sign in with a different Atlassian account, okay? Start a new site. >> So you can use any Gmail account, okay? Okay, so this is your Gmail account. So you're seeing, right, guys? How I'm doing? Same thing you have to do. In the lab Jira is available. I'll I'll show you how to access the lab, okay? Come here. Go to practice labs. You can do here. Go to practice labs one. Click on the practice lab. Okay? Launch lab. Launch lab. It will take first time. Like 4-5 minutes it will take for all of you. I have already launched the for me it will take a minute or two. For you first time it will take 4-5 minutes. Okay? So once this is done, you have to click on this RDP access. And then Oh, you have to close the previous terminal, okay? You have to again click on the start instance. Okay, sometimes some problem happens. So see again it has started, okay? It will start again. So just wait. I'll show you again here on my screen, okay? So now it will say upgrade now. So I'll create click on upgrade now. Jira is getting set up. See, your premium trial has started. Okay, it is a free for 30 days. For 30 days you can enjoy the premium free Jira features. Okay, you can practice, you can do whatever you want. If you go in any company you'd using Jira, so we can do enjoy this feature. Okay? So then I'm closing it. Fine. So this is guys, no billing, nothing required here. Jira will Fine. This is screen. Okay, now you come here. Can you see Jira is here? Click on this. Okay. It is saying create space. Space means a project. Now little bit the name got changed. Already I have created one project here. Can you see? Panther. If you want to create a new project, you can create here. It's saying create space. Okay, let us I will show you how to create a new project. Okay, so you have to choose software development from left hand side. Which framework you want? I want Scrum framework. Use template. Again it is asking what which you want, company managed, team managed. Go for company managed. Give a name. >> Can I write company? manage then next Okay, see Jira space successfully created. Bring your team along. If you have any team members, you can write the name here. I don't have any team member, guys. I'm skipping it. This is just simple demo, right? Can you see? Home board came up. Can you see? This is the board. I have another project also, Panther. This is a company managed. Okay, backlog is empty. No, nothing is here. Active sprint, any sprint which is active, you can see here. Nothing is active. Okay? Fine? Now, let us create some ticket. I already showed you how to create a ticket, right? Now, please try to do a small demo now. You have 10 15 minutes left. You can try installing this, okay, setting up this Jira Cloud on your systems. You create some tickets, which I have already shown you how to do that. Okay. Okay, now let us create some ticket, some dummy ticket. Okay, it's already created. Okay, I'm not going to create one more ticket. So, this is my Panther. In Panther, let's go to backlog. In Panther, nothing is there. No problems. I'm going to create some dummy ticket. This is a story. So, this is like search feature. Okay, search feature. Fine? I've just written a very simple story, and this suppose I am See? Here, already sprint is created, right? So, how to create a new sprint? From this icon. How to create a new sprint? From this icon. Okay? See, one more sprint have come, right? If you keep on clicking, it will keep on adding sprints. This is your first sprint, maybe. Okay? So, you can add the how many weeks it is. You can add start date, whatever it end. You can drag and drop that. And you can start the Suppose now I'm adding this to first sprint. Move to sprint one. Came. Now, let me close this, guys. Right? Now, you can start the sprint by this option. See? Right. If you click on start, the sprint started and the that ticket came in active board. Can you see? This is how it happens in real time. You will not be doing all of this. Sprint from master will be doing. Product master will product owner will be doing. You'll not be doing, but I showed you because yeah, that was a part of the lab Jira. I didn't see it. What is happening in lab Jira? Let me see. Okay, it have come up. So, lab Jira have come up now. Please give demo on the lab. Same thing on the lab. I'll show you. Go here. This will open up. I'll show you how to So, I'll just show you how to open up this this basic things. You'll get like this. Say okay. And what happened environment like this? So, this the Internet Explorer. Double click on this. Okay. So, the lab is little slow. If you want to do it on lab, very nice, please do it. Actually, you have to do all the things on lab only. Okay. So, be very much used to with of using labs already, okay? You can see here, guys. Can you see? You have to pass In order to open the Chrome, you have to pass some password. Please, whatever password you're entering, remember it forever, okay? Whatever I'm passing, I'm remembering it. You write it down and don't forget, okay? See, now Google Chrome have come up. Same output or not? Same thing here also, you have to do same thing, guys. I'm not going to show going to show you the exact steps here again, but I showed you. If you click on the Google Chrome, this will come up, okay? See, this have little bit of connection issues. And I showed you how to connect, okay? Yes, that's how the lab is, but you have to use the lab. They came in the lab. After coming to lab, you have to click on this this icon. Can you see this icon? This is Google Chrome, okay? Understood? Once you have clicked on it, you will ask some authentication, right? You please click on that. Put some password, whatever you can remember, and don't forget that password. This will take some time. It is laggy, okay? It's slow. Yeah, it is always like that. That's why I've shown you all the steps. Okay, here also you have to do the same thing. Here also you have to do the same thing. You have to type Atlassian. Right now, nothing is working. All is getting stuck on my screen. See here, some problem there. Please do it, guys. Now you know what to do. Okay, please do yourself. 9 minutes is there. Do a small demo yourself. See this up collection problem for me, okay? Here also you can see application. Okay? We'll do software. Here sign up option is there, right? With Google. You can try this and you can move forward. Okay? The Google Chrome is not updated here and that's the reason the same UI is not coming as you were able to see in my UI, okay? Only difference. Guys, I'll show you once again, okay? I showed you I think multiple times also. I'll show you once again. I opened the Google Lab. I showed you this one, right? Once you open the lab, this is where you have to open the Chrome, this one. Can you see this earth symbol? This is the Chrome. This is the Chrome. >> [clears throat] >> Below this red this is the Chrome. Click on this, okay? How to open the lab itself? Okay, I will show you, okay? I'll show you, don't worry. I'll show you. So, there is practice lab here. Can you all see this? Okay, can you all see this practice lab? Can you see all of this? I was doing this I think all of you you didn't uh see me doing that before? I thought you guys followed me that time. No problem. Click on practice lab, okay? You will get Okay, in your distance cheat book you might have got in your learning tab one minute, in your learning tab you would have got lab guide, this one. Lab guide. Lab guide. Right? You can even You can even click on this lab guide and see what is there. Otherwise, directly come to practice labs. Okay? Click on this launch lab. Okay, launch lab. See what I'm doing now. Please see the screen whatever I'm doing. Okay, I did this before also, guys. Okay? If it is lagging, you have to do it again. There is no other option. Okay? If it is something coming, you have to terminate the instance. You have to start the new instance, okay? Fine. For me also it is taking time now to open, right? It is lagging, it will take time, okay? Don't worry about it. Yes, if you have some doubts, there is a lab document also that you can see. It's very simple. You just have to wait until it the icon appears. There is a lab document lab help document, you have to refer that. Okay? Please do refer that. All the steps are mentioned there, actually. Everything is in it. Sometimes it will be When you see the screen coming up, in that case, you have to wait Stop the You can click on this. Okay? RDP access, and then you have to click on this this icon, this one. This pointer arrow. Can you see pointer arrow? Open a new tab. Can you see? That's how this opens. Click on RDP access, and then that pointer arrow, and then you have to see, "Okay." Right? Then you get this. So, this is the screen you got. Now, in this screen, right? This is your uh what? Virtual lab, right? Below the red, there is an earth-like symbol, that is the Chrome. Click on that, you'll get a prompt asking for some password. Put the password as your you know, your uh what? Any password which you remember. But don't forget it, okay? So, as an interview point of view, what can be asked about the study sessions? Example, Agile methodology. Yeah, I will talk about that. Yeah. So, uh from the interview point of view, okay? So, uh we they can ask about the Agile methodology, right? So, what can be asked from interview point of view is uh they can ask about Agile frame What is Agile? Okay? So, from an interview point of view, interview questions can be like First question can be, "What is Agile?" Okay? And uh they can ask about and you can answer uh what is Agile and you can also add what about Agile any manifesto. Okay? To get some added uh weightage to your profile. Okay? So, if you can talk about a Agile manifesto, they will think that you are more matured as a candidate who knows more about your Agile. Okay? And uh What are the other questions they can ask about Agile frameworks? Okay? In Agile frameworks, they're asking mostly about Scrum frameworks. Okay? So, in Scrum frameworks, what all can be asked that I'll mention here. They can ask about um what are the the Scrum roles. Okay? They can ask you about the Scrum team size. Okay? They can ask you questions on um Scrum uh ceremonies which I discussed yesterday, right? Uh what are those? They are uh so, I'm I'm kind of also summarizing about yesterday's class. Okay? So, I'll come to all the questions which I've been which you have asked me now one by one. Okay? So, one by one. Scrum ceremonies. What are they? They are daily stand-up, DSU means daily stand-up. Okay? Fine? Then, they can ask you about you can backlog refinement. In backlog refinement, um they can ask you when does it happens, who does it, okay? And uh what happens in backlog refinement, when does it happen, who attends it. Okay? So, when I'm writing about this, all these things can be asked. So, backlog refinement, okay? Everything they will ask. Sprint planning. In sprint planning, a of questions can be asked so that I can tell you now. I will break down this later, okay? Sprint planning, they can ask you about sprint review. They can ask what is the purpose. So, about all of these things they can ask what is the purpose of all these, okay? What what what is the advantage of sprint review? What what So, you can say that sprint review the advantage of sprint review is continuous feedback, right? When you do a demo in sprint review, what happens? Happens on the last day of the sprint. And the team members do a demonstration of whatever feature they have worked on, right? And during the demonstration, all the product owner, the customer, the engineering lead, everybody, they they are present, right? And when they give a demonstration of whatever they have worked, right? Everybody sees what they have worked, right? So, they give a feedback whether the product, whatever the feature the whatever the team have built, is as per the customer's expectation. Whether it is as per the acceptance criteria of that user story or not, right? So, this gives cuz this this gets a continuous feedback, right? This gives a feedback on the feature or that user story, right? Now, if the product owner is not as satisfied, right? Or if that user story have not been developed and tested as per the acceptance criteria, then he can reject that user story, right? And then the team have to work on it consecutively in the next sprint, okay? So, this is the purpose of the sprint review. So, it uh it gives a continuous feedback, okay? And uh the user story can be accepted or rejected depending upon the observation of the product owner and the stakeholders. Now, a stakeholder is something who can be direct whom or indirectly associated with your project. It can be the customer, it can be the engineering head, right? I told you, right? If it is a small startup, it can be the direct CEO also can come and sit and see what you have developed, right? It is a sprint review. So, these are important questions, okay? So, if you're a fresher, they will expect you to do this, okay? They are expecting you to know and understand what happens in each one of these. You have to You have to tell, okay? You have to get prepared and you have to go fully prepared on all of these. Now, sprint retrospective. Sprint retrospective, any another last important event. So, sprint retrospective, they can ask you questions. What is the purpose of sprint retrospective, right? So, sprint retrospective is the last event. Again, sprint review and retro, both happens on the last day. So, sprint retro happens at the second half after lunch. And this is the last event of the sprint. During this, what happens? The entire team comes together and they discuss about the sprint, okay? It is like a reflection, right? Suppose you gave an examination and examination results came, right? And when the results came, you succeeded in some of the papers and some of the papers you got failed. So, you took a diary and you started noting down, you started reflecting back where you succeeded, which area. Suppose you failed in algebra, right? So, you would write that, okay, you you didn't you didn't prepare that section well. So, you have you you failed in that area, right? So, next time when you're going to again appear for that exam, maybe you need to go for extra coaching, right? That is the action item on that, right? Similarly, sprint retrospective is an inspect adapt of the sprint, right? So, in sprint retrospective, what happens? As I told you yesterday, I'm just going to summarize, right? What happens? The scrum Master will facilitate and the entire team will come together, right? So, they will create a board. So, if the team is virtual, meaning all the team members are sitting across geographically distributed area. So, once when I was in COVID, I have team members in Pakistan, in Poland, in US, right? So, everybody was at different different places. So, I used to create a board and there was this um wonderful there was this one um idea board, okay? I'll show you that also to you, okay? So, there is this idea board. I don't know if it still exist or not. Yeah, can you see? Okay, so I used to create a board using this. Okay, so this is an online platform. So, see, it's beautiful, right? So, create my own board. I'm showing you what I used to do really, okay? So, I was a Scrum Master at that time. So, I don't directly become TPM. I served Scrum Master for some time. And then I became TPM, okay? So, create my own idea create my own idea board, right? So, you will create like you can say that uh sprint uh you know, sprint you know team aster laptop, right? Something like that. Okay? And description would be this retro retrospective. So, in what format you want to with three sections, right? Section will one will be, right? What went well? Okay? Next, what didn't go well, right? And then action items, fine? I'm not a robot, you have to do this and create. Can you see? What happened? So, it will create. Can you see? Like this it will come. What didn't go well and action items so on. Okay? I think we have to log in. Why don't I create it? Okay. Okay. In sections. What went well? I think if it is not coming then we have to create an account here. What didn't go well? An action This is the actual This is the board like that it will come. Okay. So suppose one person want to say, he can create and he can start writing. Okay? I get help from Kathy. Right? Appreciate. So this is real time, right? Then what didn't go well? Okay, can't complete my user story. Everybody clear? Due to dependency on test data. Like that. An action item. Same thing. Clear? Got it? And then action items are sticky notes. Okay? And the wonderful part of this is that you can even export it as a PDF. Okay? So these are different tools. Okay? So if you you can go to the any company, they will use I'm not saying this is the only thing. You will get many different tools. Miro is there. Okay? Right? Okay, next question is that What do you do in Scrum here? So does manual testing work? I'm coming back to interview questions now. Fine. So this can be asked. Now there can be some specific questions on sprint planning. Okay? So specific questions on sprint planning is how is it? What is your role in sprint planning? What's your role in sprint planning? Okay, I'll give answers for this also. So, your answer should be that uh okay, your answer should be that I participate in sprint planning by first by you know uh by uh understanding okay, the entire uh story. Okay, when the sprint planning is going on the the Scrum Master is facilitating the event, right? So, he first read out the ticket, right? Yesterday uh we saw we saw, right? What is the ticket? What is the user story? I understand acceptance criteria. And then I try to understand the complexity of the user story. I try to understand the size of the ticket. I try to understand whether there are unknowns in the user story, right? And then on the basis of all of that I tried to uh I tried to estimate the user story on the basis of the story point, right? Because story point is the story point is the way of estimating the user story, right? So, story point is the way of estimating the user story. Correct? So, story point I will estimate. And they are then they will ask then they can ask further questions, right? So, what is story point? Okay? So, you can say that uh our Scrum Master is using some uh sprint some techniques like planning poker and all those things. I will I will do my estimation, okay? And uh based on that estimation uh other teammates will also estimate, okay? And in case my estimation is very high or low, right? My Scrum Master will ask me my perception whether uh it is why you I have given given this estimate. Then I will give my uh thoughts on that, right? Why I have estimated higher or low. And based on that the entire team will again give their uh you know, discussion, right? And my team will give inputs whether I'm giving higher or low. And based on that we will collaborate the entire team will collaborate. And suppose I'm saying this user story is very high for me, the team will help me, right? In telling that old should not be Suppose I'm fresher. Now, for example who is that So, let me tell somebody's name. Okay, now for example, Kazim is telling that some user stories eight story point for him, which means it's very complex for him, right? So, Kazim is maybe fresher in some team. Then entire team will come and help the Kazim. No, no, no, it should not be eight story point, right? Because Kazim have just joined the team. He's a fresher. So, for him complexity is more. Yesterday, what did I tell you? Story point is the combination of story point depending on three things. First is complexity of the ticket. Right? Understand? Always remember complexity. So, never ever tell that story point is number of days. If you open your mouth like that in any interview, gone case. I have taken many interviews. I forgot to tell you in the introduction that I'm also a part of many interviewing panels. I work with many interviewing companies. Interviewing companies as in like there are few companies which are which are only only taking interviews. Like I'm interviewed.com, Risebird, right? Codewars, uh Codility, I don't know. So, I'm a panel there. I do take a lot of interviews of automation developers, Java full stack, Python full stack, and all. So, you know, I have taken interviews of even senior people. When I ask them, "What is story point?" they say, "Ma'am, story point is days. One story point is one day." Right? So, what I have seen is that people of my years of experience like 15, 16, right? Because when I started working in 2007, that time there was no Agile. I'll tell you, okay? We we work in V model, waterfall model, okay? At that time the world was little simple. World started changing after 2013 and 14 only, okay? Now it is altogether a different thing. Now there is Docker, Kubernetes, AWS, uh Azure, AI, what else? Right? Copilot, everything is there. So, now that time little it was slow world, okay? So, that time the projects were still working on waterfall model, V model, world was a little simple, okay? So, people are very still of that mindset that they still that time work was still estimated in days, right? Now, if I go and ask a builder in how many days you're going to complete building my house, right? Suppose I'm building my house in Bangalore. Okay? Fine? If I ask him estimation, in how many days he'll build my house? So, what he will say? "Madam, I'm going to complete building your house in 6 months. 6 months project, right?" Like that, olden days. Olden days means in 2007, 8, 9, like that. In other models, SDLC models, like V model, waterfall models, okay? The estimation of work, okay? How much time this project will be completed, okay? How much time this website will be completed, how much time this application will be completed. They used to tell that it will take 1 year. Okay? Time was estimated or effort was estimated in man days or hours, okay? But now in Agile, there is no concept of time in hours or days. Yes, great, okay? So, in any interview if you're going, never say that one story point is one day, two story point is two day, never, okay? So, story point have nothing to do with the day, okay? Kazim can say that, okay? Kazim can say that, for him, particular user story, he can complete in a particular user story is five story point. I'm just saying. One story is five story point. At the same time, same story, user story, Aishwarya, who's a senior senior lady in the same team for the same for the same user story, Aishwarya can take two story points. Try to understand this. How? Why? Why? Because Aishwarya is senior senior but senior person. Okay? And this Kazim is a fresher. Okay? So, for Kazim, the complexity is high. Right? He just joined the team. So, he needs some time, right? The complexity is high. Okay? And the size of the ticket will also be high, right? Correct? You'll do everything for the first time. And unknowns Unknowns means he like lot of things. Risk means first time he's doing, right? That'll also be high. Correct? Okay? So, what I'm trying to show you is that for the same user story, Kazim can estimate more story point, and Aishwarya can estimate less story points. So, this is the beauty of Agile. Complexity is measured by the user story, but it is measured by the person who is estimating it, not by Shalini. Okay? Complexity is measured See, every user story effort estimation is done by the user, not by the user story, right? Okay? Agile tells, "What is your effort estimation? Your Shalini's effort estimation, not the user stories. Okay? You have to give your effort, okay?" Even senior people who are 15, 10 years of experience, they don't have understanding, they make mistakes in interviews, okay? When they do these mistakes, they get rejected in an interviews because this clearly show their lack of experience in understanding Agile concepts, okay? So, these are very basics, uh but very very fundamental. And if anybody is saying that they know agile, right? Uh They should know all these things. But sadly, people don't understand all these things. Okay, they are just doing agile, but being agile is different. Okay? Fine, so I think you understood this, okay? And when you do the sprint planning, this thing can happen. Kazim can say it is five, Ashwarya can say it is two. And when that sprint planning is happening, then Ashwarya will tell Kazim that, "Hey, you know, you can do like this. You can do like this." So, Kazim will understand, "Oh, okay, okay, fine, fine, okay." Then again, second third round, again when the voting will happen, what will what will do what will happen? Every team will vote and then they will come to three story point, right? So, now on a mutual consensus, right? The entire team will vote for three, okay? Yes, sure. I'll give you the note for story point again, okay? Did it have the definition of story point? So, now you got it, right? This thing can be asked how the sprint planning is done, okay? You have to tell like this. They can also ask you questions like, okay? That on what basis you will go and first you will decide what is a story point. So, you can tell that initially when you're joining a team, right? You will ask your colleague how the story point are assigned. You will see some reference tickets, right? Like how the story points are being done. So, you will ask a scrum master, okay? Always in every team, there will be some reference tickets. Like this ticket is one story point, right? So, this ticket is two story points. You'll get some ideas, okay? Being a fresher, you will not get the You will be They can ask you, okay? On what basis you are taking as one story point initially when you're joining the team, right? That time nobody is telling, right? This is one story point. So, then you can tell that, "When I'll be joining the team, at that time I will definitely I will not be knowing, right? About the estimation thing and all. So, I will be asking some of my seniors, okay? And some of my Or you can I will be directly approaching to this Scrum Master. Okay? And I will be learning how what is the how they are doing the referencing, how they are creating the story points, right? For what like one one story point tickets I will see, two story points ticket I will see, right? So, I'll gather some idea like that. Okay? Then I will learn. Okay? What is the story point is, okay? Then I will slowly gather idea, okay, this ticket is one story point, this ticket is two story point. That's how I will learn. Okay, this all this question can also be Okay? Right? So, like that you have to So, these are some of the questions, guys, they will ask you, okay, on on sprint planning. They can ask you how do how the sprint planning happens in your team, what uh the tools that do you use, okay? You can say planning poker that the sprint that the Scrum Master is okay is using, okay? And all these things. So, planning poker is one kind of nothing but it is a kind of a kind of a link, okay? It's a kind of a tool which the Scrum Master uses. He will send a one link, it'll get generated, and he'll send that link to all the team members. Every team members will vote on that uh you know, on that particular user story, and that unanimously whatever each person will be getting that number, it'll be reflected on the screen, okay? Every person's name and their respective user story. Okay, Dileep Kumar, what elaborate on story point? Sure, I will elaborate. So, story point is the combination nation, okay? Of 1 minute. It is a combination of I will write that again here. Story point is the combination of complexity, size of the work, and unknowns, okay? So, always remember that, okay? Story point is a combination of complexity of the site of the user story, how complex is the user story, right? For instance, suppose if your if your user story is based on artificial intelligence, okay? Then And is very complex. Right? It's very complex, right? So, that means something very difficult you're going to do. So, you will estimate it more. Size of the work, that is a very heavy work. Suppose now you have to do it for one full page, right? Some heavy UI work you're going to do or anything. I'm not just giving it a reference, okay? Then it will be you will put more story point, right? Unknowns, lot of Suppose something you're going to do for the first time. So, there will be lot of uncertainties in the work, right? So, lot of unknowns. So, you're going to put more lot of unknowns in the thing, okay? That is unknowns. So, that is story point, right? From interview point of view, from work point of view also this is important. Okay? So, I think I explained everything and retrospective and and review, I think you already got it, right? So, these are the things. And what else? Yeah. So, this this is the thing, okay? Yeah. So, idea boards you have already seen. Okay? And next uh what Okay, so next we are going to talk talk about how Agile methodology helps in software testing. Okay? So, we are going to talk about uh Agile in software testing, okay? Agile in software testing. Okay, next question was again coming from Kazi. Does manual testing any any advantage over over automation? Yes. It have got lot of advantages over automation, right? Right? Um yes, it have got lot of advantages. Okay? Manual testing over automation. Lot of advantages, right? What are the advantages, right? So, suppose now I'm testing Myntra application. What is manual testing first of all? What is manual testing by your own hands, right? Suppose now if I'm testing this What is this? Uh suppose I'm testing this Myntra, right? If I'm testing Myntra, in Okay? By What is testing of Myntra? Suppose I go to Myntra, right? I go to kids, okay? And uh I go to some dress, okay? I like this dress, right? And I add to bag. And I choose some dress, add to bag. I go add it to bag. I go to bag, okay? And then I placed order, okay? I Okay, I'm not able to log in now, right? And I does this Yes, correct. And I placed an order, for example. Just Just assume that I placed an order. I got a order confirmation. I think everybody is doing some I think I All of you have placed an order. Yes or no? On the e-commerce side? Somebody All of you might have done that, right? So, this is manual testing, right? Verify whether order have been placed or not, correct? Now, what if if I have placed the same order using using Selenium? What if I do the same thing using Selenium script? How wonderful it will be? What if I if I place the same thing using Selenium script? It will be good or not? Great. That's what you guys are going to be in another 1 and 1/2 to 2 months, right? Yes. So, what what will do? Suppose um I washing clothes with my own hands. How is that? It will take time. What if if I put my clothes in washing machine, sit back, relax, and I'm taking class now? At the time I finish my class at 10:00, right? And my clothes will be already washed in washing machine. I just have to dry it out, right? So, that is automation. Okay, now there is artificial intelligence also. Correct? What is artificial intelligence doing? Artificial intelligence is also automating your Artificial intelligence is also automating your code also, right? You might have seen that many jobs are going due to artificial intelligence. Why? Uh these HR jobs and all, right? I don't know if you if you have seen that. Correct? Correct? So, that is AI, okay? I'm not saying I'm not scaring you away, but So, might have seen that many junior developer jobs are going, right? AI is simply writing the code, right? You do not need to write the code. AI is writing the code. Correct? So, that is automation, correct? You do not need to direct with your own hands. AI is doing the work, okay? So, that is automation, okay? Where you are not But now, guys, so what is automation? Automation is faster. Manual is Manual is takes time. Slow. Okay? Manual is slow. Automation is fast. Okay? Automation is fast. Fine? Now, guys, okay, one more thing. Manual is error prone. Okay, now, suppose I'm tired today, right? As I told, I'm sick today, okay? Suppose I'm dizzy. I am Suppose now, I'm driving a car. I'm not feeling well. Okay? What can happen? My concentration can get lost, right? Or I can I can execute a wrong script or not? I can do mistakes and I can execute some script wrongly or not if I'm having a bad headache or something. That can happen or not? Yes or no? Okay? So, that is error prone. If you're not feeling well now, you might have heard of many airplane crashes where the pilot was tired, okay? And you might have seen many reels on Instagram where the driver was sleepy and he took the car and get crashed. Okay? So, manual test manual testing is error prone if you are not feeling well. Suppose today I'm not feeling well, okay? I have taken many medicines, okay, and I'm not in that condition to run the class for 4 hours. So, I'm taking class only for 2 and 1/2 hours. But suppose if now automated video was there, right? Video if you play, it can run all night also, correct? So, manual is error prone. Automation is not. Okay? Next is what? Manual is There are some advantages also. Okay? Manual does not takes time for training. Okay? So, theory does not takes time for training. There is no training required for such manual things, right? You don't need to train time for the people. Just need to know the domain knowledge. Okay? On the other hand, contrary Okay? For your automation, you guys have to be trained. See, all of you are here for learning automation. See, now you're learning Agile and all. That's a part of building up your knowledge for automation, right? Okay? But automation needs specific training. Okay? But automation needs investment. You're all investing money. Okay? And time. Right? So, here manual doesn't need any setup. No tools required. Okay? But automation needs the time. Needs setup, right? So, these are some differences, okay? I hope that answers your question. You cannot do automation without manual testing. Okay? You any So, one more thing, guys. Can you do automation? Can you directly automate any application? You cannot directly automate. Which type of application can be automated? Which type of automation Which type of applications can you automate? You can automate This is one interview question. Which is which is asked in interviews. You can automate only those applications which are stable. Okay? Any application which is not stable, you cannot automate. Okay? And any application which you're automating, definitely you need to manually test that. Okay? Definitely, there are some ISTQB Foundation last chapter. This is the This is the last chapter definition, whatever I have put. If some of you are asked to give me certified, this is what will be there, okay? So, definitely automation is now a boom, but you cannot underestimate manual testing. Okay? So, this is the thing. Fine. So, now let's now go to our now our class, okay, guys? And we will move ahead, okay? And we'll move ahead with our with our next agenda, whatever is there. I hope till now whatever I taught is clear to all of you. Okay, next Today we are going to see This is our Today we will try to see how analyze We will see how Agile helps in software testing. Okay? How testing life cycle happens in Agile projects. And how Agile fits in the testing ecosystem. Yesterday we did the basic of Agile. Today we'll see how Agile helping us, okay? So, we'll see that. Okay? So, let me know if you have doubts and everything. Today I hope my this is everything is good. Okay? And I already told you, right? What is the beauty of automation? Okay? Automation comes into picture where you have to do regression testing. Okay? Regression. Regression. This I think told you or not yesterday? I take many webinars for many organizations, okay? So, suppose, okay? Do you know this Alibaba? How many of you know about Alibaba? He's a big very big entrepreneur of China. Okay? So, yeah, he is a big man in China. So, he he had said one thing that it is not who brings what to the market, but it is the one who brings fastest fastest things to the market, right? Now, Tata Sierra have come to the market. How many of you have seen Tata Sierra? Okay. Do you like it? It's a huge vehicle, right? I saw it I saw it day before yesterday. It's a huge vehicle. Yes, it looks like Defender. Yes, but it's too big for five people, right? Yes, I liked it too, but it is too big for five people. Okay, so yes, they have given it absolutely very big vehicle, especially tires and everything are too big, right? And I'm very sure many people have already booked it, right? And it's an amazing vehicle, right? So Tata have given up something very good in the market now. I think everybody they have Now I was asking that person in the showroom what's the sale going on for this vehicle? Then the person was saying that it's amazing. Now we are not able to even give people, you know, the vehicle. There are too much bookings happening for this, okay? And you know what? Because there are so many features in this vehicle. Why I'm telling this example? What is the point of telling you here in this test right? Because you guys need to know about all of these things because finally you're going to be in some projects, right? And you have to look at the bigger picture. Why? Because they're bringing something into the market which nobody had I have told one thing, right? You should bring something faster into the market. So now you might have seen guys, right? That every time Apple iPhone brings something into the market, right? Every September they come up with something, right? Okay, now next September also they will be bringing something to the market, right? Now there are competitors which are already competing with Apple iPhone or I don't know something, right? Instagram is there, WhatsApp is there, so many things are there, right? And who wins the race? The one who brings the things fastest. Now how can you bring the things fastest? In Agile things are developing in two weeks. Right? Two weeks. Now the application is growing very fast. Correct? Fine? Are you with me? So, if the application is growing very fast, that means that test cases are also growing. Okay? So, now if the test cases were 500 in January, then by December, the test cases can become 2,000. Yes or no? What are test cases? Test cases are nothing but they are related they are they are related to the requirements. Test cases related to the requirements. That's it. Clear? So, suppose now suppose if I have to if I have to release something to the market in 2 weeks, and I have to do the regression testing for 1,000 test cases. Okay? Now, if you don't understand regression testing, that's fine. I'll teach you what is regression testing. So, just imagine that if I have to do the testing for if I have to do the testing 1,000 test cases in 2 weeks, how can I do the testing 1,000 test cases in 2 in in 10 days? Is it possible to test 1,000 in 2 weeks by two two testers? And I do testing 1,000 test cases in 2 weeks by two people. Is it possible? No. Then how can then how can I do that? Only if we have automated 2,000 test cases. Right? So, that is no not by AI Dileep Kumar. AI will not help. Okay? Automation will help. Okay? That is why you all people are here to learn automation. And that is why there is a boom there is a demand for automation developers in the market. Okay? I am I am a as I told you I'm a corporate trainer. I'm also associated with not only with Simply Learn, I teach for Edureka, I teach for QSpiders, I teach for StarAgile, I teach for multiple platforms. Okay? I I also teach directly with the corporate companies also. So, I see lot of people are coming for learning automation. And I have seen learners coming from backgrounds like I have not taken your introduction, okay? But when I take class, I I do take introduction from learners also. So, when I take introduction from learners, so they tell me that some of them they are coming from backgrounds like village panchayat, some of them they are dentist, some of them they are recruitment background, some of them they are from you know backgrounds like HR, some of them they are from fitness background. So, you can imagine, right? People are coming from XYZ backgrounds. We they are they are nowhere related to IT backgrounds, right? All of them they just want to learn I you know automation and they want to uh start a career here. There is so much demand for automation, okay? So, why? Because we want to release things faster into the market because if things are getting released faster, people will use them, the revenue will increase, the product will get a good report. Okay? And there is a brutal competition in between the products, right? And if you don't bring changes faster into the market, then you will not survive in today's world. You take any any any kind of product, right? You can see that a lot of changes are coming. If you're not bringing changes, you're gone. And that is why Agile is there to support that. And Agile supports automation. Both are related. I hope it makes sense today much sense, right? Test cases uh is test case test case is nothing but it is a step of instructions which validate your requirement, okay? So, I'll show you what does a test case looks like. Don't worry about it, okay? Uh just now understand that you're writing the test case, right? The test case to validate the requirement. I'll show you what a test case looks like, okay? So, I'll show you what a test case is. One minute. Anything I have with me. Okay, so this is a test case if you can see So this is how our test case looks like. Okay, so this is a test case. Okay, this is a test case. This is Test case means you're validating some requirements. So here I'm validating the login feature. Can you see? Verify login with valid username and password. So this I'm validating. Okay? Right? And what are the steps to validate this? I'm sure. One minute, let me just go to the So this is a prerequisite that the user credentials are already there, right? And these are the steps. So how will you validate whether the user is able to log in? Like this. You'll launch browser, okay, and then you'll open the URL, some URL, right? We'll enter the username and password, and then you'll click on login button. Everybody saw that? Right? How will you How will you validate username and password? Please have a look at it. Okay, so these are the steps to validate this scenario. And this are the test data, meaning the username and password. And this is the expected result. So once if you enter the login button, the user should be successfully this one. And then you do it. User should be successful. Yes, the test cases will have scenarios, okay, based on the functionality. Do we need to learn the test case? Regression means Regression testing means every time you get Every time you get the Every time you get Every time you get a new build from the developer, right? What happens is that there are some previously existing functionality, right? Like suppose now you get a build with some new changes, like homepage have got developed in this build, right? So the previously existing functionality was the login page, right? So what can happen is that login page can be broken. It will not be working. It can happen. So, what you will do, you will do a testing, quick testing on the new build to make sure that the old existing functionalities, like login page, is still working. So, that kind of testing to make sure that the old changes old working functionality are still working in the new build is called as regression testing. So, we do regression testing to make sure that any previously working functionalities are not broken due to the new changes in the new build. Okay? So, that is regression testing. Okay? So, what can happen, Shivani, every time is that whenever the build comes, right? What is build? Build is nothing but executable piece of software. Okay? Whenever the developer gives a new build, build is nothing but a version, right? Whenever you open a get up, you see Instagram, right? New changes a new build have come in the App Store or Play Store. That is a build, right? So, what happens is that it contains new features. Correct? So, when the new features have come, it can happen that the old features can be broken. They might not be working. So, what do the testers have to do? They have to test the older features whether they're working or not. So, that kind of testing is called as regression testing. Yeah? So, these are not a part of your course, but I'm still telling, okay? Okay. So, what is Agile? Agile is a way of managing product projects, especially software, by working in small chunks, getting frequent feedback, and adapting fast when things change. Okay? And core ideas we have already talked about of Agile. We We We focus on people over rigid processes. We focus on working software and all, right? And popular Agile frameworks we have talked about, right? So, what is What is Agile methodology? So, Agile methodology, if we have to talk about Agile methodology, then Agile methodology is basically it works It breaks works into small tasks, right? It prioritize what brings the most value, right? We work in small cycles and we deliver something usable. We get the feedback in and we improve [clears throat] the work in the next cycle, right? So, this is all about the Agile Okay? We're talking about this now. I'm just trying to open the PDF for them. Just give me a second. Okay. So, this is the Agile methodology, okay? So, Agile methodology is basically is a project management methodology, okay? And to it assists the software development teams in effectively dealing with dynamics and uncertainties, right? So, why it says uncertainties? Because there can be sometimes, you know, as I told you that the customer can come back, right? And it he can ask you that we want this to happen, right? We want this new requirement to come because our competitor have introduced this change. We want this thing to happen, right? So, because of these things, it helps us to deal deal us with those kind of changes, right? So, this is because of these things that we say that it help us to deal with uncertainties, right? So, there are certain reasons for choosing the Agile software development and testing, okay? So, there are certain reasons because of which we choose the Agile software development and the those reasons uh described are that I first I'll I'll talk about then I'll give you the write-up, okay? So, it reduces a technical depth, right? Why it reduces a technical depth? Because we develop the software in chunks, right? We do not do everything in at a time, okay? We don't do everything in at a time. We don't do everything in time because if you develop everything at a time, then it can happen that we are actually accumulating a lot of bugs, right? Suppose now if you are developing all the entire things, entire features at a time, it can happen that you may end up not making a lot of mistakes, right? And the customer will see them all the mistakes at a time. But if you're doing things part by part in increments, then that you're getting a lot of feedback from the customer, right? Then you are getting a lot of feedback from the customers and from the from product owner also, right? Because there is a even like sprint uh review where you are getting uh the feedback from the stakeholders and then if you can actually improve all those mistakes in the next sprint, right? And because of that, there is an improvement happening, right? And it creates also actually total alignment and transparency. Transparency is always there, right? There is nothing like you are doing everything hidden. So, the like in waterfall and V model, right? They say that we do we will do it, come after 5-6 months or 1 year, and then we will show you everything, right? Okay? So, this is this is transparency here, okay? And uh this is total transparency here, okay? So, this is the advantage of having the Agile, okay? Agile Agile methodology, full transparency, okay? Then what is uh another thing here? Commitment is there, okay? Commitment means in every sprint, you're committing actually that we are committing all these user stories, we are uh we are actually building this feature work, right? And we will do this we are we are doing we are actually estimating these story points as a team we are coming collaborating, and we will do this, right? So, as a team we collaborate and we are committing all these story points. Okay? Next is actually creating total alignment and transparency that I told you, right? And then uh what is the next one as per your uh this thing is yeah these are the three things now let me give you the right up okay because it's small right up on the Okay so this is the small right up. Okay so reduces technical depth means early testing as I told you and it leads to continuous improvement. Easy to adapt means short cycles and it leads to flexible planning alignment and transparency because there is a collaboration visibility and shared ownership okay. So this is all because of which it leads to. Okay and example for it is as agile reduces technical depth so what is technical depth okay. What is technical depth? Technical depth is because technical depth because suppose now if the team is not doing some process right for example now if I have to explain you there is a post now unit testing okay just understand guys okay now suppose unit testing is not happening. Okay now everybody please understand this okay please understand this for beginners it will be a little difficult now unit testing is there okay so this is the first phase of testing if unit testing is not being done by done by the developers directly testers are testing it then some technical depth will happen some bugs will be found in the application data right so if this is not happening guys then that means it will lead to technical depth technical depth means some process if it is not happening then we are going to accumulate some technical depth. Okay that means let's see suppose guys if you're not studying to today you're going to accumulate some kind of depth on your on your studies right tomorrow you're getting going to get poor marks or not so this is technical depth okay how agile will reduce it how agile will reduces reduce it because here development is happening in small manageable increments so problems are happening detected early right continuous testing is happening. Okay right. Every sprint includes some Scrum events like review and improvement. Okay? So, let me give you elaborate this. I tap. Let's go through this. Let me take my mouse. Okay, please read this. Maybe this will help you to understand for those who are beginners. So, this is about technical debt. Okay? Okay, some question asked if a task in the project spill over, how will work in short cycles will work. Anything if it is getting spill over, they need to do it later and they need to address it why it got spill over. No, it will not move to backlog. Okay? Uh Amol Jadav, work in short cycles will work. Work in short cycle, what it means is that sprints. Okay, short cycles, what it means is sprint. Short cycles means sprint. Sprint. Understood? Short cycles means sprints here. Okay? Okay, next one is Agile is easy and adaptable to change, okay? So, this is Agile is easy and adaptable to change. I already explained why it is so. Because if you get any feedback from the customer, we bring it in the next sprint, right? So, this is about that. See this one, example here. This is the main thing. Okay? So, last one is about transparenty transparency, so it is about you have seen that board, right? Jira board. How Scrum brings transparency, right? We can say using Jira board. So, this is another thing. Please go through this, okay? Agile create total alignment and this transparency. Okay? So, this is using daily stand-up, using sprint planning, okay? So, this is guys all about the first part. So, this is reasons for choosing Agile software development and testing. And then there are some other reasons also. Agile software development and test minimize risks, okay? And uh uh it it brings high-quality products, and uh it predict it it also predict the delivery dates. These are some other things, also. Okay? So, Agile software development and testing minimize risks, okay? What does it mean is that the work is delivered in small increments, okay? And then there's testing uh actually defects uh it detects defects before they go into major failures. And uh since we do regular customer feedback, right? Uh we do we prevent uh building the wrong product, right? And problems are fixed a sprint by sprint, not at the end. Okay? So, this is the Agile software development, and uh that is how it minimize the risk, okay? An example will be that if a payment feature fails security testing, right? So, then we will fix that in the same sprint instead of uh testing it at the end, correct? Okay? So, this is one example. Clear? So, let me put this for you. Okay? So, this is the one. So, Agile software development and testing minimize risk. So, what we're discussing now is how Agile software development and testing, right? What is the advantage of using testing with Agile software development, okay? So, the next we are going to discuss, okay? Next is Agile delivers a high-quality product, okay? As Agile delivers a high-quality product. So, what is that? So, Agile delivers a higher quality. Again, why it delivers a high-quality product? See, guys, everything is related on, okay? Why? Because you're you're going to get you're going to you're going to get a frequent feedback, right? From the customer. Retrospective, right? Automated testing goes hand-in-hand. Refactoring improves code maintainability. What is refactoring? Refactoring means the code refactoring, right? Whatever the code is getting refactored by the developers, okay? Even the code refactoring happens for the automation scripts also, right? It maintains the code maintainability and performance, okay? So, regression testing in every sprint ensures new features do not break the existing. So, now you know what is regression testing, right? So, regression testing is done every sprint to make sure that the new changes which are coming in the build are not impacting the older existing functionality, okay? And that will actually help you to make sure that older changes, older things are not impacting, okay? There is no mock test, guys, okay? There is no mock test, okay? Next point is Agile enables predict delivery dates, okay? What is predicting delivery dates? Suppose if a team completes 20 story points sprint consistently, delivery timelines can be predicted uh reliably. Suppose now, you know, now as I told, right? There is a sprint planning happening, correct? So, sprint planning is happening. Now, if the team is doing There are five people in this sprint, five people in a team, five people are doing suppose 30 story points, right? Okay? So, now in the next sprint they will take how much story point? They can take roughly 25 to 35 story points, plus minus, right? That's how Agile will be able to predict the delivery dates, okay? And that is called as velocity, okay? Fine? That is called as team sprint sprint velocity, okay? How much total uh story points the team can deliver, okay? Five people are there, all of them they can deliver 30 story points, that is called as velocity, team velocity. Fine? Okay? Please go through this. Okay? So, Agile quality assurance, okay? So, main aspect for Agile quality assurance to remember are that the QA teams is cross-functional, okay? So, what is cross-functional? What do you mean by cross-functional? As I already told you, right? So, what is the meaning of cross-functional? Cross-functional as I already told you, cross-functional means that everybody knows what to do, right? Everybody knows what to do. What to do means every team member is equally skilled enough to know what the other person have to do. So, that in absence of everybody, the team knows how to carry on each task and they are not uh incapable enough, okay? So, the main aspect of Agile QA are that a QA team is cross-functional and self-organized. So, in each sprint of testers help define user stories, write test cases early, and execute test alongside development instead of waiting for a final testing phase, okay? So, this is the meaning of cross-functional also, okay? So, the main aspect of Agile QA are that the QA team is cross-functional and self-organized, okay? And testing is continuous throughout the development. So, testing happens parallelly through the development. So, testers work closely with the developers. Why? Because in every sprint both the things are happening parallel, right? So, this is the meaning. I'll put this down here. So, next we're going to discuss about Agile testing principles. Okay? So, what are Agile testing principles? So, Agile testing principles mean that the quality assurance team provides continuous input to the development team ensuring defects and quality issues are identified earlier. How can How do How do the QA do that? QA will team will also be part of backlog refinement, right? They will review the user stories and acceptance criteria before the development will begin, okay? So, that's how they will provide continuous input to the development team, okay? And they will identify some defects and quality issues, okay? Development and business analysts also participate in testing and promoting shared responsibilities for quality, okay? So, how developers and developers will participate in testing. So, developers will do unit testing. I think I have not told you, right? Developers will do unit testing. How developers will do unit testing? Before they do before they give the code to the testers also, they have to do one type of testing, okay? I think most of the people might not be knowing, okay? That is called as unit testing. For that unit or feature which they're developing, that is called as unit testing, okay? So, this is called as unit testing. First phase of testing which they do that is called as unit testing. And that helps in achieving actually that is where they find lot of defects even before they give their product they have built to the develop to the testers, right? That helps in finding lot of early defects, okay? So, let me give you these Agile testing principles, okay? We will discuss We'll let me give the write-up. And these examples are there and that will help you to understand it one by one later. First, put the write-up and then I will So, one example there. Okay? So, this is the first one. This is the second one. Developers and business analysts also participate in testing. How developers participate in testing? They perform unit testing, okay? As I told you, this is only testing which is done by the developers. Now, you will wonder what is this? They perform unit testing. So, unit testing is the testing for that particular unit which they are doing, okay? How do they do it? They write some automated test cases and that's how they do. While business analysts validate the requirements through acceptance test. So, business analysts people, right? BAs. They write some acceptance test. And that's how they do the validation. Okay? Next, QA team resolves defects within the same iteration, right? This I have already told you. Within the same iteration, right? They do the testing. If any defects are found, they raise it through the Jira and all and developers have to fix those defects in the same sprint, okay? The bugs found in the sprint testing are fixed before the next sprint. Okay? So, this helps in achieving quality. Okay? Minimal documentation is maintained. So, this Agile is not heavy documentation. We work on working software, less documentation. Okay? So, test cases are derived directly from the user stories instead of long test documents. So, here unlike waterfall model and all, so here test cases are derived directly from the user stories. You see the user stories and you write test cases. They are on Like in waterfall and all, we used to write test cases from the uh long long documents. Okay? Fine? This clear? Testing next, testing is performed throughout the implementation process, not just at the end. Right? So, what does this mean? Every sprint, the testing will be performed. This sprint testing is performed. This sprint testing is performed. Not like it will be performed at the end, right? Not like here the development went, the testing will be done here. Not like this. Testing happens parallelly all through the development. Understood? So, the regression and integration test are continuously as new features are added, right? So, I hope everything is clear because I was talking already all through these points. Okay? And I'll give you 2 to 3 minutes to go through this. Okay? And if there is any confusion, please feel free to shoot out to me in the Q&A. Okay? Okay, so next we need to talk about the Agile testing life cycle. Okay, so this is the sort of agenda or the kind of scope of my teaching or the scope of content of your learning for the next uh few weekends. First next this is the second weekend, right? So, three more weekends we'll be doing. So, this uh So, I am going as per this uh content. Okay? So, this is the Agile. Okay, this is the Git. MySQL, HTML, CSS, JavaScript, Angular, Cypress, okay? So guys, this is all we need to learn. So last weekend, 8 hours we have given to a child, okay? And here you can see that see that this is the content, okay? We have covered up pretty much. So guys, whatever I will be teaching will be as per this sheet, okay? Content of as per the sheet. Okay? And I got one comment where I saw that one of the learners have mentioned that Kanban is not covered. So guys, uh I will be focusing on teaching as per the scope of the content. You can see that there is no Kanban here. Okay? So if I am not a teaching you anything, okay? So that is not a part of this content because the content have been uh made in such a way that only the topics which are mentioned uh we have a period, okay? If I also spoke with the manager, so if we need to extend the timings, we can extend to two more classes. Eight more hours will get extra. That is not a issue. So I have already discussed with them, okay? And um so this is the thing, okay? So Kanban is not here, but I have discussed that Kanban is a type of type of one STLC model, okay? So this is first thing, guys. If I will be going as per the scope of the content, okay? So So this is first thing. So one guideline is that Let me know if you have still any confusions, okay? So content wise teaching, okay? So this I'm doing actually right from the first class only. And I will be giving you lots of examples, okay? If you feel that examples are less for you to understand, let me know, okay? Then um yeah, examples based, okay? Examples I will be taking lot of examples because I think that is what most of the learners are beginners, right? And third thing will be right after every topic. Yeah, I will be addressing your concerns. Yeah, definitely I'm not going to look into those uh PDF that you can learn read yourself. I'll be using my book to uh teach you, okay? And then uh what is the next thing was that yeah. So, yeah, another one feedback which I received was that uh the quality uh the quality the training is not as per the quality. Okay? So, uh that is little bit uh vague description I found. So, I was trying to interact with Bhumika also. So, uh please let me know what is the term quality means. What are you expecting in terms of quality, right? So, what is missing in terms of quality? Is it examples? Is it something Give me some examples with reference to a topic which I taught and it was lacking with an example. So, uh just give me a with hint with an example what is the meaning of the quality that is missing, okay? So, this is how Jira looks like, okay? And I think I have already shown you. So, this is the project, okay? So, Panther is one project here, okay? And you will see if any sprint is active. This active sprints right now there is no sprint active, so the board is empty. Otherwise, here you can see see some tickets here, some user stories, okay? And you can see the backlog here. So, I'm kind of revising whatever we did in the last week last weekend. So, last weekend we have basically done about uh we have learned about Agile methodology, right? We learned about how Agile testing fits into Agile methodology. We also learned about basic rules, uh okay? Uh of Agile uh Scrums. We learned about Scrum ceremonies, okay? We also learned about how sprint planning is done. We also learned about different interview questions also which you asked me to do, right? So, we did all of these things. So, now here I'm going to as per the content I'm going. Okay, so here I'm going to talk about basically about some user stories. Okay, so user stories also I have taught. Okay, so now I'm going to talk about definition of ready. Okay, so this is one concept definition of a ready for a user story. Okay, definition of ready. So, it is in regards to our user story. So, Jira access if you get guys, you will get some 30 days free access for that user ID. I mean for that Gmail ID or whatever. After that you can use another Gmail ID and try another free trial access. That way you can just use it. Okay, like that you can keep on extending it as many days as you want. Okay, now what is definition of ready? Okay, so definition of ready. Right, as the name suggest, definition of ready is related to the user story. Okay, now for example, you're creating front end application. Okay, front end application like a e-commerce application. Okay, then for creating that application, right, what do you need? What do you need basically? So, basically you need you need the work of development, right? Now, if some of you are not understanding, right, any application if you are making then it have it will need development for from two ends. Front end and also back end. Okay, so what is front end? Front end is nothing but Java like JavaScript. Okay, front end is nothing but the UI which you see, the visible UI which you see, right? That is front end. And front end development is done using a tech stack like JavaScript. Okay, some some framework like Angular or React. Okay, so I'm just talking about high high level. Back end is on the other end then using some other frameworks like spring framework, okay, and all those things, okay. Now, you cannot create front end first, okay? So, for front end to be done, back end should be done first. Okay, so this is a dependency for the front end. So, for the UI developers to start their work, the back end should have been done first, okay? Back end means API should have been developed first. APIs. Okay, application programming interface. So, I'm just talking on a very high-level note, okay? Even if you're not understanding, just try to understand that there is a dependency, okay? For the application to be worked. Now, if there is a ticket to create a login screen. Okay? This is a real-time example I'm giving which is a visual makes sense if you go and work in any company, okay? Then for login screen to be developed, the dependency is that login APIs should have been ready by the back end developers. Okay? And this is the definition of ready for that user story, front end user story, okay? So, what is definition of ready? It's like a checklist that tells that when a user story is ready to be worked on without If this is Okay, now all the front end tickets to be done, what is the definition of ready? Back end respective ticket should have been done. Makes sense? Okay? So, front end application front end front end you can do only when the back end hits have been done. You cannot go and create a front end for the login if the back end login API is not developed. Okay? So, what is a definition of ready? Definition of ready is a checklist that tells the team that when a task or user story is ready to be worked on, right? In short, if a task meets the definition of the ready, the developers can start the work without confusion or delays, okay? And this is agile concept. Okay, it's like a prerequisite. Suppose now you are going to cook the cook your food, right? So, what are the definition of ready? You should have the vegetables, you should have all the spices, you should have the oil, right? And if if you do not have any one of these, can you start cooking? Right? How does definition of ready helps? Because it avoids unclear requirements, right? If you just start working on that front end ticket and in between the sprint if you realize that this is not ready, then then it will be a ticket which cannot be finished in that sprint, right? So, it makes our sprint planning smoother, right? It saves lot of chaos later in the sprint. So, definition of ready answers the question, do we have enough information to start? Suppose now, another example I'm telling. Back end API means to understand back end API means it's a See, any application have two things. So, people who are not able to understand, okay, this is a bigger topic. I cannot make you understand. Just understand that there is a front end which you see in the through your When you open your mobile, you see Instagram, right? Now, what are you seeing on your screen? This is Zoom, right? This is a front end, okay? So, this is a front end, what you see. But, is that all? No, right? So, but behind also there is something called as back end. Okay, for every application there is a back end. Now, for Swiggy, Zomato, Netflix, Prime Video, right? Every application have a front end and back end. You cannot develop the front end if the back end is not ready. I had just given you one real-time example. Now, if it is too difficult for you to understand that, try to understand like this. You cannot write your test cases if the requirement document is not with you. So, what is the definition of ready for you to write test cases? Requirement document should be there, right? Acceptance criteria should be clearly defined in the user story, right? Designs or inputs should be there in the ticket, right? So, this is the definition of ready for you the testers to write the test cases, okay? So, leave that front and back end if you're not able to understand, okay? So, for example, user story is create login page, okay? If no designs are provided, no validation rules are there, no clarity on error messages, no acceptance criteria, can you take up this ticket? Example, this is the example. Is this ticket ready? Is this ticket ready? Answer is big no, right? It's not ready, okay? So, what it needs to be ready? Now, I'm giving you another scenario, okay? Now, I'm giving you another ticket. See this ticket. Is this ticket ready for you to write the test cases? Yes. So, leave that front and back end, right? So, is this ticket ready? Yes, this ticket is ready for you to write your test cases, okay? Okay, guys, fine. So, now I will give you the definition since you have understood this, and now I'll give you the, okay? So, now, definition of ready is a set of criteria or checklist that ensures a user story has all the required details before the team starts development, okay? This is the definition. Okay? Testers can develop API? Yes, testers can develop So, guys, please don't go into API and all, okay? API is application programming interface. I just took one example to make you understand. Don't get confused about API. Please leave leave the API, okay? API is not the point of discussion now. I just took here a uh uh a topic that I think many people got confused, okay? So, leave that, okay? If many people understood it, fine. That is fine. But, my intent was to teach you or make you understand about definition of ready, which everybody understood, right? So, this is fine. Now, I'm moving to definition of DoD, which is also called as definition of done. These are also important from interview point of view. Okay? So, definition of done is something similar to definition of ready? Okay? And it is uh The ready was uh for uh making sure that you can start a ticket. Okay? And definition of done is something like how will you make sure like on what grounds, okay, you can make sure that your story is completely finished. In other words, how do we know that a work is done? Like you tomorrow if you are saying that your story is completed, right? How will you say that your story is completed? Okay? See, suppose you say that, "Okay, I have finished my work." Okay? You might say that, "Okay, I have done two pages of Hindi, two pages of mathematics, three pages of this, so I have finished my work." So, that might be some rule which uh your teacher and you might have done, right? So, this definition of done is also created by the team. Okay? Who defines this definition of done? No, Scrum Master doesn't defines. Scrum Master have nothing to do with definition of done or definition of ready. It is the team who comes together and they create these two checklist. They are talking about checklist items. Okay? Neither the test manager, see, test manager, product manager, nobody have done. See, Agile, what is the concept? The team works together. Team works as an Agile unit. Team is the whole and sole unit which works together to define all these things. Who is test manager? There is no test manager concept in Agile. Okay? Scrum Master is just a facilitator and the and a servant leader who just is with the team. Okay? So, it's a team who comes together. Maybe the Scrum Master will facilitate this discussion. Okay? So, what do you want? What do you need? The team defines. Okay? So, because I have done those certifications, okay, so this comes in exam also. In interview also they can ask you. If you say that my manager have defined this, maybe you can get rejected in that round, simple. If I take an interview and if someone says that okay, my manager have defined this, then I will understand that this guy have no knowledge in Scrum. Okay? He or his mindset is still with the old legacy old mindset. Okay? Or he might be working in a team which is just doing a job, not being a job, right? I have seen organizations which where the team just come and open Jira and they do stand-ups. Okay? And they just somehow show that they're working with Agile and Jira, right? They are not actually following anything. Okay? So, that is different. But, if you want to you know Yes, Abhishek. Yeah, that is that is correct. So, so it happens. Okay? That is the reality. Nobody Some of the organizations they're very very strict and they follow it also very well. Okay? They have their own TEOs this test Agile center of excellence also there. Okay? So, they do it in a very proper way also. There are some companies who don't take it for anything. Okay? It depends. We cannot do anything. Okay? So, team comes together and they define how they're going to mark story as a completed. Okay? So, this is a definition. Now, I'll give you some examples. Okay? So, now for example, how will you make sure that the code which the developers are coding, right? And the testers are testing. Now, in Agile how we deliver? We deliver in a sprint. Suppose in one sprint I'm delivering a login feature. Login feature. When I say I'm delivering login feature means this entire functionality is going, right? When you go to the URL, you click on login, you're username and password, right? You're able to successfully go to the home page. Okay? You are creating this functionality. Now, how will you mark the story as done? I definitely you say that ma'am acceptance criteria of the ticket should be done, right? That is story related thing. But, for definition of done is not for story. First understand this. Definition of done is for is applicable for all the user stories, okay? So, this is another interview question. So, I'll tell you later. So, definition done is for applicable for all the user stories, okay? So, when will you consider a story or a task to be considered to be done? So, I have some examples. I will consider a task to be done or a story to be done when code is completed, coding is completed, right? Code review is done, testing is completed, no critical bugs have been found there, feature is working as expected, right? And it is deployed to the required environment if needed. Documentation, everything is updated. Okay? So, this is something definition of that. Okay? Think about an exam. When you are done writing an exam, when you have finished writing all the answers of the question paper, right? If time is left, you review them also, then you submit the paper, and the teacher accepts it. After that only you are done with exam, right? and you come out of the exam hall. What my example? Real time example, okay? When will you say that I have completed my English mathematics English or mathematics question paper? When you went to the exam hall, you write all the answers whatever you know, then you reviewed them, and when 3 hours got completed, you gave your question paper to the in to that submitted the paper to whoever was there in that exam room. Teacher took the paper, and you came out of successfully out of that exam hall, right? Just writing the answer sheet done, right? Does not make sure that your exam is done, right? You have to do all this step by step, then only your examination paper is done. Similarly, there are certain things, it's like a checklist, right? So, similarly, the checklist for user story, everything should be done, then only user story will be accepted. Just writing the answer, blah blah blah, right? And throwing it there on this table, and running out of the exam hall, and jumping the wall, that way the the teacher is not going to accept the paper. He will just mark it as rude, right? Unprofessional behavior, this and that, and he will be suspended from the school also or college, whatever. So, he have to follow everything, right? So, this is one real-time example, okay? And this is how exactly DoD works. So, I'm giving you another example of DoD for your tickets, okay? So, this simple definition of DoD done, okay? For you, for your user story, user story. What it will be? It will be all these things, okay? You see this. A task will be considered done when code is completed, code review is go through this. All these things, if it is done for a user story, then only your user story will be done, okay? So, now finally, I'm going to give you the definition of definition of done, okay? Anything which you not understand, let me know. So, if you ask if you ask me simply, what is the definition of done? This will tell you or this can ask answer you the question that how do we know that this work is done? So, tomorrow if you're going to work in any project or any team, you can ask me, what is the definition of done, right? For this project, for definition done is for the all the user stories. It's for all the tasks. It is not for a specific user story. So, now you understand what's the difference between user story and sorry, between acceptance criteria and definition of done, okay? Demo is a part of sprint ceremony, Jyoti. So, we are not going to put here as as definition of done, right? Demo is a part of sprint review. All the scrum reviews, scrum ceremonies, we are not going to put in definition of done, okay? This is something internal to the team. Any more further questions? So, user story is nothing but it's a small requirement, right? Which you can complete within a sprint. So, user story in Jira is actually used to describe what a user want and why, and it is written in a simple format. I think I told you last time, right? Okay, so I will show you that. Okay, one practical thing on the Jira and then we will move. Okay? So, standard most of the companies follow guys this format. So, once again revising this. Okay? Okay? So, this format is followed as a user what kind of user I want what you want, that will be the feature. So, that what benefit you get out of it. Yeah, I will show you what is Jira. Okay, once again I'll showcase you this. So, guys being a fresher or being a newcomer to Jira do not have to know everything about it. So, being if you're new to Jira, you just have to be focused on this page. Okay? So, this page you should know. Okay? On this page what is there? This page you have board. Board means any act Okay, any active sprint will be there, right? Sprint you already know, right? It is a short iteration in which you deliver some working software. Okay? So, if you are assigned some work here, your name will come here, right? So, right now this is an unassigned ticket. So, if I assign it, okay? If I assign it, for example, I assign it to myself, so my name is coming, right? Tomorrow if you go and work in any company, if they assign two three tickets to you, so your name will come here. Okay, that's it. Okay? You will not be having many permissions. Only scrum master, a technical program manager, or project manager will have permissions, okay? You will have permission to view this board to work on your ticket. Suppose this is your ticket, search feature. Okay? As a user, e-commerce user, I would be able I want to search some products so that I'm able to get my desired product, right? So, this is the ticket. So, here you can see that it is assigned to me, right? You can work on this and there are different things, right? You can put the due date on which date this ticket have to get completed. Suppose this ticket have to get completed by next Friday or next Wednesday, 21st. Okay, that much usage you should know and then when you are going to start working on this, if you are a very good and then Jira hygiene, please put that. Suppose you're going to work on it from Monday onwards, right? So, you can start putting working on it on Monday, right? So, like this and then story point estimate is very important. Every ticket should be story pointed. Okay, so these things will be done in sprint planning, right? And then being a tester, you can put comment everyday here. Worked on this on creating manual script. Right? For this feature. Okay? Add it here. You can attach the link. Okay, fine? So, you can add comments here so that the entire world can see what you're doing. So, Jira is all about transparency. You can see in history who have done what. See, Sweta Rawat updated his two story point. Updated his start date, due date, right? Everything will come here. Okay? So, this is all what required from you being a standalone tester or developer or anybody, whoever it is, right? Second thing which you being a tester should be focusing is on backlog. This is very important here. On the ticket which is assigned to you. You should know how to add comments on to it and you should also know how to move it to a correct status, right? Let me show that. So, this is the ticket. Now, this is in to do. You have Once you start working on it, you have to move it in in progress. Okay? Now, if you're a developer and you have done the coding, you have to put it for code review then in review. Okay? Now, if this is blocked due to testing, it will be in blocked. If it's blocked, then directly you cannot move it to done, right? Again, it will be in progress because some remaining work was there. It have to move to progress. Finally, done. Right? So, it is done. Once it is moved to done means done. It is moved to done then it have come here. Can you see and it have been strike out by the Jira. Fine. So this is very important for you. Okay. And this is what you have to do. That's it. Nothing more expectations. Second thing which you have to see is board or backlog. This is the backlog. Click on it. If you click on it, you will get So here a couple of things I have already shown you last week last week also. Backlog here you have zero work items, right? So let us create one ticket here and I'll show you it will come. So backlog is the place where all your requirements will be there. Usually it is the duty duty of product owner to maintain this backlog. Okay. So here there is a create button. Can you see? Let us create one user story. Okay. So I'm creating a user story story. Okay. So I'm creating [clears throat] a sample user story. Okay. So let us create I have already created for login, right? Some other functionality Just letting me think about. Okay. Let we can do it for user registration. Right? As a new user I want to register. Okay. So we can just say user registration. Summary should be very very short and crisp. It should not be very huge. In bracket you can say sign up. Okay. Here you should not add a lot of things. In description you have to do the same format whatever I mentioned. As a user I want what feature so that what benefit you get out of it. Right? So as a new user. Okay. What is the feature here? I want to register using my email and password. Okay. So this is the feature. I want to register using my email and password. Okay. So this is the feature. Okay. I'm writing the same word. What is the benefit? So that I can create my own account. Okay, so this is your user story. Is that okay? And then every user story will have an acceptance criteria also. So we can write an acceptance criteria. If this is done by a product owner, it's not your job. I'm just showing you so that you have an idea if you go uh to the company, you get an idea. So acceptance criteria defines the rules to accept the story when and this have to be kept in mind by the developer when he's developing and the tester when he is creating test cases and testing. That clear? I have already defined. So some acceptance criteria like user can enter email email password. The second email must be unique. Okay, then password Suppose you're telling must be minimum eight unique characters. Okay? And then fourth one is success message to be shown after registration. Fine? So I'm not adding any negative criteria. Okay? You can add some negative criteria also. You can accept some negative criteria also. Fine? So guys, there can be a lot of things. Okay? I'm just adding few things. So is that clear? This is how you will write a user story and create. Right? So you can see that as soon as I created this user story register user registration and sign up with it came here. Fine? And uh you can do is that you can see Okay? Right? Like this you can create user stories. When you create your own sample Jira, please you can create it, okay? This is the format. Okay, any examples? Uh sorry, any other questions if you have, please shoot out to me and then I will move on to Git. What do you say, guys? You just have to click click on create. Choose work type story, okay? And this other things I'll just put it up, okay? I'm just putting this. So, if you don't know, you can use this for reference, right? And the material Inside material is here. You can use this. Summary, you have to provide uh this only. The heading and that description is this. So, I hope this will easy for you, right? What are the functions of epic and task? Epic is a big functionality which holds many user stories, okay? And task is something which is not a functionality. Task is something like you have worked on the creation of test environment or you are working on creation of test data. So, these are non-feature related work, right? Non-functionality related work. So, any non-functionality related work if you need to capture, where will you capture? You will capture it using the task, okay? Task have no relation with the epic or user story. Task is separate entity at all. It's a separate work item, okay? But you can I will put the link also, but I don't think so you will be able to access this link. Because to access this link you will need my credentials Jira credentials, which you will not be able to do that. Only I can access because this is to my Gmail ID. But even I have that I have put it here. You won't be able to access this link, okay? Linking the ticket to the task. A task is something different. I think if you're confused, we can create subtasks under a ticket. How to log a epic in Jira? Same thing you can log log an epic, okay? You can create a epic, same thing here. Create instead of story, you create an epic. Okay? And you can say that it will go to create this account functionality. Okay? So in description you can write I'm going to put here all the tickets which will be which will be used for the implementation of this account functionality. Okay? Account means it will come login also, registration also, everything, okay? So like this you can click on create button, you will be able to create epic. So epic, like this you can create task also. Okay? Like this, okay? Right? User story was the very was there as per the scope of this content, so I have shown you, okay? Turn over request. So there is I have not heard about turn over request, Sonia. I have heard Yeah, epic also we need description, right? You can say account functionality, okay? Yes, everything will need description, cousin, okay? Turn over request I have not heard of, Sonia. So I'm not sure about turn over request. Request I know. Suppose a request is coming from some team, right? Or if it is a change request. Okay? That will be a request. That also is a type of request, right? Change request. Want to add some new functionality to an app to or some bug fixes there, right? For that a request have come. So all that will come in the request, okay? You can create a request. So that is a request work work type in Jira, okay? Request work type. Mostly you will see user stories, epic, bug, that's it, and mostly task, okay? The request work type basically is for uh help, support, or service. Then it can be for change request if it is development team. Story needs to be epic to be added correct. Yes, so if you create an epic, right? You can link it to that epic. So for example, here let me let me create one account epic. Okay, I'll not put body. I'll let me simply create one epic, okay? Just to show you how I'm linking. So suppose this is account. functionality Okay? So I'm not putting in anything in description. I'm just creating account functionality epic. So view this epic. Okay? It have no child work items, right? Now go back to your project again. Backlog. Now this ticket is there, right? Scrum two. Open link in new tab. So I want to add epic. Can you see add epic? So you can add this user story into some epic. He is telling you, right? So what you can do, click on this. I'm adding it to So view all epics will come. So now in this no epic is there, only one epic. You can add this to this epic. So see? It now it have gone to scrum three. Now if you go to this account functionality and refresh this page, you will see that one story have come here, user registration. Can you see? So this is how epics will hold all the user stories in real time. Okay, so now let me open Simply Learn. We will move on to now, guys, Git, okay? Next topic is Git. So why I am opening? Because I need to open the lab, right? >> Okay, so meanwhile this will be starting. I'm starting with Git. Okay, so what is Git, okay, and why do we need Git, okay? So, I will just come up with some basic things and only help of about Git. Git So, Git does not have any short form, first of all, okay, and why the Git has been added initially because maybe a lot of people will be using sharing code each other code, right? You'll be writing and you will be needing Git for it. So, in real time suppose think think of example that you're writing a book, right? You're writing a book. Every day you're saving a copy of it, right? Today you have written something, right? So, you have saved a copy. Tomorrow you have written something, again you have saved a copy, right? Like that you'll keep writing it for 10 days, right? Every new new day a different version will be created, right? Finally, on 11th day you have created the final version and you call it as book final, finally, right? So, suppose you want to go to the changes or you want to go to that version of a file which was there on 6th day and you want to bring it back, right? How it was on 6th day. How will you bring it back? Yeah, Madhav, yeah. I mean, using Git we can do that, but I'm asking about the rest of the other people who don't have any idea about Git. So, how can you do that? If you do not have anything, can you remember on 6th day what you have done? By the time you reach 11th day, you already have made so many changes in that book. Cannot retrieve the Photoshop, or you can say, you know, you take a picture of a child, right? When he's 5 years old, then you have a picture of that child in your gallery, right? Tomorrow, when the child have grown 10 years, 12 years old, right? You go back to Google Photos and you see a picture of him, right? Means, you have a snapshot of that picture, of that kid, right? In your in So, in in your in your photos, right? But, if you're writing a book all by yourself, and if you keep making changes right now and then, will you can you bring it back manually? It is not It is not possible, right? So, what I'm trying to make you understand is that it will be very confusing. You cannot do that in real time. If you If you write it on a hard I mean, on a manual notebook, or if you start writing on a Word document also, right? It is very difficult to save the versions. Now, same thing now. We work in a distributed environment where the teams are spreaded across different countries, right? So, suppose now, we have developers working in US, UK, Poland. And when I was working, yeah, I have worked with different teams, right? We have worked We worked with overlapping time zones, right? Like, we start working, then the US team will be sleeping, right? When we sleep, they start working, right? So, suppose we're working on a similar file. There is a file, okay? On which an Indian developer is working, or Indian automation tester is working, and similar file next tester starts overriding or he starts making changes to it in his daytime in US. If we do not know who is doing what, which version is getting saved, right? Then how will you work? Tomorrow if anything goes back, how will you go back to the previous version, right? In order to save you from all that, Git is that tool, okay, which automatically saves the versions. It knows who have made what changes. It lets you go back to any previous version, and it allows many people to work together safely. Clear? So, Git is a tool that tracks the changes in file over time. Simple. Okay? In olden days In olden days, there used to be only main main one one main server, okay? People all used to work on that, okay? No, it will not be overwritten, okay? Yeah. So, suppose now there is one file, okay? There is file called as XYZ .doc, okay? And people are working on this file, okay? Two people are working on this file, and they're working together. One person is making changes to this file, okay? Another person is also making changes to this file, right? Can they work together? If we do not know who is making what changes, when they are making changes, right? And if one person's changes get lost, how will the other person blame each other, right? So, all these things can happen. So, it is very difficult. And now we have teams which are distributed, as I told, right? If you work in any project, you will get people working in different countries. Here also, I think many people have joined from other countries also, right? Both are separate, Pavan Raj Chavan, okay? You can integrate Git and Jira, but both are separate softwares, uh okay? So, Git is tool which help you to track the changes in files over time. Now, suppose I'm working on a file, and I commit to some changes in the file, okay? It will track it. Okay, for this timestamp, this was the state of the file and these are the changes I have put in that file. Okay? Yes, we'll be practicing all everything will be hands-on only in Git. Git. Okay, it will now no more everything will be hands-on. Nothing will be boring. So, Git is a tool that automatically saves versions. It lets you know who made the changes. Okay, a simple definition Git is a tool that takes the changes in file over time, right? It's a tool. So, it knows who is making what changes at what time. Even seconds also it it just is here. Okay? So, you can have Git installed on your local also. Okay? And it will keep a copy of the project on your computer on your server. Okay? You can install Git on our local also. Okay? So, why do we use Git? We we use good Git to track the code changes, work with the multiple developers. Okay? And if anything I do crashed, right? We can go back to the previous version. Okay, now suppose one developer Okay, he pushed the recent code of version four suppose. And because of pushing this code, pushing means committing. Committing means just merging that code, right? Into the main project. The entire application crashed, then what they will do? They will go back to the previous version, right? Because now the entire users are facing problem. So, what Git will do? It will move, right? It will deploy this version. So, Git is helpful there. Okay? So, it will go back to older version. And it has it is a safe backup of code. Otherwise, now 50, 60, 100 employees are working, right? On a project. How will you manage code? This is very important. We'll go through this. Take a moment. This is the advantages of Git in testing. Primary use of Git in testing process is all of these things. When you'll be writing automation script, you need to know in automation script what code have got changed. You will be working in automation script with multiple developers, right? Multiple multiple auto automation testers, okay? We are supposed to be designing a framework. You'll be working with some other people also. Right? You would be avoid overwriting other people's code. Can go back to older versions. Right? Some of your script is I think freezing the entire so many test cases, right? Then we can go back to older versions, right? Backup of the code, okay? All of these things. Same purpose for you also as a tester, okay? Basically related to code. Okay. Suppose if I ask you to write your name on paper, right? And erase it, and rewrite it. Can you see the older version? And can you see who have erased it? Can you do that? No. But Git can let you know this. It does this automatically digitally. So now, how to see Git is installed, okay? I'll show you all of that. So this is the command terminal. First, launch it, come on this is screen, and put in chat if you have got this or not, okay? I don't mind really anything Ashika or anybody here, okay? Okay, please. You can take me on funny note, okay? The thing is that, you know, you guys can ask me any question, okay? And I understand because you guys have taken up this course basically for you to upskill and get somewhere, right? So I I have many learners, right? And not only you guys, I take a lot of webinars, and there are many people who are really looking out especially for jobs and all, right? So I really do feel for all of you, and see, it's don't feel anything to ask question. You can ask me any silly question, okay? So, you can ask any silly question, also. If I don't know, also, I'll tell I don't know, but I'll always come back with answers, okay? Okay, the lab environment is in currently in stopped state, Namrata. Cannot connect to the lab until So, if it is not starting, you terminate that instance and start a new instance. You will get used to it in few days, okay? You are at the red screen. Great. So, you should be at that red screen. You can call it this red screen or whatever screen you want to give it a name, that's all up on you, okay? So, this is the screen, okay? So, you can see that this is the virtual machine. This is an Ubuntu machine. You can see the date somewhere afternoon timing. I don't know where is this being deployed somewhere in I don't know. It's an afternoon time there, right? So, what do you have to do? This is the terminal, okay? Which we will be opening later. So, another important thing about uh this screen is that you need to keep moving your cursor for some time, otherwise otherwise this gets idle. All your efforts will get So, it's compulsory is nothing like compulsory, but we like the we being the trainers, okay? we have to showcase things here. You can practice it wherever you want, okay? So, you know what is Git? Uh yeah. So, Git is You understood what is Git? Suppose now if I ask you to write your name on a paper, you erase it and then rewrite it. You can Can you You cannot see the old version and you cannot see the who changed it, right? Suppose you wrote your name as as uh suppose uh you know, something like uh John, right? And then you erase it and after that you you put it as uh as something like uh as Shweta, right? Can you remember it first what was written and then second You You not have any kind of proof, right? So, you cannot you you you are actually not having any kind of tracking tracking kind of thing, right? But Git can do this automatically without me taking any kind of headache, okay? So, now we will be actually working on installation of Git okay? And we do not need to install Git now. If you were working on on your own laptops, I would have told you that we can go and install Git. Okay? So, Git is like a camera. Okay? It takes always keeps taking pictures, snapshots, okay? So, now suppose I have saved this document till here, right? I'll go to file, I'll save it, and I am closing my laptop. So, what Git will do? It will take a camera kind of it will take a snapshot of it. Version three, right? So, tomorrow if you're saying that you this there is a code, right? There is ABC file {dot} Java file, okay? Just let us take it a little bit technical. And here you have made some changes in the code, right? And you're pushing those changes into the main repo. What is repository? You don't have to get scared about these terms like repository and all. Repository means project folder, okay? Repository means project folder. So, if you're pushing some changes after making some changes in the code in this file, right? You're saving some changes, then Git will automatically will take a you know, Git will automatically will take kind of a version. Now, we are going to actually bring the we will do the account setup. First, we will we will that is already created actually, okay? Git account is already Git is already installed in the in your lab, okay? So, that is already installed, I'll show you. Okay? Next thing is that that I'll show you again. Next thing is GitHub, okay? So, what is GitHub? Actually, there is a little bit difference between Git and GitHub. So, Git is actually saving versions. Whatever you're doing locally on your system, it will always keep saving, right? So, Git is something which you will install on your laptop and it will save whatever you're doing locally on your computer. It will track the code changes, okay? But, what if you're working with 10 different people, right? 10 different people. What will happen, right? So, for that purpose, we will be using GitHub, okay? So, GitHub is an online platform where the developers store, share, and collaborate on code using Git, okay? So, now I will ask everybody to create an account on GitHub, fine? So, GitHub is an online platform where developers store So, Git you will be installing on your Yeah, everything is free, guys, okay? So, GitHub is an online platform where developers store, share, and, you know, collaborate all together, right? Suppose now I want to share my code, okay? Right, going forward, guys, I'll be sharing you all my Java Selenium code. How I'll be sharing? Like this. I'm showing I'm showing you one example. Can you all look at it here? So, this is my 1 minute. Intellipaat demo Git, yeah. Can you see this? This is my GitHub account. Can you all of Can you see all of this? Uh this is my I think I've already Yeah, I'm already logged in, right? Can you see this? This is my GitHub. These are the repositories. Can you see repositories? I have created 12 repositories here, see? JavaScript code, HTML code is there, CSS code is there, okay? And 40 app, whatever, blah blah. HTML is a Playwright code is there. Okay? So, these are repo. Repo means repositories, okay? If I open Let me open one 1-day Python. So, Python code is also here. So, see? NumPy, Pandas, right? All of these, okay? See? Can you see? Commit. First commit 2 weeks ago. So, this is coming from my laptop, which I developed on my laptop. From my laptop, I pushed this code to the GitHub. Why did I do this? So that I can share this code to my students, to my learners. What's the point of having code on my system, right? And here on this GitHub, people can even download this code and they can also start collaborating. Okay, they can also add few more files here. So I will be showing all this practically to all of you in this class. Now, Agile was all theory. We will do all practicals. Okay? And you will also be doing practically. So you also need to go to GitHub and you need to create a GitHub account. So GitHub is like a Google Drive for code and teamwork tools. Okay? So why do learners use GitHub? So that they can store the projects online. Okay? So see, I have this code on my system also. This one, JavaScript. Okay? The code this is Playwright code. Okay. Playwright code. This code is there on my on my laptop also. Why I why I have it here? How do we create it? I'll show you now. Okay? So that I can share it with you. I can give you this link. Can you see this link up? This is on the cloud, right? This is on the cloud. I will share this link with all of you. You can download my code and you can use whatever I have created. See, you can download zip and you can collaborate to it. You can use my code, right? Great. So did you understand what is GitHub first of all? Please don't go too much deep into all other things. Did you understand what is GitHub? Okay? So think of you're like you're creating a login project. Right? So if you create the code only on your laptop, your laptop gets tomorrow crashed or something code is lost or some thief came and stole my laptop, the code is lost or not? Make sense? Right? But what if I have already uh checked my code from my laptop to the GitHub? Then even if my laptop got crashed or the thief has stolen my laptop, right? I give her them because it's I it's on the GitHub account. I go anywhere, I just log in. Just now I have logged in to the GitHub I have shown you, right? Everything is safe. It's free. Git and GitHub both are free, open source. We do not need to pay a fee to anything, okay? You can access it from anywhere and and share a link with others, okay? Okay, so now we will create a GitHub repository. Create a account on GitHub, okay? Let's all do that. So for that guys, I'm going to the You please all go through your lab only. On the lab if you can see, this applications are there. Here internet is there, right? Google Chrome, open that. You just put your password. Okay, so here you can open GitHub. So it's very old GitHub. Okay, put here GitHub. Just put GitHub. So sign up for GitHub, okay? Like this. So please you can continue with Google also if you have Google account or you can create a username password, okay? I'll give you the steps, guys. You want beautiful steps, I can give, okay? So type github.com in your browser. On the top right corner, click sign up. You will log in through your Google email or you can use a valid email, put a strong password, create a username. Username like I uh like to create it, right? Shweta demo get here. This is a username which will show up, guys. Like this. This is the username. This is my username. Shweta demo get, okay? Use a username like this. Or you can continue with Google Google, okay? And please uh sign up. Create an account. I have already created it, okay? And then uh some verify account will happen. Some captcha will go or something. You can connect. Um email verification happen. Okay? Like that. You can You have to choose a free plan. Okay? And then, your account will be created. I'm putting all the steps, guys, for all of you. So, it will ask you, "Are you Are you learner or a student?" Something. You can choose, "I'm a learner." Okay? No need to add any this thing. Just keep basic things. Okay? How to create folder in GitHub and all? We are going very step by step, Gauri. Please hold on. Okay? Let the learners first create an account, then I will go to all these things. If I start telling all these things, yeah, we will need GitHub, actually. That's why we need to create an account. If you do not remember your password, you can click on forgot password, and you can see. Okay? So, these are the exact steps for creating a GitHub account. Creating GitHub account. Okay? First time, one-time user activity. So, guys, I'm moving ahead. Every details I've shared here. Okay? What is the email ID, right? Email address and password. Okay? Email address will be like this. @gmail.com. Fine? Okay? So, username must be unique. Fine? So, this is something which you can get. Choose a plan which is select. Now, create a sample repository. Okay? Now, I think sign up is there, right? Go back. I think everybody have logged in, right? So, now, login with your uh Okay? I'm just logging in. Oh. See, authentication some bug have uh so, that I've gone. So, I'm entering the verification code 323. All right, so see here. Can you see? It have come here. Okay, can enlarge it. So, for what you can do, you can create a Can you see? Click on this plus icon. Create a new repository. Can see that? Just see that. Test Git repo sitory. Just create it, guys. Just to see, okay? First repository creation. So, this is description. I'll just say for demo purpose only. Okay? Fine. And then uh make it public only and just say create. Fine. Just created, right? The test Git repository is created. Now, if you click on those three icons here, here. You click on home. Okay? So, you can see uh you can see all your repositories. Okay, click on show more. You can see test Git repository is also here. For me, I have so many, so it is here. So, this was setting up of GitHub account. Okay? So, what is GitHub account? Now, you know what is GitHub account. Okay? And uh we will upload some code here. We'll commit changes. We'll do all that in later. Now, we created a GitHub account, okay? And there is a difference between Git and GitHub. Git is on your local system, okay? Now, uh we will be actually installing the Git uh uh locally, okay? Here, the Git is already installed on your lab, okay? So, how to check if Git is already installed? Okay? So, please open up the terminal. So, how to check how to open up that that terminal here. Go to you can come here. See? If you click down, this is coming. Terminal terminal emulator emulator, okay? Click on this. Right? Type here Git {hyphen}{hyphen} version. And enter. Right? So, you can see that already the Git is installed here. And Git version is 2.2.25.1. So, using the command line line, you can see uh what command you will enter? Git {hyphen}{hyphen} version. Okay? This is the code to check if Git is already installed. Okay? Check Git is already installed. It's already installed. We do not need to install it, okay? You will just type here. And you what you will get? You will get some version. So, here we got this version. Okay? I'm copying this and putting in the copy and I'm putting here. This is the output. Right? If this is not installed, then you will get some not this software is not recognized that on the system. Can you please show again? Yes, I can show again. So, go here. I'm closing this guys again. So, there is if you over your mouse down, you will see this black color terminal emulator. This is the command line. Okay? This is the command line for your machine. Click on this. This will open up. Here you have to type Git space {hyphen}{hyphen} version enter. So, Git is already installed. So, now we will see some practice, okay? How to see how how the Git is taking changes. We'll do some practical hands-on things, okay? I'm writing this for you. Okay? Next thing we will do is that if Git is installed, we will configure username and email. Okay? We'll connect to GitHub. We'll create your first repo. Okay? So, now we need to do uh tell the Git who you are. Right? Now, this is Git uh installed already on on your system. Right? I cannot see this terminal emulator. The terminal emulator is here. I'll show you one more time. Uh just a sec. Here it is terminal emulator. This one. Can you see my mouse is forward down bottom middle center. Okay? So, this is the second thing. Okay? Second step here. Configuring Git username and email. So, this is one-time setup. So, this tells who you are. Right? So, we have to configure your name and email ID on the Git. Right? How do do this? There are some commands which you need to take care of. Okay? I will not do this because it's already done from my side. Okay? You need to do it. So, this is the command guys which you need to execute on your system. Please take care of this command. Git config hyphen hyphen global user.name your name. Okay? I'm not going to do it because for that account, it's already done. I'm going to paste it here. Okay? So, you can directly paste it here. Command is Git config hyphen hyphen global. Okay? So, you just focus on whatever I'm teaching. User uh okay? dot name. Okay? And your name. Okay? Your name. You need to put your name here. Okay? So, what is your username? Okay? Suppose your name is Rahul Sharma. So, you will put your user your name Rahul Sharma. Okay? And then you need to actually set up your email ID also. Okay? So, for setting up email ID, you need to put your user.email. Okay? And then you need to add your email ID. Here, which email ID will go? The same email ID with which you have created your GitHub account. Okay, email ID of GitHub. This also you need to add. I'm going to put it here. So, this is an example. So, this is an example. Right? Next, you have to configure your email ID. Step three, this is very important. Fine? Any confusion, let me know. Okay? This is the example. After this, you have to verify the configuration. Okay, how you will verify the configuration? Step four, verifying the configuration by running this code. This I will run it. Okay? I'm running it on my this thing also. Verify config globally. Okay, I'm not doing all of this because it's already done. Okay? So, Okay. So, that all data is already erased, guys, from my machine. One more thing I would like to tell you guys about this sandbox environment is that I forgot to tell you, which might be little annoying. Okay? GitHub is not listed on the command. I only have the first line. I didn't understand, Kazem, that line that question. GitHub is not listed on the command. GitHub will not be the command. Command is whatever I'm showing you on the screen. Git {hyphen} {hyphen} version. It starts always with Git, not with GitHub. Okay? Richard, is it username or my name we're configuring? Your name only, whatever you want. Okay? So, guys, I'm configuring my username again here. So, you can see what I'm putting. Okay? Now, I'm putting my So, So, whatever you enter here in the machine, machine will forget after 4-5 hours. Okay? So, all your efforts will go waste. So, don't get angry because I have taken one name. So, your name. So, my name is what? Shweta, right? So, fine? Okay? Next, I'm I'm configuring what? What I'm configuring? My email ID, right? So, what is my email ID? It's Rahul bug 2308 {at} the rate gmail .com. So, you can see what I'm doing now. And no need to worry. You can do this later when you are free tomorrow. Okay? You just see what I'm doing now. Email. Okay? Because some of you will get I've configured. Now, I want to check whether everything how many things have been done. So, you can just do config list. Can you see? So, now when I do GA git config global list, what it is giving? What it is giving? It is giving me the users. Okay? So, give git config user list means configuration is done successfully. Okay? So, this is connection is done successfully. So, if you're getting if you're done properly and if you're getting this output, that means configuration done successfully. Right? So, fine. That's fine. So, by doing this, Git knows who you are. Okay? Now, let's create a directory. The fun will start now. Okay? And this is done. Okay? Now, whatever you do on your sandbox, we'll know. Okay? Now, I'm going back to the sandbox. And so, I'm putting already in the my notebook everything I see. Tomorrow, if you go and sit peacefully, you know, this is the format. This is the command. Okay? This is a command. Understand? Okay? And this is the example. This is the command. This is the command. Okay? And this is the example. Okay? Understand how to read this book? Okay? And then tomorrow do the same thing. Understand now the concepts. That's very important. Whatever I'm doing, just trying to do with me will leave you not understanding also, confusing also. Okay? Don't try to do those things together together. I have given you a simple option. Please log in through your Gmail, which will capture and all. See, capture you have to do it all by yourself. You have to see whatever is coming. Okay? And if that is a thing. Okay? And if there is anything which you're stuck, please send the screenshot of that in the chat. Okay, I'll look into it. I'm not getting any pop-up from you that Yeah, Ashika, no problem. Yeah, where I can find this file that you are creating? This file I will share at the end of the session. Okay, don't worry. Right now, please focus on the session. Understand the concepts at the first time for all of you. Git is very important one DevOps concept, okay, which you're learning today. So guys, this is all about configuration we have done. Now we want to proceed with GitHub commands. Like how we'll create a directory, how we'll try to start tracking it, right? All real-time concepts will come. Only Agile was theo