 All right, so what mistakes in her understanding Vishal she had? Okay, so it's I think for the development phase is like, you know, you there's a everyday meeting, you know, and answering like, you know, question and answers. It's not like if it's required, they have the has to do a meeting, I think it's everyday meeting where they, like, you know, if anything changes, you know, he answers back and forth with the stakeholders and developers. And then the uat is there's no requirements and stuff like that because the uat is the last testing before you deploy in the product. So it's the meat, it's the the uat testing is with stakeholders and representatives. I think that's that's what she that's where that's what she missed. For rest, she was okay. Okay, so you got that Amado. I got it. Thank you. The uat is just with the stakeholders not at that point they don't have any requirements anymore. Yeah, the b it rolls. Yeah, the b it rolls doesn't end. So the product is deployed, like, you know, it's just, yeah. So the uat test user except in testing is like, you know, it's the last thing and if there's something, if there's like, you know, the BA asked the stakeholders and stuff like that who's rep like, you know, who's going to be the main main person or main, you know, who will be the doing uat testing. You know, there could be stakeholders or representatives. But if there's anything needs to be changed, the BA has to go back and forth with the developers. Yeah, you know, if it's if it's changeable. Okay. Yeah. Thank you. You're welcome. Okay. So then user acceptance testing. So who leads the user acceptance testing and how they do that. That is a question to you. The user, from what I just said, the user as acceptance testing is still needed by by the BA, but it should be done by the stakeholders. The BA is also the leading the meeting. So, BA is leading to how we do that like that is basically the question. Okay. How do we do the user acceptance testing? Let's say they are done with the user acceptance testing is definitely to let them. The final part of the project. So the BA will send a meeting invite to the stakeholders and the testers that needs to be there. They will send out a meeting invite. The BA will call all of them to a meeting. Do an introduction in the, how do we say to the invites like the body and stop the reason for the meeting is user acceptance testing. And then the BA will go ahead and present the whole thing like, hey, this is the end of our project is our testing and all the rest. Now pass it over to the stakeholders or the person's responsible to do the user acceptance testing. Okay. So pass it to the stakeholders. So like how? I don't know how to explain it. I don't know if I'm saying. Okay, so I'm going to, I'm going to try to go over again. Let me tell you. So when, when the whole product was ready, right before deployment, there's a final testing that is called a user accepting testing. So who does the you, who does the you like, you know, the UAT. It's the stakeholders representatives of stakeholders. It's called UAT testers be a works with the stakeholders and ask them to identify the user accepting testers, the UAT testers, and he gets the list from them, and then he invites them to give them an overview of the test cases. And the be a be a leads, like, you know, be a is be a leads the UAT. But there's a there's another thing I just remembered that QA lead is a helper to a be a to provide him needed access to the test environment. And that's how the user accepting testing is done. That's the process of it. I don't know if I'm explaining right or wrong, but Right. Yeah. So now it, like what you understood. For he said the be a leads the user accepting testing, but before that they need to get through the stakeholders to identify. How do we say the people that would do the you the UAE testing right user acceptance testing. The user acceptance can seem like they need to get the leads of those people from the stakeholders. And then when you get the list from the stakeholders, you're going to send out the invites to them for the user acceptance testing session. So there's no invite. Or I mean, you can have a meeting and how are you going to basically. Yeah, exactly. Okay. Okay. Yeah. Yep. So sending an invite and then then what Get with them. So a meeting. So because we already have the leads from the stakeholders, the list of the people that would actually do the user acceptance testing. You got them. So you got it from the stakeholders and you go into the meeting. Now a day as a day of the meeting. Right. Okay. Yep. So that that was good. So again, let me quickly explain the user acceptance testing again. Yeah. So that you guys would. So what is user acceptance testing. So user acceptance testing is the last activity of of the project. Okay. That is, you know, one thing. And then user acceptance testing be like why we do the user acceptance testing. So now you are the stakeholder. Okay. Now imagine that you are the stakeholder. You spent, you know, million dollar on something. Okay. That some project you invested a million dollar. Okay. And that project is ready. And you have that product basically for your users. So. Will that be will not, will that not be wise that first at least test yourself so you don't get embarrassed in front of users. Because if you, you know, applied that product for the user and user started getting like a lot of problems, then not only you're going to be embarrassed on that, but you might be, you know, losing your users. Right. So instead of, you know, making a profit off of it, or, you know, instead of developing, you're going to get like ruined on that. Right. There would be a negative impact. Okay. Everyone will be kind of pretty hard, but there would be a negative impact. So that's why, you know, before deploying, deploying anything for the users, the business stakeholders who have invested, they have to do the user acceptance testing. So they have to test with the user perspective, all the functionality that will be related to user. Okay. So they, they have to test that before the go ahead for deployment will be like, you know, granted. Okay. So make sense. Any question? Why? There is like the UAT. So that is the answer for that. Okay. Because this is like the investor, the stakeholders who had invested in the product, they have to give a go ahead before the deployment for the user will happen. Okay. So that's why it's like user testing is done. So now, so then who will be user acceptance tester? The logical answer, if you understand what the user acceptance testing is, would be like either they would be stakeholder or representative of the stakeholders who have the right to decide who will test that product. Certainly stakeholders who have invested the money, right? Yeah. So either they will. So now, from the team, which I mean like a BA developer QA, all those like IT team, who is the person who have a closest relationship or longest relationship with the stakeholders? The BA. Exactly. So it would be more logical for the BA and BA is also vice of users, right? Yes. Okay. And BA when doing the testing with the testing team, also partnering with them and testing them all the test cases, which are user perspective test cases. Okay. So that user perspective test cases, BA does with the testing team, that is basically BA is a pre-run for the UAT. So basically that's when BA is learning the UAT. What are the test cases and what are the outcomes? And basically testing himself, okay, with the testers. Testers have definitely tested on their end, but BA is just learning that, like the testing that, you know, getting basically same the credential username and all those test scripts related to the user with the user perspective and then executing those. And those are simply like, you know, those test cases of UAT is not something complicated, you know, like a thing. Okay. So they would be like a pretty much, you know, very simple and easy to understand. Okay. So, for example, like, you know, this is how would be the UAT test scripts. Okay. So this is the actual test scripts for user acceptance testing, that real-time document. Okay. So that is a basically template. In that template, these things already would be explained like introduction, task, what that means, UAT is intended to test the functionality include, you know, data, this is whatever would be there, you know, and browser, which browser you can use it because you are testing for the user. So basically internet browser that you will be using if it is like Internet based and if it is like mobile based, then that then test account means like, you know, these would be like user ID, common user ID will be like this password will be, you know, this is with the password, this, this, this, and then, you know, the first time you use the dashboard login, we will ask to answer some security question means when you are first time login in security answer to first, first phone number answer one that is basically answer, you know, you have to write answer one, best friend answer to your favorite color, answer three and favorite sport team answer three, you know something like that. So to write answering the security question at each login click on yes radio button means like save it. So this is how it is being like the instructions are being given to the users. Okay. Like you are teaching each other how to use the Internet. Okay. Then test data. So if there is some data that you are, you know, putting to do your testing, then, you know, test would be the file of test data, you know, may, for example, like, you know, this is for a healthcare company. So, you know, so they would have a member ID, tax ID, or some member, you know, pain or something, some information, which will be there in their basically like you know, that data. Okay. Then these are the test scripts. Okay. Task one provided dashboard login. Okay. So login to ABC car dashboard. Click sign in using ABC car ID, which is definitely you will use this car ID and then enter the username, you know, respond to the security question. This is would be then under a recognized computer select yes to buy. I'm sorry. I'm sorry guys. My connection dropped. No worries. So bypass the security, you know, do this. So user data username password, which you already have, you know, you enter it. And what would be possible criteria? So it's an existing functionality means it's not a new functionality. It is existing. So, you know, expect a result successfully login to ABC car cloud dashboard application homepage opens in a new browser or start start here button gets displayed corporate information gets like. So this is the expected result. And then what next car corporate search. So intermember pin value to the test data sheet in the step one and click, you know, search button. Select text ID, number corresponding the members pin value enter from the drop down list on September to field. Then, you know, expect a result. Repeat for each of this as such, you know, they because there were multiple like, you know, cloud facet cosmos and nice. So for each members, you just have to repeat. Like, you know, you're testing multiple number. You just have to repeat that. Okay. And exactly what is what is that? What are we doing right now? I know I probably miss something in the beginning. This these are the test scripts basically for user acceptance testing. I'm giving you example how the, you know, user acceptance testing tasks look like. Okay. Okay. So I'll share this, you know, document with you guys too. Okay. So yeah. So that that is so simple. But you get these, you know, test scripts from the, you know, like the key way. Okay. So when the key way is doing their testing, they would have the user test cases too. You just have to ask the key way. Hey, can you give me that list of user test cases that you have prepared? And then you just have to prepare your and there might be a UAT template to just like this. But a UAT template in that template, these information was already there. I just like basically, you know, added and deleted. Okay. And this information, this UAT test account. I got these accounts from basically QA lead. He made that account. Okay. Test account and then test data got it from the key way because the testing would be done in like like a UAT server or test Q testing server. So they have to create those user in there because those user, if they would be in there, then you can do that. If the user is not there, then you won't be able to kind of test them. Okay. You won't get access. And similarly, like, you know, test data, they would have these test data user and all their information in the system. Okay. So basically, like, you know, in the real, like server, like in real, like best buy dot com, there would be, you know, the real users. Okay. But in test server or other, they create replica of those real users. Okay. So that's why you need this test data, that information that if you need to, you know, put, if you are searching some member, so you need to put that information member ID or something, and that data is basically the test data. So basically, you are getting test account created by QA test data from QA and these scripts from the QA. And if the QA don't have that, you know, script, then you create that yourself. Okay. Because these are just the basically translated of a translation of the requirement. Like, you know, in the requirement as a user, I will like, you know, test this, you will like, okay, you will go to this page, log in this, this, this, this. So you can create these basically like, so in this, basically, this is existing functionality. This is existing functionality. This is existing functionality. This is existing functionality. Only this little change was in this project that was happened. Okay. Test more information link on the claim detail page. So this is a user story. Okay. So even the requirement ID is like written over. So this was, you know, what happened. Okay. So there might be like, you know, few changes in there and the rest will be existing functionality. Okay. So this is what, you know, UAT test scripts look like. And you, as you have the UAT user, like I'm giving you an overview that, you know, hey, in this, these are the test, you know, you're like login ID. All right. This is the data that you will put. And, you know, task one is this. You will like go to this URL. You will log in and then click sign in, enter username password, click sign in, username password, respond to if there is a security question, ask these, put these answer in and then save it so that next time you will be doing, going, it will not, you know, bypass the security question. If you won't save or won't select yes, then every time it will ask those security questions. Okay. So then when you will be in there on the dashboard, there will be a list of application. Okay. Select application claim management or claim claims management. Okay. App claim management or claim management simple. Select this and click start here button on the welcome page. Okay. So what you will see, so these like steps will let you log in and application homepage open in a new browser, started button get displayed and when you will like click on that corporate information get displayed. Okay. So this is our expected result and this is existing functionality. So we didn't, which means like we didn't build this. So, and why we have pass fail and this in functionality we mentioned because our scope is only like, you know, this that we are touching. If there would be anything happens over here, that is not our project scope. Okay. So that would be like some other team will be doing. We just have to notify that, you know, hey, login is not working. So we will not be able to, you know, proceed with until that will be working, which is mostly like pretty quick existing functionality. So already support team has that. Okay. So we have to only like the scope of this is new functionality that is being built. Okay. Like from claims summary page should display that is a new functionality. Okay. And in the claims summary page, what would be that, you know, such function will expect a result will be this. So it's so simple. Any question? No. All right. So then UAT is the last step. So again, expectation from you guys like, say, you know, tomorrow expectation is that you will have like, you know, two to three projects and explain end to end your role as a BA. Okay. So that is basically like, you know, expectation that as a BA. Okay. You will have for each project, your kind of, you know, role like that. For example, as a BM, I mean, this is a role. First, you will explain, you know, the project I worked was about, you know, this, this, this. Okay. And then as a role, as a BA, my main role was to gather document requirement. This is this, this is this and whole story end to end. Okay. So this will be like project one. So project one, you can basically get any, maybe like, you know, best buy. Okay. And the project to maybe Wells Fargo. Okay. Maybe you can and anything you can choose. Okay. Wells Fargo, investment, small businesses, like, you know, some project of it. I, you know, work with the small businesses and, you know, loan and liens. They were introducing, you know, business liens for credit, new functionality. And I work, you know, with that team. And so as a BA what I did then from, from there. So select any project from, you know, any industry. And then you expectation is like, you prepare that end to end role. In your words, just like that, you know. Okay. Make sense. Yeah. All right. So yeah. So that would be it. And I want you guys to basically like, you know, do it at least four projects. I'm, you know, asking that, you know, prepare end to end BA and it would be in your own basically like, you know, like first person account. Okay. Means like you will speak it as like right is that your own, like as a BA, my main role was to gather and document the requirement. So I started the project understanding and stakeholder analysis to understand the project I did. I looked at the project charter understood a high level requirement. I talked with the subject matter expert and created a business area context diagram at the same time. When I was doing the stakeholder analysis, I got the list of the stakeholder from the project charter and spoke with them for spoke with the project manager and ask that if he has some list after making a list of the stakeholder, I schedule a meeting with them, identify who is primary, who is secondary. After that I scheduled a business requirement gathering session with them after organizing multiple sessions. I created the business requirement document and I get it signed up from the primary stakeholder. After getting the BRD, I given a walkthrough to the solution team. I've given the walkthrough of the document to the solution team. So here, see somebody who made the would gave. Now that is basically, you know what I'm saying, that is wrong. Okay. So because then it's not like a first person. Okay. So a first person account that I have given a walkthrough to the solution team and I would all that would should will is will not be. It would be a past tense account, first person account. Okay. So that's what you, you will like it. And then working with the, how you work with the, you know, developers, how would you work with the tester and how you would, you know, UAT all that, that's what you will like basically do. And you will do at least for four, four project. So, and that is kind of, you know, must have for tomorrow. Okay. And one more thing. Do you do that meeting like an hour later or that's going to be an issue. I mean, if you guys are okay, I'm okay with that. So it's up to you. Amado, are you okay with that? Or it's going to an hour later does five p.m. Yes. Central. Yeah. Five central. Yeah. Then it'll be six Eastern on mine. Oh yeah. That's okay. Okay. All right. Thank you. You're welcome. Okay. So do you, I mean, I don't want to send you this because I want you to create your own. Okay. So if you are, you know, looking that I will send you this. I'm not sending you this. Okay. Okay. So, and success criteria, if you would be able to create that for, for, for four projects, then I can basically guarantee you that, you know, in next, you know, six to eight weeks, you will have job. How that. Yeah. Because I really need this job. Right. Right. So because this is how much important it is to, you know, do this, you know, exercise. Okay. Yeah. And that's why you have to, you know, get that I'll send you this, like a session for today. So, you know, let's go from there. Okay. All right. Sometimes I just feel like even the job are no more out there. I just be like, Oh my God, am I going to be able to make it through a job? So I think that I can guarantee that you would be make it through the first thing is to getting inside the door. That is the, you know, so just keep eye on getting, you know, the job first and do not worry about I can guarantee you that you will basically, you know, excellent doing the job. Yeah. It's always another person. You will not have a problem in doing the job. You will do that. And I'll support you whenever you need it. And I'm pretty sure that, you know, after two, three weeks on the job, you will be totally fine. You will not, you know, initially definitely the, you will be scared and all that, that, but, you know, as two, three weeks will pass and, you know, I can, you know, get every day some time to you after your work that, you know, what you can expect and but give you the plan at that time. So you don't need to worry about that. You know, this point of time, this point of time, just focus to, you know, be prepared to get into the door, interview preparation. They, they can ask anyone question. They can ask you and what the answer would be and, you know, worry about that and prepare those. And that's why this exercise that you're doing, it's like kind of a basically interview preparation. Okay. Yes. Okay. So that's why I'm focusing forcing you two guys to do in your first hand account past tense. Okay. Yeah. Or you will get used to when you are describing the project that I did this, I did that, and this is how it happened. So you will get used to that. Okay. Because that's how when you have done something, that's how you explain, right? Yes. But when you have learned something, then you don't explain like that, right? Yep. So we are basically bridging that gap. Okay. So you are explaining. So these projects that you are explaining, that's how you are basically like, you know, you're deep diving, deep diving, which we already did. And, you know, basically did start to end. And that's why you know how you perform that role. Yeah. Okay. Thank you. All right. Okay. Bye. Bye.