 Sorry, I was good evening got into a customer service and it is awful Okay, all right, so what you guys Did own the assignment anything you Yeah, actually That's how you pronounce your name, right? So yeah, right. Okay. Um, right now I mean I had a little an emergency where I had to step out of the house so I'm attending this course on the phone right now and You know, I didn't I didn't get to create a PowerPoint and stuff like that Like I just made a you know, like notes and I was gonna scan it through it and present it But I think it's not gonna happen to like 636 40 because I won't be home My mom had a little health complications what I had to know worries. So just you can explain like a you know What you yeah, I mean I can present it what I what I thought over it, you know, okay. Yeah. Yeah, that's that will do Yeah So who want to go ahead first? Doesn't matter you want me to go. Yeah, sure All right, so I'll go as you said like, you know, think over something like how you gave an example of like a Best Buy So think over something about like, you know physical, you know and the virtual like the difference between that, right? Yeah, so I came over with like I didn't want to I didn't want to like do a store, you know Because we already did a Best Buy. So, you know, I did over something called like, you know, something something like car dealership You know how they perform virtually and physically now in these days So in like, yeah as a physical like, you know, I'm gonna just I set up an example Just not not to make a profit virtually but like how to save time, you know How a couple years back when you wanted to test drive the car, you know You had to personally present it to yourself over there and the guy will come to you We'll take your license and insurance car make a photocopy and everything make you wait, you know and everything and then let your test drive the car So now like, you know, whatever I, you know, figured it out in these days how like, you know, this virtual it made it so easy for us You know, it's like you do it everything online, you know, you go to their website, you know They ask you for your license and stuff like that. You just scan it, you know through your phone and everything and it presented to them Right away right then. So you're not wasting time. You go straight to the dealership pick up the keys and you start driving it So it's like I'm not saying about a profit or anything but I presenting this as stuff like how like, you know, it is making it like, you know, life easier and how it works So that's what I came with another point, you know, like it's it saves like, you know, how they're it's less employees. So they're making more money having like, you know, for us to do more work, which is very easy, you know, if you think about it, sitting home, you're doing everything online, you know, and you're getting stuff done where you had to present yourself in a physical form and get there and do everything, you know, on the papers. Right. Yep. So that is a, you know, good example. So basically, like, you know, they are now if we will describe that how they are performing their, you know, the business, like in more in a virtual fashion, they are using multiple softwares. Okay, that are being that are being built with the from different companies. So for the softwares, there are three scenarios like, you know, one is the company build their own software from scratch. Okay. And that is only big organization do, you know, does that. And then second scenario is that you, you know, go to the market off the shelf, take a software, and then you have a team who will customize it according to your business needs. Okay. So that is basically the second, second scenario. The third scenario, the company already have software, they want to enhance their existing capabilities of their systems. So that is the third scenario. So that they are kind of universal three scenarios in any type of IT, you know, business, either it will be like, you know, brand new, or it will be just some enhancement in the existing system, or it will be out of box solution, which means like, off the shelf, you know, software, they are either getting, you know, basically subscription off. Okay. And then basically then, you know, going from there. Okay. So basically, like in the, like, you know, for them to provide their service to us online, they're working with the bigger software companies where it which is handled by a lot of people. Right, right, right, right. Okay. Okay. Okay. Okay. All right. And then, okay. So, okay, so who's going to go next? I'll go next. This is Amadu. Okay. All right. We'll go ahead. Okay. So the assignment was to say like a difference between, for me, they were understood it between a virtual store or online store and a physical store, right? Or virtual business and physical business. So I did the same example with a clothing shop. So for me, IT makes things easy. You don't have to always drive all the way to go to a store to maybe shop for dress issue or whatever it is. And also you just have the options to maybe scan your card and then buy stuff online, the delivery system, like everything just becomes easier than going into a physical store. So yeah, basically that's just what I did. Can you hear me? Yes, I can hear you. So what's the ease you pointed out? Ease is that is one thing. What, if you will think from the business perspective, what is the benefit to them? The benefit to them, I think the online store gets more sales for me. The benefits for me, the benefits for the shop like they get more sales and more products. The benefit is that they get more profit because a lot of people shop online than in person. So they make the work easier for them and they had more clients virtually than physically. Okay, so more business basically. So that is one thing. So can you compare like that business, what they are business versus expenses, profit wise, where the business is making more profit, like on the physical or the virtuals? I think they are making, it depends, but the business I looked up, I believe they are making more profit on the virtual, not the physical because let's say a virtual store, some stores, they can have like payment plan, payment plan, for example, let's go with I can say take the same example, Best Buy. You can have payment plans with Best Buy, like you just shop whatever you want to shop and then you do payment plan. Whereas when that wasn't existing, you just have to raise your money and buy whatever you want to buy. Now if they have a lot of people going through doing payment plan instead of just going and just save money and buy some things, they will make much more than what they will do in the physical store for people just coming in and just buy directly without doing the payment plan, for example. So coming up with that one, I believe it goes through the IT section as well. So the idea of payment plan, everything's still surround, it still go around the IT section of the whole thing. So for me, a virtual store makes more profit than a physical store in 60% of the aspect. Okay. All right. That sounds good. And who is next? Hi everyone. Good evening. So for me, I went for an online clothing store too. So the difference I picked out is when you want to do shopping, virtually you just go ahead and do your stuff. You get whatever you want, put in the card and you check out. But physically, if there are a lot of queue, you need to go through that route and not everybody would like going with that so much line. So I think the virtual buying is easier than the physical course. Because you can get up at any time and buy whatever you want to do. You don't necessarily need to go to the store. So the virtual makes more profit than the physical. Okay. Can I mention something on it too? Sure, sure, sure. I feel like, yeah, virtual, like when it comes to stores, like you gave an example yesterday and I feel like virtual has more quantity. You know, like there's more stuff that you could look it up and like when you go in personal, feel like they don't have enough stuff in the store. Basically customers going in there and they're turning back saying, oh, they don't even have anything. And especially like you said, the fees that they have to put like, you know, keep, have the workers stay in the store to keep racking up the shelves and stuff like that. Virtually it's very easy because they're going to ship it straight, you know, and they don't have to worry about what are they carrying in the store. Like, like, you know, right now in these days when you go to an actual store in the malls and stuff, you know, they have a one or two things. You know, but when you go on the website, even though you go into the store, they'll tell you, oh, we have it online. We could have that delivered to your house. Yeah. You know, and it saves them. It saves them a lot of like, you know, time and like, you know, money wise to because, you know, they don't have to, you know, have that many people working in, you know, in the different departments where you could just look it up online and how it works, you know, or like over the phone or like through the app. Right, right, right. And if you have that is very basically like, you know, a good example. And if you have observed like lately, there are even they are very shortstop, like, you know, almost every store they are very shortstop. And either they are not hiring, or nobody wants to work, but you know, basically not hiring is more make sense because, you know, they don't want to basically like, you know, have to pay more people. They want to just like have the customer to change their behavior and buy online. So if you will make something difficult or miserable, you know, basically in normal process, what what is the alternative, you will try to, you know, take the easy route so that they are changing the customer behavior basically like, you know, pushing the customers to like go online instead of, you know, in store. So that is just like another basically like, you know, the thing they are, you know, doing changing the customer behavior. So make sense. Yeah. So now imagine like, you know, if they don't want to hire basically people in the physical business, where they are going to hire, they are definitely going to enhance and hire more people in their like the virtual side. And that's what gonna is happening basically, like, you know, they're hiring people in their basically virtual shop for the virtual side of the business, but not, you know, the physical side, you know, and also cutting down the physical side. If you guys like have observed that we used to have Sears stores just like Target and, you know, Walmart, there was a one brand Sears. Okay. And they have completely shut down throughout the country, but they virtually they are selling everything. And now the more basically the model of being like the Amazon and like eBay, not the eBay, but Amazon they are adopting they are providing their virtual like, you know, platform for people to basically for businesses to sell over there. Okay. So that is another thing that is, you know, going. So let's get back to so now we got with the first basically day. Our objective was to get understanding of the difference between physical and the virtual business similarities and differences of, you know, that and grabbing the concept like, you know, why the businesses are putting more effort on the virtual business as compared to physical business and how the physical business is shrinking while the virtual business is basically enhancing. Okay. And this is just for any and every type of business this like, you know, trend is not just for in the retail industry. It is almost in every industry that, you know, is happening that they are moving things toward more like the virtual side than the physical side. Just give me one second. I have a call that I have to take. So apologies. All right. So today we are going to like, you know, go to the next step. Okay. And going to discuss that how the work is being done in 90. Okay. So we got the concept of what is it. Okay. And when we will say it, it means like, you know, the whole business, it's like, you know, any other job, any other regular business, but it is the business is virtual business. So both these things are basically kind of, you know, foundation store to build the understanding on top of it, because most of the people who are, you know, like, you know, not in it industry, they just for them it. They think like a website, they are, they think like, you know, that maybe Facebook or, you know, some app, and they're basically like, you know, correct. But the only under with this training, you will be able to, you know, understand how the work is being done in 90. And what are the different roles and then train against those roles. Okay. And then you would be like, after we are done with roles, you will see like, hey, it is very easy. It's not like kind of, you know, hard. It's easier than basically like a physical store job. Okay. And the only the skills that you need at least high school degree and then basically communication skills that you would be able to communicate what you are understanding. You would be able to have a conversation with the other. And that's pretty much it that, you know, you need it in your basically like, you know, skills. And you would be able to perform the job very easily. Okay. So with that said, let's like, you know, move to the next. So in it how the work is being done. Okay. So let me so in 90, the work is basically being done in a form of, you know, the projects. Okay, so project by definition, project is just a piece of work that has some starting point. And that has ending points. Okay, it's not kind of infinite that keep going on, it will have it will start at certain point of time, and will have a certain. And that certain point of time. Okay. So that piece of work that is called the project. So in it, the method of, you know, getting the work done that is through projects. Okay. And each organization have like, you know, hundreds and thousands of the project in their basically like, you know, pipeline. Okay. So what happens that anytime the business, the IT folks, you know, the IT side of the business, they have any problem, or they want to, you know, solve some issue with the business. Or they may be like want to increase their productivity and grab some opportunity. Okay. So in the physical store that there is like the different, you know, way of doing the business development, but in the virtual, because the business process are being, you know, done by software. So ultimately, they need some enhancement or some new feature in their basically softwares in their capability, whatever the department they are, you know, doing the so any P problem or opportunity that they grab result in form of a project. Okay. So that, but the limitation is that IT can only do a certain number of project at given, you know, point of time, they can do to like, you know, short resource, resources availability. Okay. So that then what happened that, you know, if the business side or the operation side is requesting kind of, you know, 100 projects, they might be able to do only like 30, you know, after six months, another 130 and but all those projects that are not being done, they will stay there in the pipeline. And every time they will be considered when whenever they are business and IT meeting and setting up the priority, basically, they are prioritizing the work that what IT can do and based on the business need to business. And when I say business, you know what I mean, that's like the business operation folks like, you know, who run all the virtual business for the organization. Okay. And they there are departments just like any physical business operations. So business operation wise, the physical business and the virtual business, they are kind of being run in the same way. Only the processes and the processes execution is different. Okay. The physical business that, you know, the supply chain is different their execution, they basically like, you know, go you go touch and feel and, you know, like check this by the item and then the store people have to, you know, do all that other tasks related to, you know, providing those services. Okay. But in the virtual they will like you just browse the on the website see what what you like what is their basically configuration and you know what features they have compares things and then select one check out. And as you will check out order goes to basically fulfillment payment goes to accounts. And after the, you know, the fulfillment have a confirmation from the, you know, the accounts, they ship ship out that, you know, item to your address. Okay. Or they ship out to their stores, whatever the option you have basically chosen. Okay. So with with that said, let's get back to our conversation on the, you know, the project. So in IT, the work is being done in form of projects and project by definition any piece of work, which has a starting point and ending point. Okay. So broadly, we will basically, you know, divide a project it has three phases. It's like initiation phase, you know, and then planning execution. And after that, you know, closure or deployment or, you know, ending up that project. So these are basically like kind of three phases of any project. Okay. So how the initiation happened just discussed. So let's like give me an example for example, you know, these are the folks who works for basically like, you know, like Samsung account for Best Buy. Okay. So this is like electronics and under the electronics, this team, they work with the, you know, Samsung, that is basically a vendor and supplier for the Best Buy. Okay. So they are discussing that, you know, Black Friday is coming. So they are, you know, what deals that they have negotiated with them and what they are offering and how to basically like, you know, grab that opportunity, you know, value wise and, you know, sale wise and analyzing all different data and then seeing that, you know, what would be the right, basically amount and what we can provide. So all that like kind of, you know, business discussion they are having and at the end they have decided, okay, alright, so this would be like kind of, you know, the list of the product that we will be putting on our Black Friday deals. And this would be their prices. And then they appoint somebody that, hey, can you like to do that we need to get basically enhancement in our existing, you know, system. So let's like create an IT project and project on that and send it to IT. Okay, so they started this conversation probably like some somewhere in July or June, and they decided by, you know, August to, you know, like have that basically done. So, so this is basically how the project has been created. So likewise, many other departments and many other people they, you know, creates the project, and then projects goes to IT and the business to discuss that, you know, what needed to be done and how they can basically do it according to their capacity. Okay, so one document that is being created when the project is initiated and the when the business basically decided that they need to do a project, they create a project request document. Or we also call it project charter. Okay, our project, you know, proposal, so they create that document and that is basically outcome of that activity this like initiation discussion. Okay, and in this project document, usually they put like a kind of a, you know, problem statement that what the issues they are having and what the problem they are having, they may put like, you know, a stakeholder name and they put information like what different business segments are being impacted and what is in scope and what is out of scope. Okay, and some budgetary guideline and maybe current state and what the future state they want. Okay, so this, these, you know, information they put on this, the project charter template, and then send it to basically like, you know, IT. Okay, so, so problem statement and opportunity statement, you know, like any issue they are having, for example, here we discussed that they were discussing this like Black Friday deals but they got from the Samsung. So that was their opportunity statement that, you know, this year we got these, these, these deals. And last year we have, you know, this much sales and this much with these, we would get whatever they're like, you know, they put something in the intro, put something in the problem statement, and then stakeholders name they put somebody who would be kind of helping to give them further requirement. And then in scope and out of scope, they will identify that what is in scope for this project, you know, only those items which is being, you know, for that Black Friday deals that would be in scope, rest of the things would be out of scope, means they are not going to change anything other than those items. Okay, so that is what in scope and out of scope, you know, mean and current state that what is the current state currently those items are being maybe that's, you know, 500 and that would be displayed with the discount like, you know, 430 or something like that. So the current state and the future state they will like, you know, put put in there. Okay. And that is basically what they call, you know, the project charter. Okay, so any questions so far. No, I'm with the follow up. Yeah, I'm fine. Okay. Alright, so let's like, I'm recapping that what we have basically discussed. Yesterday we discussed between the different difference between physical business and virtual business and similarities and difference and why what it means when we say it, it means like virtual business or the business that is being run digitally. Okay. Sure. So is the project chapter like a roadmap. So you say it again. Is a project chapter like a roadmap project is a project and the roadmap. You project is basically like, you know, covers the roadmap, you know, roadmap is the part of execution part, you know. So you can say if we will like, you know, say the roadmap, it comes under like under the execution, there will be roadmap to execute that project. Okay, so project is kind of, you know, you can say a more big picture. Okay, so roadmap is just a subset for the execution. Okay. Alright, so make sense. Yeah. Yeah. Okay. Alright, so let's like, you know, hear that again that yesterday we discussed, you know, the concept of it, what it means it means like a virtual business and what is meaning a virtual business like any and every business which is run. You know, more virtually are using software that is a virtual business. Okay. And then in the, you know, even the physical business has some like, you know, it that in there. Okay. So all that software that physical business use that also comes under it. Okay, because it build those softwares and the physical business, any physical business use a lot of softwares for inventory for basically like, you know, accounts for their, you know, point of sale and everything that use a lot of, you know, softwares too. So just want to basically help you understand the scope of IT that even the IT if you will say like, you know, 30% of 25 to 30% of physical business operations are being done using software that will not be exaggeration. Okay. So IT not only covers their, you know, the virtual business, but it also have a portion of like, you know, 25 to 30% operation of the physical business all software needed that is being built by IT. Okay. So that was further enhancement in your understanding that what IT means. So that and in IT today we started that how the work is being done in IT. So in IT the work is being done in form of projects. Okay. And the projects by definition is like any piece of work, which has a start or starting point and ending point means like it will start at certain day and time and will add certain day and time. Okay. So that's why it's like, you know, organization I have, you know, 10s and 100s and 1000s of projects in their pipeline because, you know, whenever they need something, little bit of thing, they just create a project and, you know, and they are the IT operation folks, or IT business operation folks are continuously like creating more and more projects. Okay. To like get what they are, you know, what they want and ultimate objective of any business, what they want to make more profit, sell more things or, you know, may sell more services or products and make more profit and more money. Okay. So with that, that said, they have a lot of projects and how the projects are being initiated are created within an organization. I've given you an example that, you know, these are IT operation folks, they sit together, they discuss opportunities and problems, what they are having. And then based on that, they come to like, you know, request that they need to either resolve their problem and opportunity, and then they create a request document, which we call project charter. And in that document, they state that what, you know, their problem or opportunity, that is also kind of high level, basically like, you know, request or the requirement that it's just sometime very vague until it will be, you know, the later on, like analyzed. Okay. So they create that document and send that to IT. Okay. And then next, when it goes to IT, that means like the initiation happen, then planning and execution phase that that starts. Okay. So in the IT, we will first understand that what is the IT team mean when we say like, you know, the IT team that will work on the project on the IT side, what are their usual components and like usual members of that team. Okay. So in that team, there is usually like a one project manager PM or project manager. Okay. And then there is a business analyst. Then there are developers multiple, most of the time. And then they are quality assurance analyst. There are also data analyst. If the project is related to some data or data is involved. So there might be data analyst. So these would be basically kind of, you know, folks in within the team, within the IT team. Okay. So then there is also leadership, which and some of the resources which are being shared between teams. Okay. So usually these folks work together in one project at a time. Okay. So they take one project, they finish it, you know, at a time. So that's why they are like kind of a unit in basically to execute that project. Okay. So then there are other resources to like shared resources like architect or, you know, data architect or enterprise architect. So which help these basically folks. Okay. So with that said, any question that is coming in to your mind. Nothing so far, but I just want to mention one thing. So, when you said there's a there's a group of people, you know, as an example, you give us like, you know, group of people when they come together. And they, you know, talk about like, you know, what's what's going on in like, you know, what's going on in the store, how can they make a profit and stuff like that. And they, like, you know, they so basically they plan out something to write this together. They make a plan what the requirements and stuff like that they need to get it done. And then they give it to the IT people. Right, right. That's totally right. Okay, so that's completely and the part you just explained it to us. That's like, you know, the developers, you know, business. That is that happens before before them. Yeah, that happens before that. And the word is given it to the people right like that developers, you know, project manager and stuff like that. So the work is handed over to it. Okay. It now and these are the people that we work in. Right, right, right. The team of the IT now, right? Right, right. Because I was driving. I'm sorry. No worries. No worries. We will repeat it, you know, multiple times, you know, to explain it so that your concepts are very clear. Okay. So I was just describing the IT team so that you have the idea what who are the IT team members. Right. When the initiation happened and then they create this as a project request before coming to the team before the work is being assigned to the team. There is like another, you know, the IT side and the business side leadership, they sit together and they prioritize the projects basically. Okay, I follow that I just I just saw it. That's why I was listening to it, but I just want to make sure now we're. I'm sure if I was left behind and we already in the IT team terms, you know, that's what I was thinking. Right, right. All right. Yeah, I caught up now. Awesome. So okay, so when the project request is already put towards the IT then IT and business folks, they meet and they discuss, you know, whatever the, you know, top 100 projects are there in the pipeline. So the leadership like, you know, the, the meet and they make the decision and then IT teams, the leadership know like they have maybe like, you know, 50 IT teams. Okay. So those 50 teams may be able to maybe able to do like kind of, you know, 75 projects during next six months. Okay. So based on that, they only like, you know, okay, so that like, you know, basically IT team only picks up 75 projects out of whatever the number they have. And they prioritize that in their during that activity when leadership both IT leadership and the business operation leadership meet. So they prioritize and they discuss basically budget and other but what's the business need is and based on that they pick up like maybe 70 to 80 projects out of whatever the number of projects, you know, the business operations have. Okay. And then when that, you know, that assignment happen and it is all always happening around because many people are doing their job, everybody is doing their job. So it's happening all the time. Okay. So the IT teams will have their projects all the time. There is no time that they will be sitting idle. They will be keep working one project to other, to other, to other. So, so similarly, like the IT side, they will have their basically delivery pipeline that, you know, these are the number of, you know, maybe 75, 80 or 100 or, you know, 200 the project that IT had promised to deliver. Okay. So they will be ready. And then there are like, you can imagine like 60 or, you know, 50 or 40 based on the how big is the organization and maybe in hundreds, these IT teams are sitting in the IT organization. Okay. And each team has a project manager, a business analyst, developer, QAs and you know, all those folks that needed to basically execute or deliver any functionality. That is needed or requested by the business. Okay. So then the project managers, they have, they are part of, you know, project managers organization within the IT. Okay. So in, so as the project is being assigned to the IT teams, it's usually get assigned to the individual first. And then pass on to other individual, then to pass on to the next individuals and so on. Okay. So, for example, project manager is the first person who start working on any project when it is assigned to a, like, you know, a team. And when the project manager finishes his or her, like, you know, task, the next person who pick up, that is a business analyst. And then the business analyst start working on, you know, his or her task. And then, you know, that business analyst is done. The project is being sent to system analysis or, you know, system designer to design the basically solution designer to design whatever the functionality that is needed. And as the, you know, system analyst or system architect create their design, then the development team starts and they start developing the functionality. They write, keep start writing the code and then the code is done. Then QA start testing that functionality. Okay. And when the testing is completed, then it will be ready for users or user representative to, you know, test the functionality and gives a final go ahead. Okay. So this is basically like, you know, how that is being, you know, done within the team. So now let's step back. So first person who will start working on a project is the project. Right. Okay. Project manager. So project manager. Now we need to know what is the task that project manager has to do. Okay. So project manager is basically do the project planning. As a first, basically business, our project manager or first, like responsibility of a project manager. And when we say the project planning, so it, it means like project manager have to do certain tasks. Okay. And in those planning tasks are basically resource planning. And what that means means how many people they need are how what is the basically hardware they need. Okay. How many team members they need for that, you know, team based on that project. Okay. And then what the soft software and hardware means that, you know, the people who will be working, they need laptops. Okay. They need certain, you know, softwares on their laptops. So all those needs for those resources that is planned by the project manager. Okay. And then also preparing a timeline of the project. Okay. That when it will start and when each phase will end. Okay. So preparing the timeline of the project and then preparing a communication plan that project manager has to update on the status of the project all the time that, you know, so whom he have to update and when he have to update according as per project timeline. So he prepared a communication plan. Okay. And these are kind of the main task that the project manager, you know, does to hand over the task for the next team member before, you know, the project manager would be hand over the task. And in each basically task, there are documents being created. Okay. Okay. So each day, a task of the project, there will be some document, you know, created. Okay. As a outcome of that. All right. So how basically then comes the question that, you know, if you are working as a project manager, you know, and these are the tasks that you have to do how you do it. Okay. So resource planning, how you do the resource planning and resource you already know that, you know, the projects you need what you need basically like, you know, QA, you need BA, you need developers. So all that people you need. So what you need to, you know, the plan for that how many people you need, how many developers you need for this project. Okay. So what you will do, you will pick up this, you know, the project charter may make a little presentation out of that, and then start working with the development managers, BA managers, and the QA managers that hey, this is the project. This is what they are looking. So how many people you need to do that? Basically it's a business analyst has to do what business analysis, business and requirement analysis. And then like system analyst does a design or system analysis, and then developers are programmers. And then after the actual technical folk, they code the features for software and then QA, they test the features coded. Okay. So these are basically, you know, the folks. So the project manager in the resource planning, they are not like born in the project yet. Okay, they haven't acquired at this, when the project manager start only project manager is working in the project. The BA QA, others are not yet basically allocated or assigned or hired whatever the, you know, situation based on that project. So project manager start the planning, work with the BA manager, you know, system analyst managers, development manager and QA managers and ask them the question that, you know, this is the project how much basically how many resources that you need. And usually that, you know, like, take that information in hours like, for example, you know, BA manager say like, you know, I have 500 hours worth of work for one resource, one BA to work on this project. Okay. And like, you know, put that like 500 hours for the BA, and then, you know, 300 hour, the system analyst manager tool, then, you know, 300 hours for this, and the development manager, you know, said like, you know, I need, you know, for developers, and for that, each of them have to work like 500 hours. And I need this, you know, their dotnet developer or whatever, you know, the kind I need these these these. So the project manager just document that and add that, you know, three developers each with this one, and then QA manager said I need to QA working full time for this like, you know, this many 600 hours. Okay. And so all those information that, you know, project manager put and put that in the resource plan and based on that information also create the project timeline. Okay. In the project timeline basically. So in the project, the first. So projects life cycle. I have a quick question before we move forward. Sure. Yeah, so the project manager needs to reach out to the BA, the system analyst, the developer, and the QA to know what they need for their resources, and then put it all together in the resource planning is that what it is. Yep. Okay. So the resource resource planning means like human resource planning, human resource planning when you will know how many people are working, then you will know how many laptop you need. Okay, then you will know, you know, for development, they need different software for, you know, the BA need different software for, you know, the data or system analysts maybe need a different software. Okay. So the need the starting of the planning would be first, you know, this project charter that project manager will go go on create a presentation off of that and then working with the, you know, do those technical leaders to basically document how many people they need. And from there, they will calculate like what hardware software need, and then basically like, you know, prepare a timeline that how that from the, you know, starting point or ending point, how the project would be basically done. Okay. Yeah. Okay, quick question, please. So does the project manager also get the availability of the PA system analyst developer and QA. Yeah. Right, right, right. So in the project planning, because that is the first thing is to put down a resource plan and get it like approved and you know, are usually like kind of a way of doing business and then definitely. He, when he had like, basically timeline put on and plan, you know, completed, then he will share that plan to their managers that hey, and in there, there will be as per life cycle that when the development is starting, for example, like, you know, if the project is starting the first analysis phase is starting in August. And for two months is like kind of analysis phase. After two months, the development will start. So that means the, the be a manager have to provide the resources, like in July sometime, so that they will start working in August to complete in two months. And similarly, the development have to provide the resources before they're basically like, you know, development part start. Okay. And similarly, so that certainly to answer your question, when the project manager will have that timeline and project plan ready. Then we'll share with the basically, you know, the development managers. Excuse me. Make sense. Yeah, it makes sense. So it means they all work in different time frames. Exactly. According to the project timeline, they all work according to the project plan and project manager prepare the project plan. Okay. Okay. Yes. Okay. All right. And in the basically like, you know, project life cycle, the first item is like analysis. Okay. And analysis, you know, first is the business analysis, basically, business analysis and outcome is basically requirements document. Okay. So be a does the business analysis. And as the outcome create requirement document. Okay. And then system analyst does the system analysis and at the outcome create design document. So the system analyst does it like work mostly with the software like, like, given telling the project manager how the different softwares are going to be using or what does the system analyst do. Okay, that's a very good question. So I will hold on your thoughts right there. I will explain to you what the system analyst do right now just focus on what are the phases. What are the phases in the project life cycle so that you would be able to understand the timeline of a project. Okay. Okay. And yeah, so all these roles we're going to explain in very detailed so don't worry but you know, hold that thought. Okay. Yeah, it is being recorded and I will have that basically this recording shared with you guys. So you will have that for your review that you can would be able to like a review and listen that what we have done. So just focus on your basically developing this understanding and questions don't worry about writing or you know anything you will have that and you would be able to basically like a review watch this in a video that you know whenever you have time after the training. Thank you. Okay. All right. So basically like you know there is a three main you know phases in that's in the basically project life cycle. Okay, and we also sometime call this project life cycle sdlc or software development life cycle to but they're they're the same thing. So, in the project life cycle, the first phase is basically analysis phase. Second is development or sometime we also call it implementation. It comes from like because sometimes you develop a brand new system and sometimes you just take like kind of off the shelf solution and implement it. And then third phase is testing and in the testing comes like you know system testing and then user acceptance testing user acceptance testing. So, basically this is how the project manager prepared the timeline. Okay, timeline is prepared around these phases. And these phases are being completed in a sequence like in analysis first will go business analysis, and that will be done by a business analyst. So basically what the business analyst will do he will talk to basically stakeholders these guys ask questions that you know what's the problem you know you're like having and you know all those question in detail because this proposal will be very high level. It will not like, for example, if they are asking for, you know, they may have like, you know, these five item will go into far, you know, like Black Friday deal. Okay, for for the Samsung. So that's what they have written as a requirement over here, but here the be a work with them and, you know, document all the details that how will be the look and feel what what's going to happen. You know, existing, you know, state is this and future state would be what so document the whole process whole like every step of that. Basically like you know, by discussing with the stakeholders. Okay, and create a detailed document of those requirements of all nitty-gritty details. At the end of business analysis that requirement document is basically the deliverable by the business analyst. Okay, and when the requirement document is complete requirement analysis is complete business folks, they sign off that document. Basically as a last step of completion. And then the next is basically the design that how the system will fulfill those business needs. Okay, so business need is they want to, you know, make more money by having these items as basically highlighted for Black Friday deals. Okay, so how they will like look and feel how the system will be made what will be the design of that. And with this is the system perspective, you know, the other the business analyst, you know, document with the business perspective. What the business need is, while the system analyst will talk to basically different systems stakeholders, and will document what is the system need. Do we need a new software to deliver the, you know, these business requirements are we need to made an enhancement in the existing system if the enhancement will be made what it will take. So basically prepare a kind of architecture of our design for that, basically how it will look like for those requirements that business has given and business analyst as document and then prepare a document, which will be called like a design document. It is also sometimes we call it a system specification document or just like, you know, specification document. So multiple name for the same document. Okay, so now you ask the question that what the system analyst do system analyst does the system analysis and what the system analyst take as a input those requirements that are being basically like you know documented from the like business side. Make sense. Yeah. Any question. Okay, so, of, okay, I have not a question but I just want to review myself. Okay, so the, the, the project is handed to the IT team, right. And the main lead is the project manager that creates everything like the timeline of the project how many months it will take and everything and then show show hot like you know, I mean, they already have a team. And then you ask her business analyst like how long it will take, you know what you need and the requirements and stuff like that. And then it comes to like system analyst right that gets the work from business analyst, right. And then it goes and then it spreads into developers who coded the the fields that needs to be done. Okay, goes back to us to test it if the project whatever it's given it to them, if it's right or not to present it to the users. Right, right, right. Yeah, so that is basically like you know the analysis design and that are the basically it's phases. Okay. Yeah, just one one moment. Yes. So let me recap that what we have, you know, over viewed today. So today, we have discussed that, you know, the project is how the project initiation happens. And outcome of initiation is a project request document that project request is then juggled to the IT IT and the business leadership they sit together, they discuss it. And then they prioritize it, it will pick up commit to certain number of, you know, projects as per their capacity, and then balls comes to the IT side. IT has multiple teams, 50, 60 teams, then they distribute those projects in among those teams. Okay, and one team mostly has one project at a time, sometime to depending on how big is the project. Okay, so they distribute the work and as the work is distributed, which mean they that work is assigned to first, you know, like the leader of the team that is the project manager. Okay, and consider that, you know, the how the work is gonna be like how the team is gonna, you know, get together, it's gonna get together sequentially as per basically like, you know, the project lifecycle. Okay, so the first person who got assigned the project is the project manager and project manager have to do certain tasks before the projects can basically and that task or project called project planning before the project even can, you know, go for basically like execution. Okay, so to do that planning, we discussed that what the project manager does. So role of a project manager, and we discussed, you know, what, what is the, you know, the do the resource planning, and but what the resource planning means like hardware or software resources and how they do that, we discussed that that they talk to the stakeholders for the business, you know, analysis, the business analysis, and analyst managers or system analyst managers or, you know, development managers, they talk to them, ask them the question, hey, this is the project, how many, you know, number of hours you need and how many resources you need, they document it. And based on that data, they prepare the project timeline and to prepare the project timeline, they prepare, you know, around the project lifecycle for analysis, for example, they put like the BA work is like for two months. So from say, from January to, you know, end of February, the BA work is then one month system design from February, you know, March to, you know, end of March, the system design, and then from like April 1 to next three months, April, May, June will be the development. And in the, you know, July, August will be testing. And yeah, so this is like how that's what I'm describing timeline. So this is how they will prepare the timeline. And also they will prepare a kind of communication plan, which just mean that, you know, for each phase, they need to update the basically status of the project and how things are going and, you know, many other things like, you know, project risks and all that stuff, what the team discovered and all. So that goes under communication plan. Okay, so that's what we discussed today. Yes. Okay, so that means the BA and the developers test everybody reports to the PM so he can be able to do the communication plan at the end of the day. No, so that is a wrong understanding. So when they prepare the communication is plan is basically like, you know, project managers responsible for, you know, planning and smooth delivery of the project. He doesn't have to do the project. He doesn't have to do the analysis job or development job or testing job. His job is just to plan the project, prepare that timeline and then make sure that everything happening according to the timeline. So if there is anything like going wrong, then reported to basically stakeholders are reported leadership that hey, we found team found this it will have this impact and then resolve that basically like issue or that risk. So before even the BA is there, they are a project manager already have these documents been created. Okay, so my question is, yeah, my question is the BA right when the BA is walking or doing getting their requirement stuff done. If anything goes wrong, who do they report so BA has his own timeline. For example, as I told you like in January 1st to end of February that is a BA timeline. So everything he have to does within that timeline if anything will happen, he will let the project manager know that hey, I'm not like able to get the meeting said I know I'm not do this this this reason and he like as a because his job is to make sure that within that two months. You know it has happened in the BA will plan that you know it should happen like you know within one and a half months or have like 15 days a wiggle room and if BA feels like at any point of time that you know that one and a half month mark is in jeopardy. In form the project manager and then project manager put to take it as a like a risk and start meeting. So all those like think that certainly happen. We will discuss that in more detail. But today I just wanted to you guys to have basically understanding that how the flow will come, you know that when the project is initiated and what is the team when it team mean and who is the first person who start on working on the project and what they do. And how they do it so basically project manager a role. That was basically like you know what we have discussed today. Okay. Thank you. Yeah. All right. So yeah, I will like you know and this conversation here and tomorrow we will start it from there. Thank you. Thank you. Thank you. All right. Thank you. Thank you so much. All right. Bye.