Project quality management why are we doing any project the project that we are doing is because of the requirements that we have received from the stakeholders from the sponsors or from the business. The best definition for quality is is what they we should deliver what they have, what they have actually thought of, what was their expectation, we need to deliver the requirements. So, it includes the processes and activities of the performing organization, the organization that you are in that determined quality policy, the objective of the quality, the responsibilities on the to the project, that who will be doing what, so that the project will be satisfied the need for which it was undertaken. Understanding the requirements is very important that is the only way to make sure that we will able to deliver the requirements and that is the quality for the project. The question here is whether we should do it or we should not do it.

So the answer is very important. Quality is not an standalone process. First of all it is part of an organization. So, if your organization is quality oriented, you will definitely be doing it. If your organization is not quality oriented and they are not they do not believe in ready to spend on quality. You might face some challenges.

I remember attending a session while I was doing a supply chain certification. And in that Professor actually explained that why the quality is technically free, the quality is free, whatever you are spending is technically you are not spending on it and at the end It is free. So that's our question that I'm leaving it for leaving for you to Ireland to prove equality is free. The most difficult process in most companies as most companies are without these processes or either we are not dealing with these processes, specifically the organizations or the project managers who are in services and in a project manager or an IT consulting the quality implementation is a little bit different than what you usually see in constants of construction, where what you see in terms of the manufacturing organization, yes, it is challenging, but this is what we are supposed to do.

This is what our This is the one of the role for us as a project managers to deliver project quality management also support continuous process improvement. Not only the project needs to be needs to deliver the requirement, but we As a project manager and a project management team or as a project the whole we should be working on process improvement and continuous improvement we need to be better than our yesterday's session. What we are today should be better than should be better than what we were doing yesterday. I was going through some motivational speakers and then example he quoted. I want to quote here it is not degrading anything or disgracing anything it is just an example. A difference between human and a donkey.

Donkey was a donkey 10,000 years ago, and he will remain as a donkey after 10,000 years we as a human I've moved from those ages of stone age's to the industry multiple industrial revolutions and to now industry four oh which is about AI and robotics, we are supposed to get better about today should be better than yesterday. This is a quality we should be investing not in the project quality, but the organization quality and at the day and our own quality. So, we need to focus and see what kind of questions would come here and that is the process that is that could be related to the project quality and the organization quality and how they both remain related together. So, what is an accepted quality? The most important question that we need to answer we need to understand before getting into the planning of the quality perception in both an iPhone and other mobile tools even with better and more functions, better memory, better hardware better more function, we many of us are not willing to pay the price tag of iPhone.

Why is that quality management exercise which will help you getting the deliverables accepted, this is the quality that they have built. This is the ecosystem that they have built that they established the quality of the product, way back in 2007 and even back in 1998 and even back when they have Macs and the the first lab computers they had established that quality and from then still now they are taking that premium prices. So we can say quality is important with the quality delivery client satisfaction is guaranteed. On the other hand, You might need to compensate your client had this will concrete the cost or the cost of quality something we will look into it. So if you don't spend the cost, if you don't spend to improve the quality of the processes and the quality of the project deliverable as part of the project, you might be spending money at the after the project is delivered based on the issues that you might face.

We do not want to spend money after the project is delivered because it is not only money, it is about rapport, it is about the loyalty It is about so many negative things. So we here in this knowledge area, we would be identifying things and processes and spaces and events where we should be putting us putting an efforts to improve the quality. This is the general introduction for the project quality management. We'll see you in the next session. Thank you very much