 Good evening everybody. You guys can hear me, right? Yes, she's on. All right, so let's start today. So the first I am gonna ask you guys if you guys have any questions from our last day session. No, I don't. I don't. Okay, all right. So then you guys, I have a question and you guys should answer me. So tell me like what is the role of a project manager? What the project manager do in the project? I can go. Go ahead. The project manager, they will upgrade the resources they need. How many, for example, how many BA they need to be working with developers and then they document it and they will do a planning and then prepare a timeline of the project and then the timeline will be the kickoff and the end of the project. And then after that do an execution planning like when they will execute the project and they will then start the project and the BA will be the one, the first person to start the project. And then they also have, let me go back to resources planning. Like they will reach out to the BA manager, QA manager, develop dev managers and they will ask them, they will ask for example, the BA manager like how many BA they need and the timeframe the BA will need to work on the project. So they will get an answer on that. Like for example, they will need like one full time BA for 400 hours for example. And then they will do the same for the QA manager and the development manager. So they will ask them the same question and they will also reach out to them access where and how they may need for the project and they will gather all this information and then get their time, do the timeframe of the project and then kick off with the project. Basically that was how they, that's for the project management, project manager. Okay, all right. Thank you. Then Hardil. Okay, I actually, I'm sorry if there's any disturbance because I'm driving with my family's Black Friday so we're shopping around but I managed there. No worries. No worries. Yeah, because I got my kid in the car with me so he's loud. But yeah, the project manager, like project manager's role is like how the stakeholders give the job like the project is handed to the project manager and project manager decides the hardware, the software they're going to use, the stuff that they need to manage this, the time limits for the VA's, they're going to assist VA's and stuff. And pretty much that's it. And then afterwards like business analyst takes it, right? Like he finds the architecture, like it's a role of it, like it's a protocol that project manager use and then the VA comes and then the architecture, like the system architect that designs everything and the developers code everything. I mean, I know I went step ahead. I'm not explaining to you what project manager do. Project manager like basically like, I just know the three steps what you told us. You know, like the hardware, software, how many people, you know, how many hours, you know, that it's given it to project manager by the stakeholders, right? Yeah, I'm on the track. Yeah. Okay. All right. So then, okay, that was good one. So basically like, you know, my question next is to both of you that before, so all these three tasks that were like, you know, discussed. So are they done before the VA starts the work on start working on the project or, you know, when they are done in time? So that is my question. You're asking you're, I'm sorry. Dad, you go ahead first. Okay. Yeah, I think all the process is done. They need to get off with the project. All right. Yeah. So are there you? Oh, okay. So what was the question? I'm sorry. Like, I'm so sorry that I just got a little late. Yeah, no, no worries. So question is that all these, you know, the three steps that's, you know, preparing the timeline and that is basically time. You know, timeline would be either in, you know, project planning document or it will have itself own document like, you know, project timeline and preparing that project plan resource plan and all that. So this, the project manager complete before the VA starts working on. Yes. Yes. Yes. The project manager has to like, you know, yeah, that completes beforehand, like project managers to come up with the plan, right? And then it gives a sort of business analyst when project manager decides everything. Okay. And after that project kickoff, you know, happens and project team project team start working on it. So that is basically like, you know, that's what the, you know, after three step, the fourth step is. Okay. All right. And then comes that, you know, VA start working on the project. Okay. So after the kickoff, kickoff, then business analyst start working on project. Okay. And then a summary of what the business analyst like, you know, do. So then what the VA do in different phases of that project. Okay. That what we discussed yesterday. So just on that question to both of you, what the VA does during different phases of the project. So I want you to explain in like the each phase. What is the role of a VA during the business analysis phase? Okay. The role, what do you say, please the role of the VA during the business analysis phase? Okay. The role of a VA during the business analysis phase. I think the VA starts by documents all the requirements. And then after that, the VA will reach out to the system analyst gather all the requirements needed and then after that, the VA will reach out to the developers to do the same with them, take all the requirements, assist to some of the to their meetings to answer questions regarding all the requirements gathered before the start the project. And then the VA also will have to help answer the questions in regarding the QA testing like where they go for testing. So yeah, in what phase VA does that? Do like which work do the what you're telling that, you know, working with the QA answering the question, what the project is basically when the VA does that activity working with the QA, they do that on testing because the QA is the one that's supposed to test the software at the end. So that is when the VA works with it with the QA during testing. Okay. All right. And then. Hardly. Yeah. So what did I get from, you know, what you told us last time, the VA's job is like, you know, they have like, you know, VA decides how many hours he has to take, you know, to do the job unless the project manager is the hours given it to unless the stakeholders needs this job done in a certain amount of time. Right. So so what VA does is be like, you know, controls everything afterwards. Like, you know, he go, he gives a time to like, you know, the system system analyst, you know, like, oh, he has to take this much time to do his job, but they all like system analyst has to report back to the VA to, you know, if there's any, like he attends meetings and everything in the stakeholders receives like, you know, all the requirements and stuff like that. If the company's like, you know, the project's handing in to them, like, you know, if they need to change anything into like, you know, for the whatever is the task is given it to them, you know, so he attends the meetings and stuff, stuff like that. Basically, he becomes the head of whatever the job is given it to it. So the developers is given at the time, that's how many hours they need to get their work done. If the developers need anything, any questions that goes straight to the VA and be straight, like, you know, handles the business with stakeholders, you know, so like, you know, VA's job is basically like, you know, follow up with everything. And if they have anything needs to be changed or the stakeholders want anything needed to be changed in the last like, you know, and throughout the, you know, task is given it to the, you know, people and he handles everything. Okay. All right. So there is like, you know, it was kind of open book. You are seeing at the screen if you are, you know, looking at that, what I was asking the answer is right in front of your eyes. Okay. And that's what, you know, I have explained to you guys in the last, you know, session. Okay. So basically there are three main phases of, you know, the whole software development lifecycle, analysis phase, development phase, testing phase. Okay. And in analysis, there is a first, you know, sub phase that is a business analysis phase and then second is system analysis or design phase. And then like after their development phase, testing phase, so this is like, you know, and these are aligned, these phases are aligned with what? They are aligned according to the project timeline. Okay. Project time timeline and where the project timeline located in project plan. Right. So these are in alignment with the, these phases in alignment with the project timeline. Okay. So the BA role summary that first thing that you have to basically understand. So first thing of the first job is the BA to do the business analysis and that is basically like, you know, when BA only working on the project, just like the project manager was only working during the project planning and all these three steps when doing, there was nobody else, just a project manager from the team perspective. Okay. So that was the only single person working. Now in the business analysis phase, BA is the only person who is working to gather and document requirement from the stakeholders and stakeholders are all those like business folks who have requested the project. Okay. And or anybody who is impacted by the project by that project requested as well as impacted either they are directly or indirectly impacted or they're you know, in any way they are impacted, they would be the stakeholder. So they needed to be in those requirement meetings so that they can, you know, make their inputs whatever that is, you know, needed from their side. Okay. So business analysis, the BA does and only now BA is working for one month or two months or whatever according to this project timeline. He have to complete within his like allowed time. He or she has to finish the requirement gathering and how the requirement gathering is done just as a summary that, you know, BA work with the stakeholder ask question, BA has a requirement template where he start documenting the requirement and multiple meetings with the stakeholders to back and forth, you know, questions, feedback and all those like session the result is business requirement document is prepared or user story document is prepared. Okay. So when that is done, so that is basically you can say 100% time BA is working. So BA's main job, if you will look at the big picture of a BA role, so 80% of the work of the BA is during the business analysis phase. The rest is only 20% of basically time he will be spending on. Okay. So this is the main thing and the rest in the next he just have to, you know, have help system analyst understand the requirement or any question they have about the requirement. Okay. So just explaining the requirement and ask answering any question with the requirement that is, you know, the BA role or during the system analysis and when the development happened, just attending one or one hour meeting, maybe a day or every other day with the development team, if they have any question about the requirement, just like attending though their meeting, if they will be asking any question with the requirement answering, otherwise just sitting back and, you know, just looking what is happening. Okay. And the connection is breaking. Is it better? No, yeah, still breaking. No, it's better now. Was that breaking for everybody? No, no, no, I think it was just hers. Yeah, it's okay now. Yeah. So yeah, so probably your connection is weak because when you was previously speaking, it was breaking. So, but you know, like it would be recording. So if you missed anything, you would be able to hear that. But you know, yeah, the connection is basically on your side breaking. All right. So then again, let's get back to the business analysis phase. This is the main 80% of the time of a BA that would be spent in there. Okay, in BA business analysis phase. Okay, so this is like how all the work of the BA is being done in this phase. The rest is basically explaining that work to him and acting as a liaison between the business and the technical team. Okay. So, okay, one thing, I'm sorry, I'm cutting you off. So you're saying business analysis. Okay. So the 80% of the 80% of the work that you're saying, he just it's like basically his job is just to get a requirements and prepare for the stories and stuff that is given its one. Right. That is his main job. That is his core job. The rest 20% of the time, he is just explaining what he's documenting explaining what to do, right? What no, no, no, no, no, no, no, no, no. There is a nobody telling nobody that what to do. He is explaining just those requirements that what was the, you know, user ask. Okay. Okay. Okay. Basically explaining that document. That's it. So he is not telling anybody what to do. He's not, he is just custodian of those requirements that he, you know, gathered from the stakeholder. So those requirements, those user needs that user identified that are, you know, those problem statements, whatever they are requirements are, that's what he documented. And he understood those documents, documented requirements. That's why, you know, he would be the basically subject matter expert for to explain with the other team. Okay. For example, like, you know, requirement is this and they why they need that, you know, what is it? Okay. So he will explain the other business logic is this because they are having this problem to resolve that problem. They need this. Okay. Okay. I got all that like, you know, so that would be like what he would be communicating. So there is a one thing that, you know, the BA nobody in there telling nobody that what to do. Everybody knows their job and they will do. So be is just explaining those requirements to them. You know, initially maybe like how they be explained first maybe like giving them overview of that requirement answering any question. Okay. Okay. Then later on they will request to the BA that hey, we have some question. Can you tell us so it can be like one to one, one, you know, BA to whole team can be multiple session from the BA with the team if they have question. Okay. So that's how I actually play out. Okay. Okay. Now, now it's clear now. Okay. Now it's more clear to me. Okay. Okay. And during the, during that design phase because those requirements are the input for the design because those requirements are what the business need is. Okay. And what would be the solution can only be after you know, the technically understand the business need and the business need is stated in those requirements. Okay. So that's why we when I say that, you know, business requirements is the input for the design that what it mean. Okay. Because design is the solution of those requirements. Okay. Okay. So that's how the hierarchy is a business requirement document is, you know, input for a system design document and then design document and business requirement both are input for the, you know, solution are, you know, the coding and then we business requirement and system requirement are both are input for the test cases. Okay. The test cases are being written assumptions and all those scenarios based on those requirements that what is so each business requirement or some system requirement is converted into test cases. And then, you know, that's what the BA the key way use both both the document to create their test cases. Okay. Okay. And one other thing that during the development phase, what is the so right now we are just, you know, with the BA perspective explaining what the BA does during the whole like, you know, development, whole software development life cycle. Okay. During all the phases, but the BA does. So first phase business analysis phase. We already discussed what does design phase. We discussed what they does and then development phase we discussed what the BA does and during the development phase, BA also work with the QA because the development is doing the development. What the QA is doing? Okay. The QA need to start creating those test cases, which they will execute when the testing phase will come. But before the testing phase start, they have to be ready with all those test scenarios test cases, whatever they need to start testing. Okay. So during the development phase, when development happening on the sideline QA and the BA, they are working together to, you know, create be a QA career test cases and they work with BA to understand the requirement. Okay. So during the development phase, if I will ask you what would be the role of a BA during the development phase working with the development team answering their question and then working with the QA on the sideline to answer any question the QA have so that QA will create test cases or in simple word be a partner with the QA during when the development happening partner with the QA to help them create the test cases. So that would be the answer. Okay. And then what does BA do during the test testing phase? So now in the testing phase test QA are already, you know, ready to go to take the system and in and out test it all, you know, business requirement and the, you know, system requirement, they have test cases for that. So they, you know, execute those test cases during the testing phase and BA attend their, you know, daily meeting. If they have any question regarding the requirement, they can ask or if the BA see there is some requirement, they don't, the BA doesn't, you know, see the test case for that. So BA can point out, hey, these requirement, I don't see any test cases. So are we like, you know, maybe I'm missing. So which test cases are related to these two requirements? So BA does create a document which called traceability document, which link all the requirements to solution to like a development to testing. So in the requirement document requirement are, you know, numbered as R1, R2, R3 design document. Each requirement design is like D1, D2, D3. Okay, just like, you know, the requirement and similarly like, you know, the development each functionality is basically numbered. So BA keep a document which called traceability document which he uses during, you know, system analysis development testing phase just to track that all the requirements have is having a solution and that solution is being tested. So that is the traceability. So that is another additional task of the BA which he does during other phases after the business analysis phase. Okay. So that is basically like, you know, what the BA does. So I want you guys to do like assignment this weekend. First assignment is act, you know, as a project manager, okay, and create a document resource planning document in which you, you know, have like, you know, this many numbers. So it's just like a role play and create that document just to give like, you know, how that will look like. For example, be like a project manager and all the stakeholder. You know that what they do. Okay. So project and BA managers, what would be the hours for, you know, different teams. So creating that and creating that timeline. So choose any project, any, anything that in your mind and just create that document. So don't worry about it is wrong or right or, you know, whatever your understanding is, put it on paper and what I want to see, I want to see that, you know, a document that is created, which has like, you know, team name that this role will be needed. And this many hours it would be. And then imagine like, you know, the project started from January to like, you know, how long is the project and what phases is, you know, will be completed in what month? Okay. So this is one and then other is basically the role of a BA but question is what does BA does during the each phases of the project? So you will like, you know, create this type of basically a chart that BA does in, you know, business analysis phase one, two, three, four, five, six, one system analysis or design phase BA role do this, this, this, this development phase BA does this and then do that this testing phase BA does this, this, this, this. So this is like a couple of things that I want you guys to, you know, basically prepare during this like two days. Okay. Okay. Make sense? Yeah. Well, you just want us to do assignments started with the project manager and then the BA. Right. So both roles. Okay. Act as a project. Both roles, what they, what they do act out like just pretending like we're exactly just like it's like, you know, use your imagination. Okay. Okay. So act as a project manager. What's the project manager does before till the kickoff and then act as a BA. Okay. So as a BA complete put a complete story, you know, whatever I want to see your creativity on it. Okay. So this is the assignment and it is make it fun and you can create create any projects. So project can be any project like even like a cooking meal for Thanksgiving. This is a project. Okay. So for that you have stakeholders, we want this, this, this, this, this, you know, requirement list. These are the requirements and then, you know, solution for that and all those solution are basically recipes, right? Yeah. Oh, created those like recipes and then basically, you know, just testing who were the, you know, tested and all that. I mean, similarly, like, you know, anything I'm just like putting out there, you can pick any of your previous projects are, you know, anything you worked on. So project being project, it doesn't have to be like IT or technical just do anything. Yeah, you just wanted it. Yeah, you just wanted to see like you wanted to create like, you know, you want us to create this. So you just wanted to see how much like, you know, exactly where are the gaps and how much you are understanding and digesting is. Yeah. Okay. So yeah, I am gonna like, you know, make you guys basically like, you know, or digest all that and then basically reproduce the way it really is. Yeah, it's better, better way of learning. So that's okay. Okay. All right. So that pretty much it for to a short and sweet session. So any question? Uh, no, as of now, yeah, as of now, nothing, you know, it's just a, we just got the assignment handed to us. So we just, I'm just going to try to work. I mean, you know, I'm sorry. Yeah, came late and stuff. No worries. No worries at all. Take it easy. So yeah. So don't. Yeah. And I mean, for me, I'm okay. Okay. All right. So yeah, so do not take this assignment like as a college assignment or anything. Don't take it as a burden. Oh, no, no, no, no, I'm gonna, I'm gonna try. I'm gonna try what my mind says and then I'm right. Right. Exactly. Because if you will, the whole purpose is that you will make mistakes. Yeah, definitely. Yeah. If I will know that, you know, what is your understanding that then I can correct it. Okay. And then I can show you like, you know, both you both guys are answered and then I basically like, you know, kind of a given you an overview know you both know that where you was your, your concept was wrong. Yeah. Yeah. Okay. So the whole purpose of this is basically to get you corrected and get you basically like, you know, so do it. Don't basically like, you know, be afraid to make mistake. It is not a, you know, college assignment. There is a no basically scoring or anything. So take it easy and do it, you know, don't stall it or don't be worried. Even if you are blanked out, just take my example of, you know, cooking a meal and create some, you know, nice projects. Okay. I'm just gonna, I'm just gonna go, I'm just gonna ask you one thing, just one thing, just to clear up. Okay. So I know, I know you probably explain it to this and I just need a review on it. So the project manager knows when, when the, the project is handing to the project managers by state, by stakeholders, right? Yeah. So project manager already know in an IT team that, that many people she needs. Right. Right. So yeah. So that's, that's like, that's not any IT job. Like what, when it's given it to it. So the, the project manager already knows I need to be a, I need a like system analyst. I need developers, you know, and then, you know, like the testing phase, that's, that's already written right before the job is given it to the project manager. Definitely. That, definitely. That is already. So this is basically like kind of becomes like, you know, how the things are being. So if you will see software development life cycle. So there are analysis phase, business and system analysis, there as a development and there as a testing. Okay. Yeah. That phase is already there in IT. Exactly. There, those phases are the way that, you know, the development, the way the project is going to run. Right. So for each phase, there, it's understood you need people to finish each phase. Okay. All right. So similarly, like, you know, if the project is service now project, then the development phase will happen, but the developer will be service now developer. Okay. Similarly, like, you know, if the Salesforce project is then developer will be Salesforce. Dotnet based some application development, then developer will be dotnet developer. Okay. So that variation within that, but you know, there will be like understanding that developer needed QA needed, be an eithered system analyst needed or you know, design system design person needed. So it's like, you know, understood knowledge or you can say, you know, common sense for with regard to the project. All right. Okay. All right. Perfect. Yep. So we'll do our best, you know, and all right. So that's it for today. Thank you very much for joining and you guys have fun. So there's nothing on the weekends, right? No, no, nothing on the weekend. We will meet on Monday. So we can take our take time, you know, and listen our session again and create your assignment. And this will be recorded too. Yeah. This is this is recorded too. So you will get the. Yeah, because I'm gonna, I'm gonna go over it again because I'm still driving. So again, I was just listening to it. So I'm just going to go over it one more time. Okay. That sounds good. All right then. All right. Thank you very much. I wish you a great weekend. All right. You too. Bye-bye. Yes. Go ahead. Yes. So for today of this, basically they say this and we go to the assignment. Uh, that week, we went to the room. Your, your voice is pretty like, you know, uh, it's really like cutting bad. So you have my number. Just give me a call and, uh, I can answer the. Okay. Okay. Okay. Thank you. Thank you. Bye-bye.