Functional Testing Automation Full Course 2026 | Functional Testing Automation In Java | Simplilearn

Key Takeaways

What if you could understand the foundation of every web page and see on the internet from headings and paragraphs to tables, list, 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 web page 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, list, 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 context correctly, and also how different tags work together to build a complete web page. Also, just a quick information. If you're interested in building a successful career in fullstack development, don't forget to check out the AI powered fullstack developer program. This course is designed for aspiring developers and professionals who want to master the mer stack while leveraging the latest generative AI tools such as chat GPT, GitHub, Copilot, Amazon Code Whisper, and Hugging Phase to enhance coding, testing, and deployment workflows. You'll gain hands-on experience to 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, backend development, database management, APIs, cloud development and AI powered software testing. In addition, you will receive Microsoft learn access along with official Microsoft course completion certificate and transcripts. With AI powered resume building, LinkedIn profile optimization, mock interviews, and simply learns 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 pin 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 T body? 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 know 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, get MySQL. Okay. And then we'll be covering HTML, basics of HTML, then basics of CSS. Okay. So I will be u got to know here. So I will uh I will be teaching all this JavaScript. Okay. And then Cyprus. Okay. So all these things we have to lot of things here. Okay. So we will be touch piecing 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 uh project where you can be an automation estate developer QA engineer right here are some there are some people who are already some worked some real realtime 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 mummica I have told right so going forward the path will be to cover agile get MySQL okay basics of HTML CSS okay and then we will be covering um Cyprus okay so this is for the phase one phase two we'll be starting with Java selenium and all those Okay. So this is a plan for the phase one and I think in the last uh 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 buminga 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 um okay u planning and automation at phase planning and automation. Do you all have this course? I hope everybody have got uh simply learned um 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 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 ebooks ebooks are there right and you can download this lab guide also there's a download icon right and download these practices also okay so download these three things okay so take a minute or two and please download all these materials practices are not visible to you okay it will be visible to you okay practices because uh these are the things from where I have taken all the BPT and stuff okay and that is what I will be referencing and from there only I will be teaching you okay and this is the 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 few things on the G9 all directly that's different practice option assisted practices okay the practice um should be visible and these This option 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 after the session for that. Okay. As of now please open the ebooks. In the ebooks you will get uh the first ebook of introduction to agile okay you'll get that uh you can click on that okay so we are going to start from there introduction to agile please click on that there is trainer PPT also okay phase and projects once again we are going to start with okay I'm just going to open the PBT only if I if I I have uh the downloaded the ebooks just let me download the ebooks I have the PPD but I prefer ebook. So I'm just downloading ebooks. Just one minute. Okay. I'm just opening that now. Go download 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 EP. 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 we I'm going to talk about SDLC first. So even before I talk about agile there is something called a software development life cycle right. So any software right which develops in any company. So here there are many beginners in this room correct. So I'm setting the context before I start into agile and 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 teenager years 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 the life cycle of human beings similarly a software also goes through different phages in one day nothing have got developed right if you see so many applications around it fine 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 it gets developed through some phases. So what are those phases? Let me talk about okay so first phase is the 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 highle 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 is called is 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 I'm going to teach you. So we'll keep it very short and crisp. Okay? And we will try to focus on these 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 now order two. Okay. But in this course of yours we have specifically focused agile because now 99.99 projects across the world IT IT projects are using agile as DLC 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 the agile method methodologies to comprise a series of frameworks. So agile methodology is a way of project management and software development. Okay. And it consists of series of frameworks. Okay. So there are lot of frameworks which implements 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 do you develop everything at a time and give it to me? No. So what you are going to do? So suppose for the first two weeks you're going to develop the home login page. Next two weeks you're going to develop the homepage, right? So like that if you're going to develop something like that, right? Login page. Then after that you're going to develop homepage. Okay? In the first two weeks if you're going to develop the login page, next two weeks you're going to develop the homepage. Right? If the development happens like that develop means both development and testing. Okay? You're developing this functionality of login page and next two weeks you're developing and testing homepage. Right? like that if you keep on developing and uh 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 are 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 two weeks okay because that's the that is the that is how the development happens in agile okay you 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 two weeks I'll do login Next two weeks I'll do homepage. After that I'll create the search functionality. Next add to cardart. Okay. And after every two weeks you will tell you will showcase that to the customer that we have done this. Okay. So this kind of actually uh development brings uh customer feedback. Okay. If you have not done something what the customer likes, he can give some suggestions which you can incorporate in the next spread. So there is lot of flexibility in terms of incorporating customer suggestions right. So that is why this is agile. Okay. And there are lot of frameworks which implement this agile methodology. Okay. Like there is u uh scrum one of the very famous framework. Okay. Scrum framework is there. Safe is there. Scale agile framework. Okay. Canban extreme programming all these are there. Okay. So John have to uh 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. So for that he have to learn few concepts which he'll be learning in this lesson. Fine. So 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 in 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 gel testing. Right. So here what happens? You do the work in sequence. Right? So this is for two weeks you develop something and you deliver. Right? Next two 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 par. Okay. So this is what it means. There 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 suggestions for the improvements and process. Okay. So any agile uh process 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 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's lot of collaboration and all these things which happen. So I will tell you how these things happens when you will go through all the other slides you will 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 are going to automate something which we are 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 uh 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 uh 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 these 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 that the story is already written here we can see here. So these are the manifesto for agile software development. Okay I hope you can see the screen right. So this is the manifesto okay for agile individuals in interactions are prioritized over processes and tools okay in agile these in we believe that more focus should be given to the people's 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 over the more over the right hand side customer collaboration over contact negotiation and responding to change over providing 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 two weeks you're developing something correct and in every two weeks you are going to get the feedback from the customer right so there you're getting working software and customized collaborating also every two weeks right and if the customer is saying that this thing they don't like in that two weeks they are not liking this particular thing whatever the developer have made then they can change that in the next uh in the next uh sprint or in the next upcoming week right that is responding to change okay so this is manifesto same thing is here in the slide okay related in a little but different way but same thing you want this I can send you the 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 If you want we can have a look at it. So this is not uh this is actually not a very uh you know this um uh agile is very theoretical. So I'm using this PDF. Other topics we will be directly using helps on. So we will be uh using directly I will be using my runbooks and I will be teaching through the uh lab. Okay. So it will 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 talk where I'll be writing and teaching you. Okay, we might not be using all these PDFs much. Okay, you can use it through rapper at the end of the class. Right, this is very theor theoretical, right? I cannot uh I mean just uh show you through lab all these things, right? So now um there is something called as uh uh okay yeah where is it? Yeah, here agile methodology, right? Agile project management techniques involves communication and iterative development. I told you right iterative development just now I told you I think uh she just asked me right so we developed 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 sprint I developed login second sprint I develop homepage third sprint I develop the add to cart 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 a project can be improved continually throughout its uh cycle and changes can be made swiftly and appropriately. Okay. So this is what it is. So this is a 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 2 weeks you will give a demo to the customer and to everybody that what you have developed and if there are any changes required right you will do the changes in the next sprint so this brings lot of adaptability flexibility and emphasis This here the customer is the god right whatever customer will say we'll do. Now let's talk about differences between waterfall and agile approaches. Now 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 what all I told these phases were there requirement gathering correct? So requirement gathering was there and uh system design will be there right and then your uh HLD LLD everything was there okay and uh but these phases will be happening sequentially okay in requirement uh 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 waterfalls from a staircase like that or waterfall right here all the phases are You can see development uh requirement gathering design development testing then deployment and mandator. 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 this cycle and then only you can go back. Okay, that is why we can use it only for simple projects where requirements are simple and stable. We cannot use it for those kind of requirements where requirements are fastly evolving and customer is fastly changing requirements. We cannot go back because of the nature of this model. 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. We 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 Zumato is bringing this change then will say that I'll bring this change. Right? Today if this car if this car is bringing this change maybe in another one and a half month 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 uh the competitors in the market right and if they don't change my 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 remodel approaches. Now there are no more waterfall and V water. 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. Takes a step-by-step method. Waterfall technique is a method of sequence design. Okay. Agile technique is well known for its adaptability. Right? So as I told you that uh after every two weeks you can uh take the feedback from the customer okay and you can take the changes also from the customer and it's very flexible and agile on the other hand waterfall you know is structured sequential right flow it can it is very rigid rigid means anything happens in between I told right it cannot change or to go all the way down right next one agile can be thought of as a collection of many projects right so here wide 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 the original planning has been accomplished once the project development begins there is no VA 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 lovely framework. Okay, please go through this guys take two to three minutes. Now we are going to discuss about scrum. Okay. So there are different frameworks which are there in agile. Uh scrum is there, canban is there, extreme programming safe scale agile framework is there. The what is framework? Framework What is framework? Framework is basically uh basically something which gives you some guidelines okay or some rules like for example there is a the game football right we call it as football because it has some rules or it have some it have some steps to follow right so yeah you are parish 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 by by producing high value solutions in a com 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 process and technique can be used. Okay. So what is scrum? Scrum displays the 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 consist 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 the 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 is not just a facilitator actually he is more than that. Okay. He makes sure that the team is following the uh agile best practices. He makes sure that the team is following the uh following the scrum uh 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. He made sure that the team is using the Jira in a hygienic way, right? And uh okay. So this is uh this is this is what uh 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 uh website just like ISTQB in India. Sorry internationally uh accredited uh organization which gives ISTQB foundation level and so many other certifications right you heard about it right website is not visible on this. 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're making some tester some developer as some master that is not the correct thing okay I'm pinging here for you guys that is not the correct thing okay scrum master should be your 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 XY Z as uh 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 is correct you are correct not only facilitator he is also a coach for the team a mentor for the team it is his respons responsibility to remove all the impediment, 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, where did you do this work? No, he have to work with the team. He makes correct processes. He makes the team crossunctional 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 asking do you have the certification or not. If you don't have any certification means go. Okay. Product owner he is a BA business analyst. Basically this person is from an MBA background who is having some uh special expertise in some domain like finance domain or marketing domain whatever your project is right. So he's the one he will be in constant communication with the uh with the customer and he's the one who will be actually uh doing um uh all the requirements gathering right and he's the one who will be taking care of uh creating all the making all the requirements in the Jira. Now Jira is a product is a requirement uh is a project management tool. Okay. I'm not sure if I have the Jira account. Jira account still with me. I'll just see if I have Jira one. Okay. So, this is a Jira. Okay. Jira software and you can also download. We 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 an website Atlassian. Okay. Atlasian is a 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 um developers it and all. So it it have uh it 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 uh continue. Okay. So for me it is not showing pi 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 are free you can try this okay right now you can see is uh okay I have created one project here Astro Right. So this is the uh this is some project which have been created. Can you see? Scrum is the framework. Jira is the 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. Curve 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 that 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 u all the all the requirements of for that particular application. And here they are creating they means who is creating. So you can see this is a ticket. This is one user story right now by 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 where it is gone. This one product owner. So product owner creates all the requirements in the product backlog. Okay. And he keeps it updated. Next is the team. What is the team? Team is made up of developer plus Q. 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 certified scrum master, right? He's a 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 know how to estimate the story properly and all those things right 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 uh the developer and testers knows how to uh uh how to accept right these are the suppose now there is a login requirement right and login requirement he will write that if you enter username and correct username password the homepage will be visible. Now he will also write that you cannot enter uh if you enter wrong username and correct password you will get an error page with this description right so all these things he will end in acceptance criteria so that the developer and 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 is 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 by 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 hands meeting with the team in understanding the requirements backlog refinement meeting and all those things happen. So I'll discuss about that going forward. Okay. The team the team is crossunctional and self-organizing and implies the team is what the team is 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 a 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 member's 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 the programming design, right? The team entire team, the developers do the programming design and improvement of the products. Even the even the testers are also part of all the design and uh backlog grooming backlog refinement sessions. Okay, kickoff feature kickoff sessions. When I'm talking about backlog refinement means the product owner is talking about the features uh features okay functionalities or the gert tickets okay anything you can say or the background requirements okay so this is this the this results in collaboration and the entire team works together as one agile unit okay to determine the best development strategies using the data so the team is uh in a position that they develop the product using the best development strategies is due to the data right. So they have the sufficient data and based on that datadriven decisions they take they develop the uh best product okay including testing product and prototype as well as other methods include testing products and types as well as other methods. 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 a 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 now now the real UI is not developed. So what I will do before that I'll create a prototype. So the pro 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 homepage 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 two weeks. That is the sprint uh sprint one. Next sprint next two weeks you're going to develop the homepage. That is the sprint two. Okay. Next two weeks you're going to develop the checkout 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 uh PTM or some kind of wallet or Google API that will happen in the sprint 4 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 uh this two 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 In most of the companies it is 2 weeks. Okay. It's not one 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 two week. Okay. So sprint one started on 8th December then 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 that make sense? Okay. 16th Jan. And I have to change the year also. Okay. And then this is the uh 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 okay and testing. So 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, so in this 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 events or meetings anything you can say. Okay. So these are scrum ceremonies or events or meetings which happens okay within this two weeks times. Okay. So first is the daily standup. Okay. So daily standup as the name suggest will happen every day. So this is time box 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. Right? Product owner is not mandatory. His pres presence is not mandatory. He attends 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 uh daily stand up between uh issues or blockers right? So if she says that if she have any issues or blockers then the scrum master's duty is to uh unblock her. Okay. It is his duty. Okay, is this clear or any doubt here? And it's in the daily stand up. 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 a 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 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 estro. This is your backlog. So backlog is the 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,000 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,000 requirements based on how much requirements the product owner have created. You will not have the option I think to create the tickets. You might not be able to see this option only. Okay. No, it is not future or pending works. Yeah, but these are the requirements which might be implemented in the coming future. Okay, so this is the backlog. Backlog means requirements. Okay, so backlog 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 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 confusions, you can ask. So in real time what will happen is that uh 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. You can see this option start sprint right. So this is the sprint option. Uh this is the sprint name. He will take whatever tickets as per the customer's priority. You'll pull up those requirements. Now for the next sprint we need to develop the homepage. We need to develop what we need to develop homepage. Right? For the next sprint, we need to develop homepage. So all the homepage 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. So whatever number of requirements. Yeah, it will be drag and drop. I can show you. See either you can right click on this. Right click. Can you see? Move the work item. Suppose I want to move it to sprint one. Can you see I just moved. Can you see it went up? You can also drag and drop. Can you see? One minute. 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. So 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 users to. Okay. So 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 e-commerce user I want to log application okay now what you will achieve so that I can access the page. So this is my guys uh the user story description right every user story will have some uh you know acceptance criteria also. So all these things are not here in your uh 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 uh you know successful login with valid credentials. Okay these are some what is acceptance criteria? acceptance criteria will tell you okay yeah you're correct uh chakaj so near d I'm 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 attemp attempt must show error message. Okay. So this is some acceptance criteria. Okay. So this is about the acceptance criteria. It can maybe be many other things also. Right. So this is if you can go and create. So I have created a story and it have come to here. Okay. So this is how the product owner will basically create guys. Okay. And u in product uh backlog refinement what will happen? Suppose now the team have come up. Okay. So what the product uh uh owner will do? He will click on this ticket. Okay. Login feature. Okay. And he will discuss uh about this ticket. Okay. Suppose now this ticket is there. We'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 uh after uh after getting this functionality right the bigger picture this is very simple thing which I have written login in your uh in your real time in your realtime 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 and what you're going to test. If you have any doubts or confusions during uh the feature development, you can directly 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 backup requirement is that if the team does things that this particular ticket right this particular ticket is very big it's very huge ticket which cannot be done by uh the team in one uh 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 uh 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 right so which is at the highest priority will be kept at the top of the stack then the medium priority 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 So basically on Tuesday or Wednesday. Okay. Tuesday or Wednesday. First half of this sprint. Okay. PR back. Fine. So once this is done the next uh scrum event which happens is sprint planning. Okay. So what is sprint planning? So in sprint planning you will be planning 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 you have to do? In the next sprint you will be doing homepage right? So this is one one example which I'm explaining. Okay. So in the sprint two what you have to do homepage. 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 homepage we will plan about the homepage in the current right. Planning is always done on sprint before. 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 but you should plan for the next sprint also right? You will do the you should do the planning for the next sprint. In next sprint what is coming? Homepage. 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 homepage basically. Okay that is the sprint planning. So in sprint planning is a event which happens in the second half of the sprint. Okay. So first of all understand when it happens when do the sprint planning happens. Sprint planning happens maybe on the witness day or Tuesday or witness day. Same thing Tuesday or witness day. Okay. In the next half of the sprint. So what will happen in 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 on the homepage. So this is suppose the upcoming sprint right? Suppose now I take this and put it here this feature ticket. Okay. Say fine. And suppose this sprint this sprint is going to start from uh 2 weeks and this is going to start from 19th January here 18th January to 1st F 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 who 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 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 I 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 the 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 the 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 1 2 3 4 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 sprint backlog is nothing but this one right. So this is the backlog. Backlog means the tickets under the sprint. Right? This is the 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 better backlog and this is the input for your sprint planning. So what will happen? The super master will open login feature. Everybody will see this features will see this ticket will see this using 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 are going to use fibonaci numbers. 1 2 3 5 8. Okay. Story point is fibonaci numbers. and story point does not means mandates. 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? Homepage. 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 search for master will open and the entire ticket team will go through this ticket and they will start estimating and jira and and in agile we estimate through story point. Story point is not mandates mandates. So in sprint uh in in in the scrum we do not estimate in men days in 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 or work for the first time. 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 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 take. 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 the mathematical series. The series is called as Fibonacci series. 1 2 1 + 2 is 3. 2 + 3 is 5. 3 + 5 is 8. So you can go to chat GPT 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 + 3 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. Right? That's the fibonacy. Okay. So now suppose if one developer 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 of the persons who have given maximum and minimum. Okay. So if another one says one another one say five circum 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. I am here as 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 have 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 revote 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 were they going to vote for two on a mutual consensus. Okay. So then after that he will go here to 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 honored or team members work in the same team. right in the same company. So on or in the same place. Okay. So this technique planning poker is used. Okay. So story point is used for estimating the story label tickets. Okay. Fine. Is this clear to everyone? So scrum master will set it to the meeting. Every story requirement is estimated. Estimation is done using story point. Story points are nothing but bonus series. Okay. Now if somebody is saying this ticket is eight story points that means it is very complex and there are lot of unknowns in that ticket means some 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 I see some questions being here we need this material name for future reference uh so going forward I will be running this PDF runbooks only with you no problem so since this was my first class right so and uh it is first class it will take some time to get used to uh meanings this is the agile topics it's theoretical concept I have all the documents with me don't worry I have lot of content with me to give to you if you want okay so I thought of teaching a j from PDF only but in PDF things are little bit differently written okay it's uh uh little bit differently in a way it is written as little 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 is also estimated 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 so if you if I say that this is story is five story point that means that ticket is pretty heavy right it's more uh complex it is more uh size of the ticket is more and it is also little more lot of uncertaintities are there it is 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 Here you can read this guys. Okay. Story plan print planning. We'll read this for a minute. Okay. Then we'll move to the next point. Priority severity. No, it have nothing to do with the priority and severity shani. Priority is from the ticket set like how fastly we want to tell 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 script. Okay. So we have to plan it in such a way that suppose I'm taking uh story user you I have assigned two story to you. You should be completing those two stories within the sprint. So if you're taking one very heavy story then I will assign only one very heavy story to you. Okay. So that is a whatever we have planned right to finish it within the sprint we should be completing it within the sprint. So that is the sprint goal. Okay. Next is sprint review. Okay, what is sprint review? So, sprint review is another scrum event which happens on the okay jadaav story points and tickets epics or bucks will be matched with each other estimates. No, epics and bugs. Epics does not gets estimated see some some companies they are not they're estimating in uh story points and some companies they're estimating the epics in uh t-shirt sizing like XL, triple XL, 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, uh 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 uh estimation. Okay. So uh epics are usually estimated in excel sites like medium, excel, triple xl, small like that. Okay. So next is sprint 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 will happen on the last day of the sprint. So when it will happen so it will happen on 16th January. So it will 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 your project directly or indirectly is a stakeholder. Right. Right. Stakeholder means anybody who is involved with your project directly or indirectly is a stakeholder. Okay. So PO is a stakeholder. Okay. And uh the customer can be a stakeholder or uh the engineering head can be stakeholder. If it is a small startup even the CEO can be a stakeholder. Right? Anybody who's coming and asking you about a 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'll give a demo. So for now example uh let me see what all are the participants. Hersida hersa is there right? Hershitta and uh have developed something. Okay or somebody have done testing also anything whatever they have done anybody. It's not like uh everybody who have done something they will come and will showcase their work. Okay. And the product owner will see their work will see the 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 a 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 given 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 signed team members will have to work on it okay so this event achieves continuous feedback why because even they are getting the feedback back from the PO they are 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 appreciate but I understand if you are saying that bugs get rejected that's a different thing no that is not u bugs get rejected no tickets will it will not get 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 have been done. Okay. And the tickets will not become rejected. Okay. Tickets can 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 the mistake of developer right. is the mistake of the customer only I mean right okay next is um last one is sprint retrospective okay few more thing guys I'm going to copy paste on the same document one minute just give me a sec yeah okay same do 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 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 there three columns okay so first column will be what went well okay what went where second column will be this one what didn't go well and third column will be for this action items Okay. So now the suppose there are five people in the team. So he will create five rows. Okay. 1 2 3 4 5 rows. And he will go one by one and he will ask everyone. Suppose now there is Romesh in the team. He will ask Romesh can you tell what went well as per you in this sprint? What didn't go well for you in this sprint? So you will say that okay this went well. I did do here. Okay. I got support from this team member and all. He'll say thank you and all that. He'll also mention he'll also mention that um one of his ticket didn't get finished because there was a dependency on another team for this test data or something and u he couldn't finish his ticket because of 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 with 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 the even the spread start. So he will do that. So 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 or this table. Okay. So this is all about the sprinter perspective. Any doubts here let me know. Okay. So I got some questions on get giving me examples on action items. Okay. And how the 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 uh he could not complete his story because the test data support. Let me give one example. Suppose the team is working on an OTT uh platform. Okay. OTT platform. Okay. What is OTD protocol? Like some like Netflix movie and all those kind of things, right? So there you have you have to uh suppose uh test some HDK content or ultra HDK content, right? 4K content, 8K content, right? So what do you need to uh 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 were 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 definfined process with the other team asking for all these things even before when our work starts. Okay. Even before we start our work our work means even before when our sprint starts we should also we should be we should be already be having these kind of test data with us. We should not be asking these things in between our strength because this can put at our work at the risk of spilling over right 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 we we we should be telling that team that hey we should not be sending through chat or through email that we want this right we should be raising these tickets on their board asking that we need this 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 the 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 the 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 is the best footballer, he need a coach. He still need a coach. Okay. So scrum master act like a coach. He will work with the team 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 access action criteria for login requirement. You can go through. Okay. Now issue types in Jira. So there are many some issue types at 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 you 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 appic called as account and registration. Okay, 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 2 to 3 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 and process 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 fun bits of functionality. Okay. And it will have 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 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 for 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 pooling 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 you understand point of view and uh 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 uh it's all simple theory today whatever is just theory nothing much technical we have done okay so don't worry about it. Next is user story. Right? User story you have already seen, right? I created one user story. You see Epic can go more than one spread, right? It's like a bigger umbrella. So can remember this. So this is the umbrella, right? This umbrella will have many user stories, right? Okay. Fine. 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 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 the feature so that what is the benefit of value you're receiving so I have given some examples please go through this and that will complete the business 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 I 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 problem so epic is a bigger piece of functionality okay which will have lot of user stories inside it. So suppose something you are going to implement which you cannot implement within a sprint. So you can create an appic and you can create multiple user stories into it. For example, you can create an app account and registration and you can create all the tickets related to account and registration and login into it. Okay, that is a what is user story? User story is a piece of functionality which is completed on the 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 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 uh user story we are related to functionality, right? So epic and these two minute let me show you again create right epic and story related to the functionality right or requirement now task is something related to nonfunctional nonfeature work okay suppose now if you have created some KT document okay or or if you have designed an automation framework okay or if you have uh created some or you set up the test environment and uh start up a 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? Zero. So, for that you will 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 or performance, testing 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. Right? Okay. So guys, this is all about the scrum. Okay. Now I have completed this. So there is a uh demo here to create a Jira account. Okay. I'll show you how to create a Jira account. Okay. And uh there are some practice here creating a backlog, creating new shoes, 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 to go to Jira Premium, right? So this is the website pinging you all. Okay. So you have to click on try free. So I will say sign in with a different class in 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 I'll show you how to access the lab okay come here go to practice labs you can do here go to practice labs sorry click on the practice lab okay launch app launch lab it will take first time 5 4 5 minutes it will take for all of you I have already launched so 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 I 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 okay. So now it is saying 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 um enjoy the premium free Jira features. Okay, you can practice, you can do whatever you want. If you go in any company you'll be using Jira. So we can do enjoy this feature. Okay. So I'm closing it. Fine. So this is guys no building nothing required here. Zero will fine. This is screen. Okay. Now you come here. Can you see J here? Click on this. Okay, it is saying create space. Space means a project. Now little bit have got changed already. I have created one project here. You can see panther. If you want to create a new project, you can create here in create space. 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 Chrome framework. Use template. Again it is asking what which you want. Company managed, team managed. Go for company manage. Give a name. You can write company manage. Then next. Okay. You 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 board came up. Can you see this is the board? I have another project also. Panther. This is the company managed. Okay. Background is empty. Nothing is here. Active sprint. Any sprint which is active. You can see here nothing is active. Okay. F right. Now let us create some ticket. I already showed you how to create a ticket. Right. Now please try to uh 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. It create some tickets which I have already shown you how to do that. Okay. Okay. Now let us uh create some ticket some dummy ticket. I think 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 problem. So 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 uh 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 right this is your first sprint maybe okay so you can add the how many weeks it is you can start date whatever and you can drag and drop the and you can start the suppose now I'm adding this to first sprint Move to one. Okay. Now let me close this guys. Right. Now you can start the sprint by this option. But if you click on start the sprint started and uh that ticket came in active boot you see this is how it happens in real time you will not be doing all of this scrum master will be doing master product owner will be doing will not be doing but I showed you yeah that was a part of them lab Jira I didn't see it what is happening in lab jera let me Okay, it have come up. So, lab zero 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 uh this basic things. You'll get like this. Say okay. You got up environment like this. So, this is 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 useful of using labs only. 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 came up or not. Same thing here also you have to do same thing guys. So 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. I 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? So, please click on that. Put some password whatever you can remember. And then 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 have shown you outside. Okay. Here also you have to do the same thing. Here also you have to do the same. You have to type at right now nothing is working. wall 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 some collection problem for me. Okay. So here also you can say atlesian. Okay. Go to 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 the only difference guys. Uh 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? So 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 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 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 this cheat book, you might have got in your learning tag. One minute. and your learning track. You would have got lab guide. This one lab guide lab guide right you can 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 icon appears. There is a lab document, lab help document. You have to refer that. Okay, please refer that. All the steps are mentioned there. Actually, everything is sometimes it see and you see the screen coming up. In that case, you have to just stop the you can click on this. Okay, RDP access. And then you have to click on this this icon. This one this pointed arrow can you see pointed 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 say 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 that there is an earthlike symbol that is the chrome. Click on that. You'll get a prompt asking for some password. Put the password as your uh 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 here. So from the interview point of view. Okay. So we we 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 question can be what is agile? Okay. And uh they can ask about and you can answer uh what is a child and you can also add what about agile and manifesto. Okay. to get some added uh weightage to your profile. Okay. So if you can talk about a uh 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. And 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? we 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 have which you have asked me now one by one okay so one by one ceremonies what are they they are daily standup DSU means daily standup okay fine then they can ask you about you can backlog refinement in backlog refinement um we can ask you when does it happens who does it okay and uh what happens in web refinement when does it happen who attends it okay so when I'm writing about this all these things can be asked so refinement okay everything they will ask sprint planning in sprint planning lot of questions can be asked so that I can tell you now I'll break down this later okay sprint planning they can ask you about sprint review you can ask what is the purpose. So about all of these things they can ask what is the purpose of all these okay why what is the advantage of sprint review what so you can say that sprint review the advantage of sprint review is continuous feedback right when you do a demo and 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, whatever the team have built is as per the customer's expectation, whether it is as per the acceptance criteria of that story or not. Right? So this gives c this this gets a c 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 the 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 the 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 stakeholder is something who can be directly 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 C 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, uh they will expect you to do this. Okay? They are expecting you to uh 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 filled. 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 will 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 a extra action item on that right similarly sprint retrospective is an inspect 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 code 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 um idea board. I don't know if it is still exit 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 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 uh create my own idea board. Right. So you will create like um you can say that uh sprint uh you know sprint to you know team aster right something like that. Okay. and description would be just 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 in action items only okay I think we have to login. Why didn't it create it? Okay. Okay. Sections want to well I think if it is not coming then we have to create an account here. What go and This is the action. 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 and action item same thing. Clear? Got it? And then action these are sticky notes. Okay. And the wonderful part of this is that you can even export it as a PD. Okay. So these are different tools. Okay. So if you you can go to the uh any company they will use I'm not saying this is the only thing you will get many different tools miro is there okay fine okay next question is that uh okay what do you do in scrum yeah so does man testing okay 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 means how is it what is your role in sprint 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 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 try to uh I try 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 then they will ask they can ask further questions right. So what is story point? Okay. So you can say that uh our snap 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 uh why I have given this estimate then I will give my uh thoughts on that right why I have estimated high or low and based on that the entire team will again give their uh you know discussion right my team will give inputs whether I'm giving high or low and based on that we will collaborate the entire team will collaborate again suppose I'm saying this user story is very high for me the team will help me right in telling that it should not be suppose I'm fresher now for example who is that some let me tell somebody's name okay now for example Kazim is telling that some user story is 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 have the kazim 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 the 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 forget 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 all which are only only taking interviews like I'm interviewed.com risebird right code javo and all so I'm a panel there I do take lot of interviews of uh automation developers java fullstack python fullstack 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 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 we model waterfall model okay that time their world was little simple world started changing after 2013 and 14 only okay now it is all together a different thing now there is docker kubernetes AWS uh Azure AI I what else right co-pilot everything is there so now that time little it was slow okay so that time the projects were still working on waterfall model v model word was little simple okay so people were 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 you'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 we 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 band 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 are going never say that one story point is one day two story point is today 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 Asharia who a senior senior lady in the same team for the same for the same user story Asharia can take two story point try to understand this how why because ashwaria the senior senior senior person okay and this kazim is a treasure 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 he'll do everything for the first time and unknowns unknowns means he a lot of things risk means first time he's doing right that will 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 Auroria 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 shallini. 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 salin is effort estimation not the user stories. Okay. So 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 interviews because this clearly shows their lack of experience in understanding agile concepts. Okay. So these are very basics uh but very very fundamental and uh 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 uh when you do the sprint planning this thing can happen. Kajim can say it is five, Asharia can say it is two. And when this sprint planning is happening then Ashwara 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 um you will go and uh first you will decide what is the 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 you will be uh they can ask you okay on what basis uh you are uh taking as one story point initially when you're joining the team right that time nobody is uh 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 uh some of my uh or you can I will be directly approaching to the 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 for story want this thing two story point that's how I will learn okay this all this question can also be okay fine 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 uh how do how the sprint planning happens in your team what uh tools that do you use okay you can say planning poker the sprint transform master is okay is using okay and all these things so planning poker uh is one kind of uh the thing But it is a kind of uh kind of a link. Okay, it's a kind of a tool which the scrum master uses. He will send the one link. It will get generated and he will 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 unonymously whatever each person will be getting uh that number it will be reflected on the screen. Okay. Every person's name and their reflected user story. Okay. Dip Kumar what elaborate on story point? Sure I will elaborate. So story point is the combination 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 the combination of complexity of the of the user story how complex is a user story right suppose if your if your story is based on artificial intelligence okay then it is very complex right That's very complex. Correct? So that means something very difficult you are 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 are going to do or anything. I'm not just giving it a reference. Okay? Then it will be you'll put more story point, right? Unknowns, lot of uh suppose something you are going to do for the first time. So there will be lot of uncertaintities in the work, right? So lot of unknowns. So you are going to put more lot of unknowns in that thing. Okay, that is unknowns. So that is story point. Fine. From interview point of view, from work point of view also this is important. Okay. So I think I explained everything and uh retrospective and and review I think you already got it right. So these are the things and uh 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 Kazim. Does manual testing any advantages over automation? Yes it have got lot of advantages over automation. Right. Right. Yes it have got lot of advantages. Okay. manual testing over automation lot of advantages right so 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 uh this what is this uh suppose I'm testing this uh myntra right if I'm testing myntra in okay by what is testing of myra 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. I choose some dress. Add to bag. I go added to back. I go to back. Okay. And then I placed order. Okay. I Okay. I'm not able to login 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 all of you have placed some order yes or no on the e-commerce site 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 uh selenium what if I do the same thing using selenium script how wonderful it will be what if if I place the same thing with selenium script it will be good or not great that's what you guys are going to be in another 1 and a half to 2 months right yes so what what will suppose um I'm 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 by the time I finish my class at 10:00 right and u my clothes would be already washed in washing machine I just have to dry it down right so that is automation okay now there is artificial 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 uh you might have seen that many junior developer jobs are going 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 die right with your own hands AI is doing the work okay so that is automation okay where you're 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 errorprone. 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 errorprone if you're not feeling well. Now you might have heard of many aeroplane crashes where the pilot was tired. Okay. And you might have seen many reals on Instagram where the driver was sleepy and he took the car and got crashed. Okay. So manual test manual testing is errorprone. If you are not feeling well suppose today I'm not feeling well. Okay. I have taken many medicines. Okay. And uh I'm not in that condition to run the class for 4 hours. So I am taking class only for 2 and a half hours. But suppose if now uh uh automated video was there, right? Video if you play it can run all night also. Correct? So manual is errorprone. Automation is not. Okay. Next is what manual is there are some advantages also. Okay. manual uh does not takes time for training. Okay. So there does not takes time for training. There is no training required for such manual things. Right? You don't need to train time for this. Just need to know the domain knowledge. Okay. On the other hand, contrary for your uh 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 are all investing money okay and time right so here manual doesn't need any setup no tools required okay but automation needs time it's set up 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 kind of applications can be automated you can automate this customer interview question which case I was just asked 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 are automating definitely you need to manually test that right definitely there are some ITQB foundation last chapter this is the this is the last chapter definition whatever I have put if some of you are ITQB certified this is what 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 uh we will uh move ahead. Okay. And uh we'll move ahead with our uh with our next agenda or whatever is there. I hope till now whatever I taught is clear to all of you. Okay. Next uh today we are going to see uh this is our uh today we will try to see how analyze we will see how agile helps in software testing okay how testing life cycle uh happens in agile projects and how agile fits in the testing ecosystem okay so study 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 place is uh everything is good. Okay. And uh and I I I already told you right what is the uh beauty of automation. Okay. Automation comes into picture where you have to do regression testing. Okay regression regression this I 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 a big entrepreneur of China. Okay. So yeah, he is a big man in China. So he he have said one thing that uh it is not who brings what to the market but it is the one who brings fastest fastest things to the market. Right now Tatas have come to the market. How many of you have seen Tatas? Okay. Do you like it? It's a huge vehicle right? I saw it two I saw it day before yesterday. It's a huge vehicle. Yes, it looks like defender. Yes, but uh 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 amazing vehicle, right? So Tata have given up something very good the market now I think everybody they now I was asking that person in the showroom uh 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 uh 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 testing 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 bringing something into the market which nobody Ali 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 into 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 things fastest in agile things are developing in 2 weeks right 2 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 they are they validating the requirements. Test cases validate the requirements. That's it. Okay. So suppose now suppose if I have to if I have to release something to the market in two weeks and I have to do the regression testing for thousand 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 thousand test cases in two weeks. How can I do the testing of thousand test cases in two in in 10 days? Is it possible to test thousand test cases in two weeks by two two testers? Can I do testing of thousand test cases in two weeks by two people? Is it possible? No. Then how can then how can I do that? Only if we have automated those thousand test cases, right? So that is no. Not by AI 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. And 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 treated with not only with simply I learn I teach for edurea. I teach for Q spiders. I teach for star agile. I teach for multiple platforms. Okay. I I also teach directly with the corporated companies also. So I see lot of people are coming for learning automation and I have seen learners coming from backgrounds like uh 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 uh you know backgrounds like HR, some of them they are from fitness background. So you can imagine right people are coming from XY Z backgrounds which they they're no way related to IT backgrounds right all of them they just want to learn 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 rapid into the market. Okay? And there is a brutal competition in between the products, right? And if you don't bring changes fast onto the market, then you will not survive in today's world. You take any any any kind of product, right? You can see that 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 case is uh in 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 uh the testers write a 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. I think I have with me. Okay. So this is a test case if you can see this. So this is how a test case looks like. Okay. So this is a test case. Okay. This is a test case. This is test case means you are validating some requirement. So here I'm validating the login feature. Can you see verify login with valid username and password? So this I'm validating. Okay. Fine. And what are the steps to validate this? I'll show 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 login? Like this your log browser. Okay? And then you will open the URL some URL. Right? You will enter the username and password and then you will 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 this is the steps to validate this scenario and these are the test data meaning the username and password and this is expected result. So once if you enter the login button user should be successfully this one and 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 uh the every time you get uh 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 functionalities 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 reflection testing. Okay. So what can happen 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 and 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. Clear. 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 products project projects especially software by working in small chunks getting frequent feedback and adapting fast when things change. Okay. And uh core ideas we have already talked about of agile. We we we focus on people who are agile processes. We focus on working software and all right. and the popular agile uh frameworks we have talked about right. So what is uh 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 work in small cycles and we deliver something usable we get the feedback in and we improve the work in the next cycle right so this is all about the agile methodology okay we are talking about this now I'm just trying to open the PDF for them. Just give me a sec guys. Okay. So this is the gel methodology. Okay. So gel methodology is basically it's a project management methodology. Okay. And to it assist the software development teams in effectively dealing with dynamics and uncertaintities, right? So why it says uncertaintities? Because uh there can be sometimes you know as I told you that the customer can come back right and it he can ask you that uh we want uh 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 the uncertaintities. 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 uh there those reasons as described are that I first I 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 lot of bugs right suppose now if you are developing other entire things entire features at a time it can happen that you may end up lot 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 are getting lot of feedback from the customer right then you are getting lot of feedback from the customers and from the product owner also Right? Because there is a event 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 uh it creates also actually total alignment and transparency. Transparency is always there right there is nothing like you are doing everything hidden. So the taken waterfall and B model right they say that okay 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 we are committing actually that we are committing on these user stories. We are uh we are actually building this feature work right and we will do this we are we are 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 the 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 write Okay, this is a small write up only. Okay, so this is the small write 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 uh 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 uh some process right for example now if I have to explain you there is suppose 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 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 later 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 you are going to accumulate some technical depth. Okay, that means that's the suppose guide. 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 reduces reduce it? Because here development is happening in small manageable increments. So problems are detected building. Right? Continuous testing is happening. Okay. Right. Every sprint includes some uh scrum events like review and improvement. Okay. So let me give you elaborate this up one minute. Let's go through this. Please make my mouse. Okay. Please read this. Maybe this will help you to understand for those who are beginners. So this is about technical dep. Okay. Okay. Some question asked if the project spill over how will work in short cycles will work? Anything if it is getting spilled over they need to do it later and they need to address it while it got spilled over. No, it will not move to backlog. Okay. Uh among other 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 transparent. Transparency. So it is about you have seen that board right? Jira board. How scrum brings transparency right you can say using Jira board. So this is another thing please both okay agile create total alignment and transparency. Okay. So this is using daily standup using sprint planning. Okay. So this is guys all about the first part. So this is the 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 it it brings high quality products and uh it but it it it also predict the delivery dates. These are some other things also. Okay. So, general software development and testing minimize risks. Okay. What does it mean is that the work is delivered in small increments. Okay. Uh actually defects uh detect defects before they go into major failures. And uh since we do regular customer feedback, right? uh we do we prevent building the wrong product right and problems are fixed sprint by sprint not at the end okay so this is the agile software development and that is how to 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 So agile software development and testing minimize risk. So what we 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 you're going to get you are going to you are going to get frequent feedback, right? From the customer retrospective, right? Automated testing goes hand in hand. Refactoring improves code maintaining. What is refactoring? Refactoring means the code refactoring, right? Whatever the code is getting refactored by the developers. Okay? Even the red factoring 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 Mac test. Okay, next point is agile enables predict delivery dates. Okay, what is predicting delivery dates? Suppose if a team completes 20 story point sprint consistently delivery timelines can be predicted uh deniably. 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 a 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 unable 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. Right. Okay. Please go through this. Okay. So, agile quality assurance. Okay. So, main aspect for agile quality assurance to remember are that the Q teams is cross functional. Okay. So, what is cross functional? What do you mean by crossunctional? As I already told you, right? So, what is the meaning of cross functional? Crossunctional 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 except aspects of agile QA are that the QA team is crossunctional and self-organized. So in each sprint 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 crossunctional 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 agile testing principles means 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 uh also be a 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 uh quality issues. Okay. Development and business analyst also participate in testing and promoting shared responsibilities for quality. Okay. So how developers and uh developers will participate in testing? So developers will do unit testing. I think I have not told you right. So 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 of feature which they are 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 build 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 let me give the write up and these examples are there and that will help you to understand it one by one. First put the write up and then I will so one example. Okay. So this is the first one. This is the second one. Developers and business analyst also participate in testing. How developers participate in testing? They perform unit testing. Okay, as I told you, this is the 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 analyst validate the requirements through acceptance test. So business analyst are those people right BAS they write some acceptance test and that's how they do the uh validation okay next QA team resource 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 spread okay the bugs found during the sprint testings are fixed before the next spread 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 like 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 where like in waterfall and all you used to write test cases from the uh long long documents. Okay. Fine. Is this clear? Testing. Next testing is performed throughout the implementation process. Not just a 10. Right. So what does this mean? Every sprint the testing will be performed. The sprint testing is performed. The sprint testing is performed not like it will be performed at the end. Right? Not like here the development went testing will be done here not like this testing happens parally all through the development understood. So trigression and integration test done 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 two to three minutes to go through this. Okay. And if there is any confusion please do 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 uh 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 three more weekends because 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 access JavaScript, Angular, Cyprus. Okay. So guys, this is all we need to learn. So last weekend 8 hours we have given to a child. Okay. And uh here you can see that see that uh 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 um I got one comment where I saw that u uh one of the learners have mentioned that uh uh canban 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 canban here. Okay. So if I am not 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 we'll get extra that is not a issue so I have already discussed with them okay and um so this is the thing okay so canen is not here but I have discussed that canen is a type of type of 1 SDLC model. Okay. So this is first thing guys if uh I will be going as per the scope of the content. Okay. So so this is first thing. So one guideline is that. So let me know if you have still any confusions. Okay. So content wise teaching. Okay. So this I'm doing right from the first class only. And uh 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 okay examples I will be taking lot of examples because I think that is what most of the learners are beginner right and third thing will be right after every topic. Okay 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 runbook to uh TG. 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 a vague description I found. So I was trying to interact with Muma also. So uh please let me know what is the term quality means. So 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 uh 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 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 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 uh as as per the content I'm going. Okay. So here I'm going to talk about uh 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 ready for a user story. Okay. Definition of ready. So it is in regards to a user story. So Jira access if you get guys you will get some 30 days free access for that user ID. uh 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 uh 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 uh 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 uh text tech like JavaScript. Okay, some uh some framework like Angular or React. Okay, so I'm just talking about high level back end is on the other end 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 uh 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 which will make sense if you go and work in any company. Okay, then for login screen to be developed the dependency is that login API should have been ready by the backend 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 tickets should have been done. Make 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 ready, the developers can start the work without confusion or delays. Okay? And it is agile concept. Okay? It's like a prerequisite. Suppose now you are going to cook the cook your food, right? So what is 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 uh front end ticket and in between the sprint if you realize that uh this is not ready then then it will be a ticket which cannot be finished in that sprint. Right? So it makes the 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 backend API means understand backend 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 the front end Okay. So this is a front end what you see. But is that all? No. Right. So um but behind also there is something called as back end. Okay. For every application there is a back end. Now for Swiggy, Zumato, 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 have just given you one realtime 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 end 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 criterias, 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 am 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 will 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. 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 the API. Okay, API is not the point of discussion. Now I just took a a topic and I think many people got confused. Okay, so leave that. Okay, if many people understood it, fine. They understand 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 these are also important from interview point of view. Okay. So definition of done is something similar to definition of ready. Okay. And uh it is uh the ready was uh for uh making sure that you can start a ticket. Okay. And definition often 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 your work is done? Right? 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. So you might say that okay I have done two pages of Hindi, two pages of uh mathematics, three pages of this. So I have finished my so that might be some rule which your teacher and you might have done. Correct. So this definition of done is also created by the team. Okay. Who defines this definition of done? No scrum master doesn't define 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 nothing but checklist items. Okay. Neither the test manager. See test manager, product manager to nobody have done. See agile what is the concept? The team works together. Team works as an agile unit. Team is the whole and soul 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 the 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 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 form. Simple. If I take an interview and if someone says that uh 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 the old legacy old mindset okay or he might be working in a team which is just doing agile not being agile right I have seen organizations which where the team just come and open Jira and they do standups okay somehow so that they're working with uh agile and Jira right they are not actually following anything. Okay. So that is different. But if you want to uh you know Yes, sisha that is that is correct. So so it happens. Okay. That is the reality. Nobody some of the organizations they very very strict and they follow it also very well. Okay. They have their own uh uh tu uh 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 def it depends. we cannot do anything. Okay. So team comes together and they define how they are going to mark the story as a completed. Okay. So this is the 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 right now in agile how we deliver? We deliver in a sprint. Suppose in one sprint I'm delivering 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 are entering username and password you're able to successfully go to the homepage okay you're creating this functionality now how will you mark the story as done right definitely you will say that ma'am acceptance criteria of the ticket should be done right yeah that is story related thing but for definition of done is not for story. Let's 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 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 and 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? Here 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. Then when 3 hours got completed, you gave your question paper to the to that uh uh submitted the paper to whoever was there in that uh exam room. Teacher took that paper and you came out of successfully out of that exam out. 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 okay just writing the answer blah blah blah right and throwing it there on the table and running out of the exam hole and jumping the all 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 uh 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 do works so I'm giving you another example of DOD for your tickets okay so this simple definition of dot done okay for you for your uh user story user story what it will It will be all these things. Okay, you see this a task will be considered done when code is completed code review. Please 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 uh I'm going to give you the definition of definition of done. Okay. Anything which you not understand. So if you ask and 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 or this project for definition done is for the all the user stories is 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 time. Okay demo is a part of sprint uh ceremony ji. So we are not going to put here a as a definition of t right demo is a part of sprint review all the scrum reviews scrum ceremonies we are not going to put in definition of t okay this is something internal to the team okay 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 uh 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 uh most of the companies follow guys this format. So, I'm 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 uh 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 uh maintaining Jira Hising, 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 student planning right and then um being a tester you can put comment every day here worked on this on creating right manual script right for this feature okay added 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 See you can see in history who have done what seeat updated the story point updated start date due date right everything will come here okay so this is all what required from you being a standalone tester or developer 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 get comments onto it and you should also know how to move it to a correct status. Right? Let me show that. So this is a 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, then it will be blocked. In a 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 fine. So it is done. Once it is moved to done means done. See it is moved to done. Then it have come here. Can you see? And it have been strikeed out by the Jira. Fine. So this is very important for you. Okay. And uh this is what you have to do. That's it. Nothing more expectations. Second thing which you have to see is board backlog. This is the backlog. Click on it. If you click on it, you will get. So here 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 a duty duty of product owner to maintain this backlog. Okay. So here there is a create button. Can you see? Let us create user story. Okay. So I'm creating a user story. Story Okay. So I'm creating a sample user story. Okay. So uh so let us create uh I have already created for login. Right. Some other functionality. Just let me think about okay let we can do it for uh 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 a 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 a job. I'm just showing you so that uh 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 is developing and the tester when he is creating test cases and testing. Is that clear? I have already defined. So some acceptance criteria like uh user can enter email and password. Okay. Second, email must be unique. Okay. Then password suppose you're telling must be name each 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 negative criteria. Fine. So guys there can be lot of things. Okay. I'm just adding few things. 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 regist user registration and sign up it it came here. Fine. And uh what you can do is that you can see okay like this you can create user stories when you create your own sample uh Jira please you can create it. Okay. This is the format. Okay. any examples uh sorry any other uh questions if you have please shoot out to me and then I will move on to get what do you see guys you just have to create click on create choose work type story okay 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 the heading and the 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 uh task is something which is not a functionality. Okay. Task is something like you have worked on the creation of test environment or you are working on creation of test data. Okay. So these are nonfun feature related work, right? nonfunctionality 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 topic 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 linked 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 aic in Jira? Same thing you can log an API. Okay, you can create a a same thing here. Create instead of story you create an app. Okay. And you can say that we're going 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. Fine. User story was the very uh was there as per the scope of this content. So I have shown you. Okay. Turnover request. So there is I have not heard about turnover request sonia I have heard uh yeah epic also we need description right you can say account functionality okay yes everything we need description cin okay turnover request I have not heard of sonia so I'm not sure about turnover 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 to uh or some bug fixes there right or 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 tasks. Okay, a request work type basically is for uh help, support or service or 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 uh let me okay let me create one account okay I will not put body let me simply create one okay just to show you how I'm linking so suppose this is um 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 uh project again backlog. Now this ticket is there right scrum 2 open link in new tab so I want to add epic can you see add epic so you can add this user story and do some epic here I 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 epics is there only one epic you can add this to this epics you see right now it have gone to scrum 3 now if you go to this account functionality and refresh this page Can you see that one story have come here user registration can you see? So this is how appex will hold all the user stories in real time. Okay. So now let me open simply learn. We will move on to now guys. Okay. Next topic is g. Why I'm opening? Because I need to open the lab, right? Okay. So meanwhile this will be starting. I'm starting with the kit. Okay. So, what is git? Okay. And uh why do we need git? Okay. So I will just come up with some basic things then only I'll talk about git. So git does not have any short form first of all. Okay. And uh why the g have 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 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 the 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 sixth day and you want to bring it back right how it was on sixth day. How will you bring it back? Yeah. Madame I mean using it we can do that but I'm asking about the rest of the other people who don't have any idea about G. So how can you do that? If you do not have anything can you remember on sixth day what you have done by the time you reach 11th day you already have made so many changes in that book. You cannot retrieve uh the Photoshop or you can say you know you take a picture of a child right when he's 5 years old and 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 you have a snapshot of that picture of that kid right in your right 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 write it on a hard uh 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 we worked with overlapping time zones right like uh we start working then uh 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 um similar file next tester starts overwriting 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 uh 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, G 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. Okay, so G is a tool that tracks the changes in file over time. symptom. Okay. In olden days, in olden days, there used to be only 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 do. 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 paper 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 pan rajavan okay you can integrate git and jera but both are separate softwares uh okay so g 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 is in the file okay it will break it okay for this time stamp this was the state of the file and these are changes I have put in the file okay yes we'll be practicing all everything will be hands-on only in g okay okay now no more everything will be hands on nothing will be boring so git is a tool that automatically sales version it lets you know who make the changes okay in simple definition git is a tool that takes the changes and 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 takes care. Okay? So, you can have git installed on your local also. Okay? And it'll 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 told crashed, right? we can go back to the previous version. Okay. Now suppose one developer okay he pushed the recent code of version 4 suppose and because of pushing this code pushing means committing committing means just uh 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 g will do it will move right it will deploy this version so g is helpful there Okay. So it will go back to older versions 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. Please go through this. Take a minute. This is the advantages of creative plans. Primary use of kit in testing process is all of these things. When you'll be writing automation script you need to know in the automation script what would have got changed. You will be working in automation script with multiple developers, right? Multi multiple auto automation testers. Okay, you suppose you're 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 uh script is I think pressing the entire some test cases, right? Then they can go back to older versions, right? Same back up of the code. Okay, all of this same purpose for you also as a test. 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 screen and put in chat if you have got this or not. Okay, I don't mind really anything Ashika or anybody here. 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 um I understand because you guys have taken up this course basically for you to upskill and get somewhere right. So I I I have many learners right and not only you guys I take lot of webinars and there are many people who are really looking out desperately for jobs and all right. So I really do feel for all of you and see it's it 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. Namata cannot connect to until. So if it is not starting you terminate that instance and start running instance. You will get used to it in few days. Okay, you are at the red screen gauge. 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 upon you. Okay. So this is a screen. Okay. So you can see that this is a virtual machine. This is an Ubuntu machine. You can see the date uh somewhere afternoon timing. I don't know where is this being deployed somewhere in um I don't know it's an afternoon time there. Right. So what you have to do this is the uh 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 it's 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, 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 uh John, right? And then you erase it and after that you you put it as uh as something like uh as Shwita, right? Can you remember it first what was written and then second you do not have any kind of proof, right? So you cannot uh you you you are actually not having any kind of tracking tracking kind of thing right but g can do this automatically without be taking any kind of headache okay so now we will be actually working on installation of git uh okay and uh we do not need to install git now if you were working on uh on your own laptops I would have told you that uh 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 uh I am closing my laptop. So what G will do? It will take a camera kind of it will take a snapshot of it version 3. Right? So tomorrow if you're seeing that you this uh there is a code right there is ABC file 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 uh get uh scared about this term like repository log. 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 g will automatically will take a you know g will automatically will take a kind of a version now we are going to actually doing the we will do the account setup first we will we will that is already created actually okay get account is already g 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? 15 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 developer 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 showing you one example. Can you all look at it here? So this is my 1 minute demo g. Yeah. Can you see this? This is my GitHub account. Can you all of Can you see all of this? This is my I think I 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. The JavaScript code, HTML code is there, CSS code is there. Okay. And 4D app whatever blah HTML is the playright code is there. Okay. So these are repo. Repo means repositories. Okay. If I open, let me open one day Python. So Python code is also here. So see, pandas, right? All of this. Can you see? Can you see commit first commit two 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. Oh, this is playright code. Okay, playright code. This code is there on my on my laptop also. Why 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 can share this link with all of you. You can download my port 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 crash 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 have stolen my laptop right I give a because it's I it's on the GitHub account I go anywhere I just log in just now I have logged into the GitHub I have shown you right everything is safe it's free g and GitHub both are free open source we do not need to pay a fee do anything okay you can access it from anywhere and can share a link with others. Okay. Okay. So now who will create a GitHub repository? Create the 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. Uh uh internet is there right? Google Chrome. Open that. So just put your password. Okay. So here you can open GitHub. So it's very old uh 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. If you want beautiful steps I can create. Okay. So, type github.com in your browser. On the top right corner, click sign up. You will loging in through your Google email or you can use a valid email. Put a strong password. Create a username. Username like I have uh like to create it, right? Sha demo get here. This is the username which will show up twice like this. This is the username. This is my username. Shut demo git. Okay. Choose a username like this. Okay. Or you can continue with Google web. Okay. And please uh sign up create an account. I have already created it. Okay. And then some verify account will happen. Some capture will go or something you can create. 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 you. So it will ask you are you are you a 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 gory 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 forget password and you can retrieve okay so these are the exact steps for creating a GitHub accounting github hub account. Okay. First time one time user activity. So guys, I'm moving ahead. Every details I have shared here. Okay. What is the email id? Right. Email address and uh password. Okay. Email address will be like this atgmail.com. Fine. Okay. So, username must be unique. Fine. So, this is something which you will get. Choose a plan which is select. Now create a sample repository. Okay. Now I think uh sign up is there. Right. Go back. I think everybody have logged in. Right. So now log in with your uh Okay. I'm just logging in. Oh, see authentication some bug have that have gone. So I'm entering the verification code 3 2 3 right so see here can you see it have come here okay can enlarge it so for what you can do can create can you see click on this plus icon create a new repository and say that just say that test it repo just create it guys just to see okay first repository creation so this is description I just say for demo purpose only okay find and then uh make it public only and just say create right fine created right the test Create repository is created. Now if you click on those three icons here here click on home right. So you can see uh you can see all your repositories. You can click on show more. You can see test kit repositories 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 will do all that thing later. Now we created a GitHub account. Okay. And there is a difference between Git and GitHub. G is on your local system. Okay. Now uh we will be actually installing the G uh uh locally. Okay. Here the git is already installed on your lab. Okay. So, how to check if it is already installed? Okay. So, please open up the terminal. So, how to check uh how to open up that that terminal here? Go to you can come here. See if you click down. This is coming terminal terminal. Click on this. Right. Type here and enter. Right. So you can see that already the g is installed here and git version is 2.2.25.1. So using the command line line you can see what command you will uh enter gy-en version. Okay this is the code to check if k is already installed. Okay check kit 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. And copy this. I'll put in the copy and I'm putting here. This is the output. Right? If this is not installed then you'll get some not this software is not recognized that on your 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 hover your mouse down you will see this black color terminal evaluator this is the command line okay this is the command line for your machine click on this will open up here you have to type get space - enter so g is already installed right so now we will see some uh practice okay how to see how how the g is making changes we'll do some practical hands-on on things. Okay, I'm writing this for you. Okay, next thing we will do is that if G 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 uh tell the G who you are, right? Now, this is G uh installed already on on your system, right? I cannot see this terminal. Your terminal is here. I'll show you one more time. Uh just a sec. Here it is. terminal. 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 G 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 to 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. Get config -y 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 get config - global okay so you just focus on whatever I'm teaching user 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. So this also you need to add and I'm going to put it here. So this is an example. So this is an example. Fine. 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 am not doing all of this because it's already done okay So yeah though that old 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 kazim 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. G - version it starts always with g not with GitHub. Okay, Richard is it username or my name? We are configuring your name only. Whatever your 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 away. So don't get angry because I have taken one name. So your name so my name is what? Twitter right? Okay. Fine. Okay. Next I'm I am configuring what what I'm configuring my email id right. So what is my email id? Rahul bug2308gmail.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 have 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 g get config global list what it is giving what it is giving it is giving me the users okay so give get config user list means configuration is done successfully okay this is connection is done successfully so if you're getting if you done properly if you're getting this output that means configuration done successfully fine so fine that's fine so by Doing this g knows who you are. Okay. Now let's create a directory. The fun will start now. Okay. And uh this is done. Okay. Now whatever you do on your sandbox will 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 sit peacefully you know this is the format. This is the command. Okay. This is the command understand. Okay. And this is the example. This is the command. This is the comment. 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. I have given you one simple option. Please login through your Gmail which will capture 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 is stuck please send a screenshot of that in the chat okay I'll look into it I'm not getting any popup from you that uh yeah ashika no problem yeah where I can find this file that you are creating uh 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 the first time for all of you g is very important one devops concept Okay, virtual learning today. So guys, this is all about configuration we have done. Now I want to proceed with GitHub commands like how you will create a directory, how you will try to start raking it, right? All realtime concepts will come. Only agile was theory which was a little bit boring and it gone. Now everything will be we'll doing practically over the lab. Okay. And um I'll be showing you and you'll be doing it. Okay, you'll be seeing it at least. Okay. And maybe uh if you finish the concepts early. Next guys, we are now moving into the real time uh things. Okay, we are going to focus on g file management. Okay, g file management. We will see how to how the g is used to track the changes on our file. As I told you, right, it is used to manage the files. Okay, so now so for this what we will do few concepts you have to understand. I will be using the word repository. What is repository? So repository means we already created repository in GitHub. So again I'm explaining it for everybody. So here now just a folder where some code will be present direct. Okay. So repo also some people say repo. Okay. Don't get confused. Okay. So now let's get get started with hands on. Okay. So for this let's create a folder and reconnect. You will see this message then reconnect until it is reconnecting. What I'm going to do now idea is to create a project. Okay. And then I will create a I'll create a folder. Then I will tell the I'll tell that folder that you are under the G control now by initializing it with G. Okay. So for that I will be using one command called as get inate. Let me see if it have got open or not. See this is the problem with sandbox. Everybody will have problems. Okay don't worry even I get problems. So let me till then write. If you face problem like this if it is not connecting it is black screen or something like that then you cannot do anything. You have to close this window. You have to come here. You have to stop the instance. Stop the instance. Yes. Right? See again it is started. So let me now tell you what I'm going to do meanwhile the theory part. Okay. So now basically what I'm going to do I'm I'm going to create a directory. Okay. So either you can create a directory directly. I'll show you how to create a directory directly inside the lab. I was about to show you that or or you can do it using some command. Okay. So what is the command? These are the command. Okay. So what I'm going to do creating a directory and and basically I'm telling it let's start tracking this folder and it files using okay and what I'm doing I'm telling the g okay I'm telling what telling it what some guys I'm trying to tell you very basic things okay as basic as lame as I can get right so how can I do that through couple of commands so what are those commands These are the commands made diir. So this is a command mkdir is a command. Yeah. So I'm explaining that only now sonia. Okay. Make diir. My first project. So this will make a folder. Make directory or folder. Okay. What is a folder name? My first project. CD means it will take you to that directory. Change directory. Okay. If you want to change control of your right what is change directory sometimes you're in C C drive you take the mouse control to D drive right that is change directory the CD now you're going to my must first project to that directory and you're initializing with g init so what does git init do what does g init do after you do get g get init right it is no more a normal project folder right it became completely trackable folder using g okay so this folder is now a git repository. So what happens after you do get in it? So all these things happen I'll show you practically meanwhile. So once you do get in it a hidden folder.get is created and this folder actually stores all these things. I'll show you. Okay. And you should never delete.get or you will lo get history. Okay. Sometimes this is being asked in interviews. Just this is just for information. Okay. So now I'll move. Okay. So you can see that RDP access have come. Now can you see it is still will not started. Wow. This is wonderful thing. Again it is starting. So it will take my time. Can you see it is taking my time. So if it is already open for you. Okay. You also cannot do anything. Wait. You have to wait. We cannot do much. We all have to wait. Finally, it has c