Project Management Masterclass ( Learn The Art of Project Management from Zero to a Hero )

1. Introduction to the Course: Welcome to the course and thank you for stopping by if you are looking forward to learn about the core essentials and fundamentals as a project manager, whether you're an entrepreneur or a freelancer, or an actual project engineer, project manager by profession, then this course is definitely for you as I'll be sharing with you my experience as a project manager in the field. Where are you learning core concepts and fundamentals that every single person who's going to take on a project should learn about in order to make sure that they're following the steps and not reinventing the wheel and getting things done in the proper fashion in order to ensure that their project is a success. If that sounds interesting to you. And if we're looking forward to taking you up, taking on a project, a learning the proper concepts and fundamentals to facilitate your journey. Then definitely this course for you and hope to see you in class. 2. Your Course Project : Your project for the course would be to break down the exact structure or the approximate structure, let's say for a project of your own, whether you want to create a website to one of their development application, or actually, I construct a small house, irrespectively, it's your own personal project. But as you go through the course, you will learn that all of them BY have common ground. And the project would be about you using the template, the outer be sharing with you. Consider it to be a courtesy, downplayed. Feel free to use that template to write down a list, the structure of your own project. Uh, once you are done, feel free to share it with other students as well and the community members within the course in order to make sure that we are spreading them all it and everyone is benefiting from the course. 3. Definition of A Project : So the first thing that we need to ask ourselves before learning of project management, how to manage projects, how to make sure that our project is a success and how to avoid failing our projects. What we need to understand, first of all, is what is a project? What makes a project? And it's what, It's a very simple concept. Wrap your head around if you think about it this way. By definition, a project is the use of resources and a structured sequence of events deliver a specific outcome. Let's replay that I got. A project is the use of resources and align sequence of operations, which means tasks, things that you have to do using these resources in order to deliver a specific outcome. Now let's explain this generic definition through the use of an example. Let's say you're writing a book is considered to be a project. Building a house is considered to be a project. Creating a website is considered to be a project. A changing the tires of your car is considered to be a project. Even writing a small article or creating your own CV is considered to be a project. So why all of them are projects? Well, today reasons all of them big choir, they use a fleece sources, whether time, money, effort, knowledge, and the list goes on. Plus a sequence of events, a sequence of actions, you, someone who is conducting or executing the project, then you must follow in order to make sure that we deliver that acquired outcome. Let's take baking a cake as an example. You will collect the resources. First of all, you define the project. I want to make a cake, baking a cake. This is the name of the project. Who's the owner of the project? Let's say yourself, you want to make your own Kagan's. In order to deliver that cake, you're going to list down the resources that you have, which can be added as flour, butter, me some equipment, let's say a queen Worker, Union, an album. You get electricity, you need water. So all of these are resources that you're going to arrange, properly sorted them out, utilize them to bake the cake. And the cake is going to be baking itself by itself. You're going to utilize these resources plus a series of actions that will deliver that gate for you. So you have listed down your resources, you have taken down all of the resources that you could possibly think of in order to ensure the delivery of the cake. Now the sequence of steps that you must follow to bake the cake, what would they think about it? You need to combine the eggs and butter of the flower and the water together for a certain period of time, then you're going to use that whipping cream equipment, just the blenders to blend all of them together. You're going to let it rest were a bit, add some salt, then you don't disrupt the Alban, this specific temperature. Wait for the temperature to be reached by the oven. Place that whole batter inside the oven. Just to make sure that, you know, once you have that blend of free sources sitting in that specific temperature, close the Alban. Then you're going to wait for a specific period of time, led the whole cake, bake, observe, monitor. Take a look at what's going on. Then you're going to be tasting the cages to make sure that you have the left forever, right flavor. Everything is quite aligned perfectly before we actually take it out of the album and prepared for your final presentation for the icing with the fruits and all that kind of stuff. So something as small as in baking a cake. If you take a look at it, you have a line, a lot of effort, resources, allocated, time, equipment, energy, money, preparation, manpower, and you arrange them in a specific order in order to deliver that cake. So a cake is considered to be a project and making a cake as a product of small-scale project. However, the same logic applies for small k project. That K is project small-scale. The same. 4. Understanding Project Management: So we've developed an idea or well understood the concept of a project. What does a project? Now in order to ensure that this project that we have, regardless of the time, the nature of the project, we want to ensure that this idea that we have or something that we need to create or do, we actually get it done? We need to manage these resources and we need to manage the sequence of steps to ensure the delivery of this project. And this is where the term project management comes into play. Sort of define the project. What is a project? Which is the allocation of resources and a sequence of events, operations to deliver a specific outcome. This is the project. Now, the project management is the chain of managerial steps and procedures to properly, at best, to utilize these resources for the successful delivery of a project. If we replay the previous video and you take a look at the example of baking a cake to a different chefs could bake the cake differently. One of them could do it faster than the other. One of them could do it with less resources than the other. One of them could save money on the process. Some of them, the other might be overusing the equipment that they have, but both of them will be able to deliver a cake, will give you that final product, which is a cake. So both of them we have successfully delivered the project, but one of them is a better project manager than the other line because one of them was able to use the resources at hand and effective, efficient way to ensure the successful delivery of the project. And this is where the whole field comes in. The field of project management comes into play. We are surrounded by projects, buildings, websites, stores, tweets, cafes, all of them. They are forms of projects. And you have people that are actually managing all of these things from the time of being an idea or a concept, then actual realization of that. And all of them, the follow up or the fall under the umbrella of project management. Which means the utilization of these resources and proper alignment of steps that will successfully deliver the desired outcome or the desired project. And the resources that we have. They can include manpower, time, money, and the list goes on. Think about what it takes to build the house. Now at this point, I just want to, I want you to pause this video for a second. Pause the video. Think about what it takes to actually build the house and tried to be as detailed as possible. Think about the plans, the drawings, the required manpower, the time, the cost, as much as possible. What are the things that come to mind in order to build a house? Think about it for a second. Now as you progress through the course, as you build up on your knowledge base, you are going to refine this idea. Or you'll find the project that we're building out. And by the time you get to the last part of the course, you will see this from a different perspective completely. At this point. You might have run them ideas about what it takes to build a house or what the proper sequence of events that you must follow in order to properly align the resources and the operations to build the house. It could be randomly arranged, but as you go through the course, you will put a frame for the proper sequencing. And under the proper allocation of the resources and operations to actually build a house, you will be able to develop that awareness as you proceed through the course. Now, in the following segment, I will explain to you why the field of project management is quite important. 5. Why is Project Management Important: So in the previous segment, we've talked about what does the project and what is project management, which is the proper use of the resources, the proper alignment of the steps in order to make sure that we have a successful project. And this current is a segment of the course we're going to look at the work, isn't such an important thing. Why do we have to properly manage all the resources? Well, why do we have to manage our sequence with it balanced and a great way, the best way possible to ensure the success of the project. First of all, a project needs resources and a clear or structured to be delivered. You kinda just simply utilize things for rapidly. And I'm just simply use resources in whatever way possible and whatever sequence that you feel like and you will, you will have to have a successful delivery of the alcohol. Again, the example of baking a cake, you cannot put leaves, whole batter, which is eggs, flour, and butter, without mixing blue and said they all went on and expect that a prompt to have by the end of the baking process. Why? Because it did not mix them in the right amounts are not properly and put them into white sequence so the project will not work. And that's why we need project management, because we have to use their resources in a way which works. So if we have a poorly managed projects, there are consequences to that. And the first thing that comes to mind is the waste of time, wasted, money, waste of manpower, and the poor of the poor delivery. Again, we've worked with a example. Let us say you have not followed the recipe that tried to do things and the way that you think it's fast without following the best practices. And then by mandibular process, you have found that you know what, It doesn't work. So what have we done in this case? You were wasted your resources, you've wasted your time. You wasted the allocation of resources and the right of sequence, completely gone two ways. You have to wait into random process. We do everything from scratch to get the job done. So in other words, you are, you have voices, everything. Wasted money, wasted effort, wasted the resources, wasted manpower. To redo the whole thing again from the beginning to get the same outcome. So the main reason for that because it was poorly managed in the first place. So that's why the project managing them is very important. Because it ensures that you use whatever data you have and the right way possible. So with not the proper project management flow, without the project management cycle, There's a huge risk that you might not be able to actually complete the project in the first place. So if you heard about project management standards of their white wine quantity tangent has been standardized because project managers throughout the world, throughout the code, over years and years, they have shared their best practices of things that do work, things that don't work, and their mistakes that you made, and the hiccups that came along with the way that it came into play in the progress of the project. It has been documented and the best practices have been documented as well. So project management that they think about it from my own experience. Ions, NO2 project managers alike, even though it, they have independent state project. Again, the example, maybe two shots that could be made that exact same take a webinar that one could do it in the fraction of the time. But the fraction of the resources for the fraction of effort with waves added results. And it's not something new or something quite surprising. It's possible. And the main reason for that is done. They have to properly use what they have and the best way possible to make sure got it. We are able to deliver the required logic. And this is in its purest form, project management. So and this is the basis of the course, the following segments, what we're going to be learning about those. We are going to go up all the phases of a project. What are the different milestones that any projects, your garden, the garden, regardless of the size, will undergo before it gets to completion. 6. Understanding The Phases of a Project : Welcome back. So in the previous segments, we can talk about what we've talked about the definition of a project. What is project management? What momentum is so important? And in this current second, we're going to learn about the five phases that a project will undergo from the moment that they can see all the way through the delivery of the project. Now, something broadly in the literature, project is under the broad term that you hear about between professionals other, they are working on a project that started a problem. They have finished the project. But every single product, regardless of the size, small crowd letters, medium-sized projects, all of them need to follow these five different phases. And phase number 1 for the project, which is the initiation and the conception of the project. 7. The Conception: So please number one, entity logic. It is the initiation and the conception of the project, which is the first phase. And in project will undergo working toward simply or was simply a vision or a concept that needs to be turned At chain. We have an idea, simply thinking about soft lighting that you want to do and then conceptualizing it. Then they give an example. Let's say you want to build a little bit and you have an idea of what it looks like and how that might be involved. How many storage would like the building to be? What are the different apartment types? We've got gross signal. The bedroom apartment where they want to build a house, townhouse, suburban house. So you have the idea of something that you would like to do. And another example would be building a website. So you have an idea that you want to build a website. So this is the conception stage where the project was married. At the same phase you have the initiation phase, all the conception, which is the process where you start to take actions based on that specific idea. And this involves the meetings, welcoming patients, people who own the project where they sit together and they discuss what we wanna do, what we want to have, what you want to deliver, what is the main goal of this project and what are the requirements to get into. So this is fading number one, which is the initiation and big conception of the project. And this involves sitting with me owners of the project, Let's say you are the owner or you're doing a project or working to deliver projects for someone, want to build a house for someone you want to build a website for someone. You sit with. Your discusses the idea, you discuss their requirements. What is the expected outcome from the project? What did they want to have you deliver? What are the key things that this project should achieve? What is the requirement that they have in mind or you have in mind? How do you know what this project is a success? So I'm in this phase involves a lot of conceptualization, sharing my ideas, sharing of requirements for documentation, contractual terms. Dependent on that, the project will our expectation with the client, if you are working for someone to deliberate their project, what are they holding you accountable for? What you should deliver to them? All of the documentation that comes along many technical drawings are shared with you that help you wrap your head around the concept of the have, the visual representation of the project that they have in mind a specific floor. Just simply brainstorming with her teammates before the actual execution of the project. So this says we have nothing planet Aleks. Simply sharing a little idea of the concept that conceptualization that I need documentation or technical requirements that your client or yourself, you might come across. That mean to kick start the process and today, Sure, That's your 18 to deliver it that project. Now, in the following phase, which is the planning phase, we have a different set of criteria or different set off the bat that would go to follow so well over the next video. 8. The P and the E Phases: Now the second phase for the product, which is a very critical phase of the product. And this is where you should allocate the pumps to mark time for the Ford being tired within the entire spectrum of the project delivery, 60%, 50 percent of the entire class patch should be done on planning the project properly before actual execution. You don't wanna get too excited to just jump started with process and some work on the project without vision above it, what you need and how are you going to use what you need to deliver that product. So the planning phase, which is the second phase of the project, key phase and the success of the project. Wherever sufficient time to be allocated to ensure that the delivery for the proper planning of the project and this phase would involve step-by-step breakdown of the works that he accomplish the project. This is what we call as the work breakdown structure or WBS. If you are a project manager, is this term, that is this flux. This is the ternary should be quite familiar with, which is the WBS work breakdown structure, where you simply break down all of the steps that you need in order to make sure that you have a successful delivery of the project. Again, with the example of making, can you do right now the resources that you need? What are steps? Step number one. All right. Can I said lever to get the flow graph? Step number three, mechanisms, we've got to step number 4 at the bottom, older sequence of steps. That means from the time you start a project, although in towards the final result, the delivery of the project, this should be as detailed as possible. And during this phase, the planning phase where you list now the structure of the project, the work needed to deliver the project. You are enrolling to actually calculate the required time and the budget, the amount of money that you need to fund the project. Because all projects the money to be developed. So I'm the moment they had been conceptualized or old, all the way to the actual delivery of the project. All projects, they need money at projects, they stop, stop when there's no more funding for the project. So that's why we've not proper estimation of the budget, the costs, what is needed, what is acquired. You are jeopardizing the success of your project. Not to mention as well, you need to keep in mind, you're in this phase, you need to estimate the timing of the money required budget for this case, resources, manpower, equipment. All of these things shouldn't be planned out before doing anything related to the project. So that's why when it comes to the project management cycle, the second phase, which is the planning phase, a very crucial step because it can either make or break a clock. If you have a poorly planned projects, you might wanna Ross a series of problems. Problem number one rule. You could run on a pointing for the project level funding. You overspend on one aspect of that Fraga. I'm younger, but another aspect of the project. You are understaffed. Your project needs, let's say at 200 and engineers, you have a 100 years working. So your overstressed in your staff, they're under-performing and you're not giving it to deliver. You all were running project that term over on in mediation when the project is staying more than 100 required time for delivering, your project should be completed or handed over to the client within the period of two years. For some reason, you automatic able to deliver within a year is your delivery or lives that we could five years. So you're running your project, you're consuming resources. You are simply verify your project down and you're expected to get any profit from your project. Most fun with that, your profit will be consumed. Because of all of these wastes, you have poorly managed platform in the first place. So now you have an idea about the importance of planning for the successful delivery of a product. Then again at another example where under Islamic of a project actually jeopardizes the success of a project. If you have, let's say we want to help building the building of a fillable. That's a tweet for sorting below. And you expect that everything is quite rotating. Care of the meat plans ready a grounding is ready to be flogged for both the House. And then you bring in all of the map already graded all the equipment in the exculpate or the equipment that you need to use, the raw materials, the electrical equivalence. Plumbing, if ate all the stuff that you need to build that hops and get them on site. And all of a sudden, it's kinda get licensing to actually begin works. And you have to file for an application for the licensing that was acquires between one to two months of the review process to get that approval, failed to allocate that period of time during the planning of the project. All of a sudden you have people were waiting for the worksite. You have equipment laying down a white worksites for a period of two months, completely unutilized, completely not use for a period of two months for safe off licensing. So many things play a role in the success of a project, and specifically in the planning of a project. Starting from the licensing, required, documentation, needed, manpower, time, resources, money, budget thing was financing, insurance, all of these things. Depending on the nature of the project, it could be more or less, shouldn't be accounted for it. Now, honestly, if you're planning on top of your projects, building a website, you don't need to secure it, the license for a flam. But if you have This building ability to secure the licensed for construction a lot. But all the little b are under the umbrella of what? You need to plan your project properly. And things could go wrong later on the lifecycle of the project if you poorly plan your broad leg from the get-go. So it is important to keep in mind that the second phase of the project is considered to be one of the most important phases of the life cycle of a project, which is the plan. We conceptualize our project. We have a clear idea on what is our project we've done around the planet. Everything is quite aligned with, have broken down all the Orcs needed to ensure that everything is quite taken care of. Everything is quite aligned from the get-go from day number 1 all the way to today, where we have a successful delivery of the project. We have allocated their resources, medical ward or are they acquired their quiet equipment under quite licensing bottleneck? They shouldn't the budget, the money, hold these things happening. Why? Planets? Now we can get this phase number three, which should be easy right now. Say is number two and above it quite well. Yeah. Well, yeah, lander project quite well. Not face number three, which is the execution shouldn't go down lower. During the execution phase. This is quiet, Let's say budget heavy because this is the time we're actually going to put the money to work, right? We are going to spend the money on the resources spent on me, manpower and the time. Utilize them, properly, manage them under the umbrella of effective project management to help you take the idea that you have planned for and start delivery of that. I did. So the start of the project realization as as the execution phase and ongoing phase till the project is completely delivered. You're going to spend the budget, spent the resources time demand our spending the time till the final delivery of the project. So this is an ongoing basis to actually get to the final end result and you deliver that product. Now, this phase may host to meet them the use of their resources. They use on the sequence of operations effectively and a systematic way during the execution. Tracking the liver works. This is very important as the goal above the process of buying stuff, getting manpower, spending time, spending effort. You're going to keep an eye on the progress of the project. Are the resources used in the way that shouldn't be used. Or we can progress in Asia, we shouldn't be progressing out. Let me give you an example. Let's say you know that the construction 9. Elaborating the Third Phase: Now the construction works for a building. Terms off to the Civil War. The symbol of the iron means that the columns, the slabs all over them, they need about six months to a year to default it up. And as you go above the view on the project, you are keeping on what sounds they sit in you like eight months so far are the troposphere did up there. Do you have a problem? So he started to investigate what is the problem and then you realize that you don't want lacking map. More people on the ground. Get them quickly. So you mobilize more people to work on the project and you resolve that problem and your project is on track. So during this phase, the execution phase, you have to keep in mind that it's an outgoing interface and you are going to track the progress of the project are multiple aspects. Time, we budget, the use of the resources, and in case of any problems, you are going to do some corrective measures. You're going to do some steps, let's say, to make sure that your product is back on track. So let's talk so far in terms of the phases of a project. So in phase number one, for a project that wouldn't be the initiation and the conceptualization phase of progress. I mean, the idea. It's a discussion that you're having with the owners on the project. They present to you the documentation that may have. They present to you the idea that they have the requirements. What are they looking forward for you to deliver? If you are working to deliver the product for that, or if you are working on your own projects, what are the key things that you need to achieve? Or to keep in mind? Make sure you get working on your project. One thing I need to go, okay, patients, the design and the calculations. Any specific things I should take into account? How will my project look like? What should you do? Well, RP success criterias that will, that will show me that you don't want your project to success. Now during that phase, at the core is made at meetings with the owners of the project, documentations, sharing wealth requirements and the contractual terms of things that you are obliged to follow, things that you are upward and should avoid. And it seemed to requirements, let's say you are not allowed to work from these hours to those hours. I ne sites limitation that you have multibeam offsite or in terms of a new licensing requirements, if you are working on a specific project that it would require some sort of transportation. So all of these, which are mainly not related to the project yet, but these are discussed at the beginning of a project. To help you frame your work's, help you wrap your head around the concept of project. What are you trying to achieve from working on this project? Now that's phase number one, initiation of sexualization of the project. Phase number two, as I've mentioned, which is the most important case as the planet, this is time required a little time. It's time dependent and you should give it the time require any kids at this point. Let's put it this way. A planning compared to the entire cost of the project is considerably low when compared to fixing a problem later on in the project. Because during the planning phase, you are simply putting everything together in the right sequence, taking into account the resources that you need an alignment that perfectly I'm just simply going through every single detail of the project from the licensing, time management, the resources man on the manpower required, the risks, all of those things and contractual obligation for say, all of them you are taking care of and you are simply just thinking about getting the work required for the project and the proper sequence written down. Clearly, I'm perfectly step number 1, 2, 3, 4, 5, 6. You are reviewing it with 15 minutes with your members or your company, with your managers, with your client. Or if you are working on your own projects, you are going through the details to microscopic levels. 10. The Birds Eye Skill: So the fourth phase of the project, which is the monitoring phase, which is a crucial phase to anticipate any problem I'm profoundly from happening at this current point in time, only be planning on deck. I'm the product is ongoing and the growth and the development of the product is taking place. You as someone managing the project, applying proper management skills, you should monitor the project and keep on line or the progress of the project just to make sure that everything goes aligned as per the plan. Because I'm going to just simply take your hands up the project and expect that things were resolved themselves, by themselves without any interference. Because things can go wrong easily or the project. And you could just simply go wrong. Having a properly successful delivery of a project to just simply implementing. Now, if people take any corrective measures or actions. And this phase, the monitoring phase of a project, It's an ongoing phase from day number belong. So they Acts the delivery of the project. You're going to continuously monitor the project. Probably assumption, the planning, the execution, all the way to the final state. And we're going to see this monitoring cycle is a continuous phase that involves key important aspects that could happen. Let's say highlighting any potential risks. You're going through the project and running, you have a natural hazard, start to rain. If you're working outside, I'm at a fire broke out, then you have to do some corrective measures, vacua, apply safety regulations. And we call granite damages file for insurance. If you have something real quick, cross product has been damaged and it's covered by insurance. So all of these things that shouldn't be accounted for during that phase. So if you're monitoring your project, you're not keeping an eye on your project. Things can easily go on. Let me give you another example. Let's say you're working on the project. You've bought a specific piece of equipment that used to be used. And a couple of months down the road, the supplier has an expected to deliver that equipment, tells you, You know, what? We're out of stock, where I'm not able to deliver as for our requirements. So what do you do in this case? You have to find out which supplier which might delay or more, depending on the nature of the project. But you have to take corrective actions to make sure that the project is delivered. Password requirements on time, things do happen. The lifecycle of the project is not just steady state where everything goes smoothly from a to Z. Things do happen easily being most the project managers out there, it will tell you I won't put it time he worked on a project and their project was jeopardized by external circumstances and aspects that they had to deal with on the spot. The willing to do so is by continuously monitoring project and prevent the risk by applying recognizers anticipated risks and try to avoid it. This is what a successful product manager. You will have to wait for things to go wrong, will anticipate things that might go wrong and try to apply corrective or preventive measures to push them to whisk away and make sure that your projects quite intact. And as you go up both through the process, any adjustments that you make, keep in mind that the planning phases has been done. The execution is all going and things went wrong for some reason or something popped out time, you'd like to adjust your work breakdown structure, the sequence of the status, or the allocation of the resources, you would like to deviate slightly from your plan based on Southern circumstances. This should be reflected back and be logged or the planning phase of the project. Let me explain to you how 11. Example From the Field: Let's say I'm working on construction of the building and I'm going to work to install and XJs your system and not the electrical works to that. Actually, he sees this, the aspirin, my lab, it will take me, let's say we must, as an example, to install the systems and two months to connect the electrical requirements for that system. However, as I wonder with the project and you have some licensing issues, some problems regarding to weather conditions, were not able to execute the task of the installation of the interface and systems within three months, four months. So in this case, I'm going to reflect back on the planning phase. I will mention both adjustment that I have made and the corrective measure that have done that had to be avoiding any problems during the lifecycle of the project. And instead of having the electrical work, let's say it's three months and we'll spend a bit more money getting more and more, more manpower, and having the work delivered into months. So I don't reduce the time required for the electrical works at all a one month because they require works with bed face the system external. So you can see that you are able to shift the balance between the resources at the structure of the works. As a cycle of the project is going on when they need arises in order to ensure the smooth delivery of the product. So that's why module 1, 3 of the project, that's continuous process, because we want to avoid the risk. We want to avoid things from happening that get into the way of the successful delivery of the product. So let's retrace all of the steps, all the Thetas so far. So we've covered phase number one, which is the initiation of a project coordinate conceptualization. Then you've got to face and number two, which is the corporate planning of the project, which is the most time-consuming part. Or they quite a bit of attention. Phase number three, which is the execution phase where you didn't have the delivery of the project, that the manifestation of a project taking place through the use of the resources and proper sequence of operations. Then you have the phase number 4, which is a continuous phase throughout the entire lifecycle of the project, which is the monitoring phase, we keep an eye on the progress of the project. The potential risks. They look at the trajectory of the project, check out the budget. Are we in paycheck? I hope they quote unquote. Okay, manpower. We say that timeline of the project, are we on track? I would lay it out. We should we, should we accelerated by adding more power, more resources, more manpower working on the project, If it that push me any adjustments are we expect from some sort of unforeseen circumstances, let's say a natural hazard or disaster that would accommodate. So all of these things are for monitoring. So at this point, we started a program plan that we execute the project by one, commit a problem on the project post two, which is the holes out or the Hathi cool effects. 12. The End of the Roller Coaster: The final phase of the project, which is the part of the project, which is the close out at an angle, which is the last phase of a project. You delivered a project. Now you'll go to the client. They say congratulations, congratulations, you go thumbs up, the project is done. Why don't align? Give you the key for some projects, let's say all of the required documentation that supports the delivery of the project. Again, the hidden look about how VK example of a cake. At this phase, you wouldn't be having at ready-made delivered, you're flying or shortly you in this case, if you aren't the one working on the project that you hold. Good. Now in this last phase of a project, it involves the Closing procedure to deliver the project to the client or the knot up works required? I didn't touch ups any given moment that your client has. Well, you find something which is missing, you want to have it up? I didn't tuck shop works. Something minor monument tweaks here and there before the final project is completely top. And this phase mainly involves quality checks and contractual requirements, if any, Let's say you have a working on product which is the construction of the building. And once you're done, you're going to ask the client for a site visit teacher, look at the works that we had done 48, we have finished up the project as per your requirements from day number one. Can you please send me your team to take look like the quality of the work that we have come so far. I didn't give you any comments. Can you provide us with your feedback and we'll do the corrective measures, too. Fulfilling these requirements, your client sends a team or personally go through the essay, worksite, I'll take a look at the project and it tells me, okay, can you fix that? This is aligned with the requirement. Can you adjust? Got so on. So you knew the words that the client will gives you the final close out of that fracturing documentation that you're going to be signing, that you don't want to go with the project. I'm done. So you're going to sign up those requirements with a client and everything is perfectly aligned and evil are completely off from working that project. And that project is considered to be finalize while the product is considered to be completely done and not faze me close out of phase of the project. It has two parts. The quality aspect or the client was taking a look at anything that he needs to fix before accepting the project as a handed over and the contractual requirements and that payment cards, Let's say the client was going to be painting the rest of the money that you owe is you wanted to add that the project we hope to collect that a mom so as not to face any connection between you and the project will be discontinues. Project is someone else, an owner, stake holder. You as a project manager at this phase, you're going to disengage from the project and you are going to deliver the project to be acquired report as well. If you are someone who has worked on the product for your own good, at this phase, your involvement with the product becomes less and less and less. Table. You are simply an observer where you are. You are a person taking a look at the project that you'd have completed. And Dole works out to be quite. So. These are the main phasors. To give you five main phases for any project, regardless size, a small brought a big project. Why dig a book? Building a website? Building a tower building ago, baking a cake. I don't know about this foreign work. Well fed up with the baking a cake example, but it's a very simplistic. They can project that all of us have worked on at 1 in time. All of them be undergoing these five phases, the initiation phase, what do you think of? Okay? But you want to pay, you plan for it by allocate the resources and tools and the sequence of events to actually bake a cake. 13. The 4 Pillars of Success and Starting with the First: So in this segment of the course, we're going to be learning about what are the key important pillars that make any project a success. And the first pillar for any successful project. It's team, the team members. Whenever you go to begin the journey of completing a project, that one of the first steps during the initiation stage of a project would be the assembly of a qualified t. Let's say you're going to encounter on a journey, we're going to be building a project. Constructing a building. Obviously you need a team of engineers, you need a team of electricians, plumbers, you need a team on the ground, me, a team in the office, people addressing the contracts. So all of these kind of aspects of the project that requires specialized manpower and you fall under the umbrella of assembling a team. So whenever you go into a project, it is very important that you have qualified team members. And this is a thorough process that requires some time and attention. When you are assembling your team, you have to keep in mind the requirements of the project in the first place. What are you trying to achieve? The desired outcome from the project? But at the same time, you have to keep in mind the cost, budget, the ability to outsource talents from different countries in case she needs to, or you need to delegate some of the work to different parts of the world. So all of these questions related to the assembly of the team shouldn't be addressed at the beginning of a project. Because you don't want to have a randomly assembled team without careful consideration to their talents, their abilities, their background or expertise when it comes to conducting similar projects. And it goes down the hall as you go about the execution phase. Mainly all of these hiccups or problems related to lack of talent, lack of professional experience within that specific domain. It could be quite affordable and it could delay you and it costs you a lot of time and money as you go about the project, especially if you find out that your team is not qualified to actually execute the job. So that would require you to stop the works. At the same time, tried to outsource required manpower and talent to execute the works. And during that time, it wouldn't be quite critical to the actual movement of the project and the progress. Think about it this way. As you go above the works, you realize you've got three or four team members. They have no idea what they're doing and their background does not match with the job requirements. They are actually causing a lot of mistakes during the progress of the project. So why would you do in this case, what's probably going to be firing those individuals, hiring someone else, but at the expense of the time and the cost of the project. So you don't want to end up in that position rather than you want to take your time, assembled the property and tried to have the same team go through the projects from a to Z. Because that will save you a problem as you go about the project as well. Because if you, even if you had the right talent midway the project, you will realize sometimes filling in the, let's say the information that you need to provide in a short period of time to new members. It could be quite costly and it's not sufficient and efficient. Nothing is worse than having a qualified team member to join an MIT project. Or towards the end of the closing phase of the project, where you have to fill them in on that information, tell them what they need to do until and help them catch up with all the things that they have missed from the initiation of a project. So having the proper team happening, having the proper manpower, The qualified talent, one of the essential pillars for a successful project. 14. The Second Pillar of Success : Now the second important resource actually is one of the most important resource, one of the most important resources, and it's quite an obvious one. You need the resources for the project. If you have a project and you don't have the time, you don't have the money, you don't have the manpower, we don't have the equipment or any other thing which falls under the umbrella of as we source, most probably you're going to end up not completing the project, abandoning the project, or the project might fail along the way, it had become one of those unfinished and businesses. And it's often quite seen. And the extreme sense where you have a building and halfway through the project, the owner of the building runs out of money to finish on the works, or the contractor doing the job is quite done it with the suppliers working on the project where they end up holding the works for an extended period of time with the hope that it gets some funding to move the project forward. So you don't want to end up being in that position. Rather than not, you want to have a careful plan, carefully plan and budget, and time-frame for the project. And if you recall from the previous segment of the course, it's one of the most important phases of the project, which is the planning phase. So with proper planning, you're able to allocate required budget, timeframe, manpower, equipment without causing you a penny other than the cost of your simply hiring the people to do so before executing the project and figuring out down the road that you have all these problems. So having the sufficient resources, having the properly allocated resources, It's a huge boost for the success of the project, even, even when things do not go quite smoothly during the progress of the project. So let's be quite straightforward. It's quite rare that you have a product go as smooth as flow in a smooth as it could possibly be without any hiccups along the way. That's quite impossible. No matter how much of a veteran of a project manager you are, how qualified you are. Things that do happen as you go about the progress of a project. And it's quite natural because there are a lot of things that you need to control. A lot of error that can happen, and human errors that could go wrong within the span of a project. So these resources that could help you fix these problems somehow. Let me give you an example. Let's say during the construction of a building, you notice that one of your team members or the engineers working with you, the bought the wrong piece of equipment to be installed in a house. Now if you have a specific budget for that specific equipment and you have no extra flow of cash or extra flow of resources to help you avoid that problem or by the correct piece of equipment. That would be quite problematic because you have an X amount of money that should go in a specific place for that project. And one of your team members put that amount in the wrong place so that you have a gap in your budget. You need to fix as soon as possible. So this one, this is one of the things when you are planning your project. Again, we cannot just simply emphasize this enough that the one of the most important phase of any project is the planning phase. Because all of these things are quite accounted for in the beginning. Whether the time, the risk of running out of cash flow for the project, financing the project, all of these things, they're quite accounted for in that beginning. Insurances, for example, if things go wrong, one of the equipment get damaged. So these resources, they provide you with a solid backup. If your project costs $1 million and you add resources worth $3 million, you are able to easily control all of the required resources, budgeting and cost and time. You can allocate more manpower. You could get more equipment that you need, that you can't substitute things that went wrong with that sufficient budget. So that's why it's very important during the planning phase that you have what we call as proper estimation. Because things could go wrong and he always keep a margin of error. What do you are budgeting? Taking a look at the cost and the expenses. So the second most important pillar for any successful project would be allocating the sufficient resources. 15. The Third Pillar of Success: The third, well, not the most, but one of the most important pillars were a successful project wouldn't be the quality of the works. Imagine you have your hand over a project to your client. Let's say you're designing a website. We're going to skip the example of the cake. And I'm quite sure that this point you're fed up with the example of habit or baking a cake. Let's say you are designing websites, we're building a website. And then you pass on the end results, the project to your client and you tell them you know what, here's the website and they go through a quality check. We want to check that your project that you have delivered to them matches their requirements and expectations. Because nothing is worse than having someone to work on a project and deliver the project as their own vision. With neglecting all of the requirements of the client needs a spur their own separate vision. So that's why a quality check is very important for any successful project. If things go wrong, especially on the quality wise, you could end up paying a lot of a mom of money, not mentioning the time waste, doing we work. Another great example would be buying a piece of equipment that you think works best for a specific project. And then once you give the product to your client, you hand them over in the last phase that closing out the telly, you know what? As per our requirements, we've taken a look at the specifications. This piece of equipment, that machine does not fit with our requirements. So we're I'm not going to pay you the rest of the amount of money for that specific project. We're now going to finish up your contractual obligations because you did not fulfill their requirements. So towards the end of the project, you end up getting stuck. Why? Because you have to resolve that problem. You bought the wrong piece of equipment even though it couldn't be way better than the client's expectations. But you have to keep in mind some clients and some projects they're quite delicate. And New York client, if you're working on this project for yourself, feel free to do whatever quality material or what whatever quality checks that you wanted to. It's your own project. So pillar would not be quiet to make it or break it for you if you're working on your own project. But I'm being specific with this pillar, the quality pillar because many problem that many students watching this course right now. The product that couldn't be working on that could be for someone else, would be working for a company that could be working for a client or they could be helping out a friend. And we have a specific outcome in mind and you're going to be delivering those projects for them. So in this case, quality is very important and you don't, you don't want to just simply complete the project with complete disregard to the quality of the work that you're doing. And you want to have a project that has been designed, executed, and delivered, SBIRT the proper specification requirements that you want or the client wants. So in this case, if you end up, I've seen this firsthand with many projects where it could be a very small project, very straightforward project. However, the company that you're working with or the individuals that you're working with on a project. They want to get things done quite too quickly and they want to profit from the project quite quickly. So they end up buying random equipment around them, supplies for them. If assume that this means the clients expectations. And surprisingly towards the end of the project where they want to hand over the project, they realized that the client does not want this. So they end up removing one of the half supplied or installed and buying exactly what the client has contractually blood. And guess what? Profit that they had in mind is gone. And most probably they ended up losing on that small project because of that specific mistake, the lack of quality. So one of the key important pillars following the resources and the team would be the quality of the works that you put in the project. 16. The Most Important Pillar of All : And to the most important pillar for any successful project, regardless of the size and the funding, the assembly of the team, the quality works, all that kind of stuff. You can put it on one end of the spectrum and the specific Pillar. It could either literally make your project a success or learn in this project. And that would be communication. Now if you want pause for a second, wonder, okay. Is communication such an important thing? Yes. 90 percent or 80 percent less than Sb. Fair enough. 80 percent of the projects, they do fail due to the lack of communication. Think about it this way. You are responsible of a series of tasks, your grade, your work breakdown structure one step at a time. And it's quite rare you'd be able to do the project yourself. Rather you need a team. You need to mobilize resources, manpower, and pass on the message to them. Every single member of your team should be quite familiar with what they need to do, how they need to do it, and when they should be able to do it, and when they should get it done. Now, if Bowl does not get passed to all of the team members in the same way that it shouldn't be. You'll end up having a progress that does not align with the plan which is in phase number to write. So it doesn't align with the plan. You have something which is completely off the design of the requirements. Simply because one of your team members failed to pass the message properly. And it's your job. Let's say you are a project manager or project owner and you weren't the one responsible for the project. You are the one to provide the umbrella of information and channel it and all the right directions where every single member to know exactly what they need to do and when they should get it done. And if you fail in that sense, your project will be on a trajectory for failure. So communication, it's a very critical step. And when I say communication, it can be anything. Verbal, written, meetings, agendas, e-mails, conference calls, all of the documentation. All of these are forms of communication. Let's say you walk into a meeting with all of your team members. You have a problem with the project and you are the project manager. And then you want to resolve that problem. So why he ends up doing all the documentation? You let's say speak a specific language. And some of your team members, they're not quite fluent with that language. And as far as you know, you are conveying yourself in a very articulate man are very straightforward. They understand what you're talking about for you. The point makes perfect sense. But for them they have no idea what you're talking about. The older thin and they're doing is they're holding their hand as if they know what you're talking about. And you leave the meeting with the expectation that the message has been quite properly delivered. To figure out, let's say two months, three months down the road, that you know what? That meeting was waste and they end up doing what they thought they need to be doing in the first place without the proper direction. So whose fault is it? That's the project manager's fault. The owner of the project, the one managing the product. And that's your fault because you failed to convey the proper message or failed to communicate with your team members properly. So that's why whenever you go into me and you want to make sure that whether it's an email at a conference call, you have proper meeting minutes have been documented, sometimes translated in different languages just to make sure that every single team member has received the required communication intact without any misconceptions, Let's say when it comes to passing on the requirements of the project. So communication, it's a very critical step. It's like the umbrella that manages all of the other pillars. Without communication, you will not be able to utilize your resources properly. You will not be able to conduct quality and check properly. You can love being able to communicate your needs to your team book properly. So with that communication, you are jeopardizing the risk of the project entirely. Now I would like to share something quite experienced myself working on various projects based on my expertise in the field because I worked in the oil and gas and the construction. And I've seen various ends of the spectrum when it comes to the project's lifecycle. And communication is mainly where all of the problems of any project arrives. I remember 1 in time wasn't meeting or I've seen on many points in time, multiple meeting ball of them, they shared the same Jewish, let's say. You end up with members from various countries they wanna go, they're assembled to sit down and discuss a problem for a common project. And let's say, and the visual a is communicating to individual B. And you have C and D and Z, and all of them, they're sitting on the table. All of them, they had their own view of the project. And all of them they have their own interpretation of that specific problem. And the main goal would be to leave that meeting hall with a unanimous decision, a unanimous view of how how that problem shouldn't be resolved. Now within the meeting, you can share your own expectations, your team member, they could share their own findings. And it ends up to a point where all of the team members should have an aligned view of the problem and how it shouldn't be resolved. And I've seen that multiple times where you share your own insights on the project and your team member shares his insights on the project. And you end up what? Nodding your heads. All of you got the idea, all of the gut, the main point of the project for simply to leave and exit the meeting room to end up repeating the same critical mistake that you want to avoid with that project and the first place. And what was the main problem? What's the reason for that? Was the lack of communication. It was the lack of communication, the findings of the meeting, the agenda of the meeting, the main resolution from the meeting was not communicated properly following the meeting to all the members of the meeting. Because frankly speaking, when you enter a meeting room with 20 individuals, it's quite rare that all of them require focusing and concentrating on exactly what needs to be delivered. However, individuals tend to concentrate when they become quite obliged to do so. And that would be when you formalize the communication. And everyone is responsible and quite as held accountable for their end of the project to ensure that, you know what, they acknowledge their problem. They are fixing the problem, and they are committed to resolve the problem as part of a team. And all of that is done through proper communication. 17. The Failure of Projects and the Reasons behind them: So we've talked about what are the key important pillars for the successful project. Now in this segment, we're going to be learning about what makes a project fail. These are key things to keep in mind if you're going through a project that you should avoid at all times because they have been proven throughout the history of projects from various project managers, even within standardised project management certifications that you know what, you should be avoiding these problems. Not directly bit. Let's say you're not been directly told to avoid them, but you should avoid them. Because if you look on them, there are catastrophic. They aren't going to destroying whatever project that you have. And these are the key things that you should avoid at every single phase of the project, whether you are, let's say during the concept phase or the visualization phase. Or you are in the planning execution, you are in the monitoring phase, you are in the close up phase, all of them. You should avoid these things just to make sure that your project goes smoothly. And the first thing we need to take a look at would be the poor management. If you're not qualified to one-off project where you have no idea how to manage your manpower, your time, the money for a project in the documentation. Step aside and have someone else do it and you can support them or ask for help. Have someone's support you on the project. Sometimes you can have 32 for product managers working on the project. And they are supporting each other where every single one of them is taking a piece of the project. If you think it's quite too much, you're not able to manage it properly. You're not going to be confident about it. Make sure that you are preparing yourself before you go into the journey of taking on a project. Because poor management of manpower time, Monte documentation, contractual obligations that will end up ruining the progress of the project and groaning the entire project regardless of the size of the project, small projects, project, all of them default the same phases, the same cycle. And if you've properly take care at every single cycle, you would not be having any problem going about the process. So in this case, let's say you have a project in front of you, and it's up to you to accept the project. Make sure that you have learned how to manage a project, how to manage your resources, your time, your manpower and documentation, or at least you're able to get the support they need in order to take on that job and execute the project. And start small, start with small projects first and build your way up to bigger projects. What, why is that a recommendation or it's just quite strong advice. Because on small projects, on if things go wrong, usually they're not cost heavy and they can be quite rectified easily without much of an impact on the budget. Let's say out of product just like a $100 thousand compared to $10 million. I worked on projects worth millions of Euros. And that was that was quite heavy because any problem would reflect quite heavily on the progress of the project and could cost you a lot if you don't take quite careful consideration for the process. So on a small project, if things go wrong, you can deal with it with confidence. And in case go south and go south completely. If things go south and completely out of the window. Worst-case scenario, you have just simply say lost dot-product that didn't work out well. We can have someone else work on it without much damage being done. But on a bigger scale projects, you have contractual obligations. You have things that you need to fulfill. And you're going to just simply dust yourself off as if we did that work on the project. So that's why start small. Build your management skills, building abilities to manage the resources, the time, the manpower, and the document patient on the project, because poor management will definitely do your project. 18. A Critical Mistake that must be Avoided: And this mistake I've seen even veteran project managers fall into and it's very important to highlight and give it some sufficient attention, which is the lack of contractual flattery. Let's say working on the project during the initial phase of the project, you are given a set of documentation. Were there during the planning phase, where are they in the conceptualization phase, you'll be sitting with the client, let's say if you're doing a project for someone else and there'll be handing you over a series of documents defines the project. What is the scope of the project? Durations, expectations, specifications, time required contractual obligations, penalties if things go wrong and that payment terms. And the delivery phase, let's say you take on the project. For some reason you do not go through the contractual requirements properly. You will run into running or you increase the chances are fronting into multiple problems which couldn't be. First of all, you might overlook that acquired and delivery date for project. Let's say you're planning a project can be delivered in two years on, for some reason, you overlook that piece of information and you're going to be delivering it into years and six months. And then another clause inside your contract, it says, if you over one year project, you end up paying from your own pocket for the funding of the project, let's say, or you'd be losing a percentage from your own payments towards down to the project. And without proper, properly acknowledging that part of the project as a goal element during that and you've over phase, you know what, it's not. Okay. Here you go, client. Here's the project, getting my money and they tell you, you know what? Well, as for the contract, you delay this were a period of six months. So you were entitled to deduct a specific amount from the funding on the project, courts on the payment of the project. So in this case, a small overlook for the contract costs you a lot towards the end of a project. Also in terms of the payment terms, sometimes in large, large projects, you have multiple payment, let's say paying timespans as you go through milestones, if you finish a specific part of a project, let's say the project is 15%, then you get a specific amount of money, 50 percent bone a specific amount of money. I'm George Dan. You get the rest of the month without clear indication about the payment terms. Or if you having no idea about the payment terms, you might jeopardize the proper planning of the project or the funding of the project. Because you might be expecting that once you get payment from the client, you'll be able to pay for other stuff within the project and then add up some profit on that without the proper knowledge of what's required inside the contract. You're on into the problem of either underestimating or over estimating some of the works without having the proper funding off the works. And you couldn't be having multiple projects back-to-back, one of them would win the contract. I would say that that the client is going to be paying you wouldn't six months of defining overlook project. And you have a project going starting your atlas and then next month after the handing over of the first one. So you end up with five months having no cash-flow to help you with the project we cannot pay you. A team member is going to pay yourself or the project. Why? Because you overlook that piece of information. And most importantly, you have two things to keep in mind me go about the contractual obligations of a project. The penalties and the restrictions. Look at the penalties first. If you have a specific problem within a project, sometimes the client has to pay to fix that problem. Or if you aren't the one to cause that problem, you shouldn't be paying it from your own pocket. Yes. Penalties, needs. And within project, even large-scale projects, you'll run into the problem of causing some damage and you have to pay up for that damage. Let's say you broke something on site, the client gave you access to a specific area or you cause damage to another area, or you're ruined something with them, the client's environment that you shouldn't be involved with in the first place that happens. Let me give an example. Let's say you're working in the building of the client wants it to fix a specific apartment, and you end up ruining two apartments on the same flat, then you have to fix for that damage. You have to fix that. These things that you haven't broken down from your own pocket to rectify any problems. And it would be clearly mentioned with them that project. Also, let's say you are delaying the client for no apparent reason. They might they might show you for what's called as liquidated damage, which is simply they will estimate the potential cost of the damage of such a delay and they will charge you for it. So these are things that you should keep in mind because they can help you frame the planning phase of the project and avoid potential problems in the future. Also, you need to keep in mind the restrictions. Some projects, they are remote sites. You need some access, you need some bolts, you need some licensing to do the works, which would take months to secure in the first place. So with not being mined, with assumed that you are good to go on the project. And the first thing you go to, happy you'll be hitting a wall that you don't want to kinda start the work. Your team has to be on hold to get the proper licensing and to be able to mobilize your team. Now I'm giving you various examples from various occasions or various projects that will help you understand the importance of the contractual clarity for a project. So with the lack of the contractual insight and that insight, you are taking on a huge risk that might cost you a lot towards the project's journey. In a huge corporate, the even have departments that are called the contracts department. Their sole purpose is to read the documents and take a look under risks and things that you need to highlight or avoid before even taking on a project. Because sometimes once you were asking for the financing of the project, eat some support on the project. The first thing that people would take a look at widely contractual obligations, or are we going to be investing in words, the risk we're taking? So with, with that, Let's say contractual insight and clarity. It's like you're driving with your eyes blindfolded. And before you know what, you don't want to end up hitting a wall. And even that project managers, the run into these problems even in the smallest fine detail. And small clause here, a small fine print there. So the contractual awareness is very important for the success of the project without that in mind. Without that in mind, yeah, I'm not jeopardizing the entire success of the project. Look at the penalties first. And if you have a specific a problem within a project, sometimes the client has to pay to fix that problem. Or if you aren't belong to cause that problem, you should be paying it from your own pocket. Yes. Penalties, they do exist. And within project, even large-scale projects, you'll run into the problem of causing some damage and you have to pay up for that damage. Let's say you broke sampling on-site, that client gave you access to a specific area or you cause damage to another area or your rule in something within the client's environment that you shouldn't be involved with in the first place then happens. Let me give an example. Let's say you're working in a building and the client wants her to fix a specific apartment, and you end up running two apartments on the same flat, then you have to fix for that damage. We have to fix that. These things that you haven't broken down from your own pockets to rectify the problem. And that would be clearly mentioned with them that project also let say you are delaying the client for no reason that you might you might showed you for what's called as liquidated damage, which is simply they will estimate the potential costs of the damage of such a delay and they will charge you for it. So these are things that you should keep in mind because they can help you frame the planning phase of the project and avoid potential problems and the future. Also, you need to keep in mind the restrictions. Some projects, they are remote sites. You need some access, you need some bolts, you need some licensing to do the works, which would take months to secure in the first place. So with not being in mind with assumed that you are good to go on the project. And the first thing you've got to happy it'll be hearing a law that you don't want to kind of start the work, your team has to be on hold. Again, the proper licensing and to be able to mobilize your team. Now I'm giving you vagus example in from various occasions or various projects that will help you understand the importance of the contractual clarity for a project. So with the lack of the contractual insight and that insight, you are taking on a huge risk that might cost you a lot towards the project's journey. And a huge corporate, the even have departments that are called the contracts department. Their sole purpose is to read the documents and take a look under risks and things that you need to highlight or avoid before even taking on a project. Because sometimes once you were asking for the financing called the product, eat some support on the project. And first thing that people would take a look out widely contractual obligations swore, are we going to be investing in? What was the risk we're taking? So with, with that, Let's say contractually insight, clarity. It's like you're driving with your eyes blindfolded. And before you know what, you don't want to end up hitting a wall. And even that product managers, they run into these problems even on the smallest, finest detail. And small clause here, a small fine print there. So the contractual awareness is very important for the success of the project. Without that in mind. Without that in mind, you have not jeopardizing the entire success of your project. 19. The Underdog that ruins Projects: And most probably you saw this coming. Poor communication. If you're having a project, poor communication could destroy the entire progress of the project. For me personally, one of the most important, if not the most important aspect of the project, would be proper communication because it could save you a lot. And I'm talking about this from personal experience because I've taken on projects which are worth millions. And they went by smoothly without a headache. And I've taken on smaller projects, not caused me a bigger attic compared to the bigger projects. Why? Because of this specific aspect, which is the communication. If you have a team and you have no idea how to communicate with them, or you're holding pointless meetings. There's no track record of the required obligation of the things to look forward to as you go about the project, or more or less, not more importantly, but if you do have linguistic barriers within your team members and there's no way to over reverse those problems, then communication would be an obstacle that you need to overcome because we have done the proper communications came without the proper communication line. You are not going to pass on the message whether you have a progress report coming up or you're going to have a meeting and we have a discussion or a problem popped up and you need to resolve. You are able to communicate with the team members to solve or resolve that problem. So poor communication, it could be the terminal for the entire success of the project. Let, let, let me, let me pass all the idea even more clearly, a different way. Let's say you have a brilliant team members, all of them, they share your same view, the same vision, most probably new intellectual work of such individuals. They are able to pick up the information on the go, you get the able they're able to foresee the problems. They are always on the same page with you. No matter what is the size of the project, they are able to anticipate the problems, resolve the problems, and they always able to absorb whatever inside that you have regarding a project. Can you imagine working with such individuals? It wouldn't be a breeze. You don't have to spend much on communication. But no, I'm not going to be spending effort time and wasting papers or reports wasting time rafting email. Why? Because all of them that are on the same page and they are able to pick up the communication line that you have drawn and a great way and they're able to translate it and execute the required tasks. Me. And this is the thing, what do you need? And this is such a team that you need to build. And with poor communication, he couldn't have brilliant minds working on a project, but they're not working together on a project. And one individual wants solo player would never be enough to complete a project no matter how qualified you are, no matter how smart you are, you always need the support of individuals to help you progress during your journey as a project manager or a project engineer or someone working on a project personally, you need to have that required amount, which is proper communication. 20. The Sucess of the Project: So in this segment of the course, we're going to be taking a look at what makes a project a success. And the previous segment we'll talk about the things that make a project fail. But in this current section, we'll take a look at what makes a project a success actually. So once you've gotten to a point where you realize that your project is actually complete. There's nothing left over to do the last phase of the project. The closing out phase is complete. It's completed. The quality check has been conducted. You've gotten all the outcome of the project as per expectations, whether it's your own expectations or a client's expectations, the project is delivered as per the required specifications, then it gets to a point where you are ready to just simply let your hands off that project. And a Sydney, I acknowledge the fact that you know what? It's, the success of the project has been completed. Now quite often you find out project managers, or let's say people who are interested in product management and they want to take on a project. Sometimes they leave the project quite too early and they end up doing a couple of mistakes in the process that might cause the last minute hiccup in the project. Let me give you an example. Sometimes when you're having a project or working with a client, and it gets to a point where you want to pass on the project to the client. There are a sequence of stuff that you need to follow. As I mentioned on the previous segments, we have to look up the contractual obligations, the payment terms, any penalties, and induce that you have to fulfill before actually acknowledging that the project is completed. Because within the life cycle of a project, there are things related to the project and which are beyond the actual scope of works. And these things that could be contractual, They could be related to the team that you're working with. It could be work related to the company that you're working on the project for. These things, they're not formalities, but they are part of the project that are not directly involved with them, the project. To simplify the idea further, let's say you are building a building, the construction phase, everything except the building is up and running, and all the equipment, all the works, the civil, electrical, mechanical, everything is just simply completely done within that project. From a work breakdown structure point of view. But It's not ready for handing over to the client yet. Why? For multiple reasons. First of all, the client did not conduct the quality check. The client did not provide the required payments. The client is quite occupied and doesn't have sufficient time to actually go in and do the final construction to receive the project. Because during the final phase of the project, there shouldn't be some legal, contractual documentations, even for the handing over that simply states that you are no longer liable for anything related to the project. And at that point, only when the project is complete, the product is functional. Quality checks have been made. The part has been delivered as per the specs, the client has checked it, you have passed on the details. And then at that specific point, you can call it a success where the idea has been realized. There's a realization of the idea and it's complete and it's functioning and it has been accepted by the poor. It is going to be receiving that project because you don't want to have, let's say a couple of months down the road, something go wrong on the project and you are the one held liable for it, whether it's your own personal project or someone else's project. Because there's a sequence for the handing over to the client, for giving the client to accept the project as their own and taking the responsibility with it. Once you get to that point, you can just simply observe that the project has been completed. There's nothing left from your end to do at a specific point, you are good to go to transition to an another project without looking backwards on that previous one. 21. Wrapping Up: Great job on the successful completion of the course. And I truly hope that you found the course beneficial and added some sort of extra knowledge to your own base of knowledge, whether you are a project manager or a recent graduate or someone within the fields, always good to know how things are done. And this is what we do within our academy. Feel free to take a look at my profile description for all the courses related to various fields drawn from years upon years of expertise. And don't forget to follow us at various platforms, whether on YouTube, you can take a look at my channel, which is the APA swimmers, Our academies channel. And as the CEO of the elite education academy of love to have you join the community as well and feel free to sign up for the latest updates and courses that are targeting core industry practices. It's been a pleasure having you on the course and feel free to follow the profile as well to stay tuned for the latest upcoming courses.