Search

Stakeholder Management in Long Duration Projects - Project Management

If you are working in project management, you know that a key to success is to manage the stakeholders involved. There are articles, webinars, and books about how to successfully understand the science around it. In many cases, you know that you will work with many stakeholders through the years because there are many projects in common, but what if the project was one and the changes came from the roles or even the stakeholders involved?Suppose you have a service contract management with company ABC that is due to last at least five years. So, do I have the same approach as it was a one or two-year project? And here comes the funny part, yes or no.STAKEHOLDERS MANAGEMENT ACCORDING TO PMIChapter 13 of the PMBOK® defines the Project Stakeholder Management as “…the processes required to identify the people, groups, or organizations that could impact or be impacted by the project, to analyze stakeholders expectations and their impact on the project, and to develop appropriate stakeholder management strategies for effectively engaging stakeholders in project decisions and execution…”. I bring all the definition so you can see the words involved in it, identify – expectations – impact – engaging. Those are the keys to success.According to the PMBOK®, the four processes in the stakeholder management are identifying the stakeholders and their planning, managing and monitoring their engagement in the project attributes. If you see the stakeholder’s management tools and techniques that are set to use in these processes, you can divide them into two main segments, the analytical and the communicational.The Driving process :  For a better Stakeholder ManagementIn both cases, only expertise, common sense and soft skills will guide you and even then, you will probably make a mistake in some moment. Don´t worry, because mistakes are expertise for the future and, believe me, everybody makes mistakes. (That´s part of the risk management)GET A LEVERAGE BY UNDERSTANDING THE ROLESPart of being an effective Project Manager is known for which strings to pull and the ones you must let go. That knowledge comes from listening, seeing and analyzing the non-spoken words in meetings. Just like when in a relationship someone does all the taking but when it comes to decisions always look for the approval of others that haven't said a word, that's the one in charge but probably is not interested in the issue.So, how can I know the level of power, interest, influence or impact of each stakeholder? Do I use the force?How do you analyse your Stakeholder?The first is obvious, talk to people that have been involved in previous projects and try to know the stakeholders involved in the project. You know a guy from another company that worked there? Buy him some coffee and let him explain to you who is who in the company.Or better, some guys in your office have worked there before. Well, let's gather information on which people involved will have more impact on the project, or if someone needs to be informed about every change of scope, etc.You will probably expect that a CEO will have more power than a Manager, so that will be a good approach.However, that's not the case of influence. It could happen that the CEO doesn't know what you will do because that’s not his/her area of expertise, so the manager makes all the decisions and has more influence on the project.Another hint will be clarified in time if you see an attitude from other people involved to always pass all the big decisions to someone specific.If you have the opportunity, during the first meeting when you are developing the scope of the project try to establish how the communication processes will be. There you will see people that want to be informed, the ones that have the final voice, some just need to check on them from time to time and the people you are going to work through the entire project and need to actively be engaged.As you may notice, each one is just an example of common sense that use the communication processes to figure out the data you need to analyze and establish the role of the stakeholders involved in the project. If you know who is who in your project, you will have a leverage.DEVELOP AN AGILE APPROACH ON ROLES OF EVERYONE IN THE PROJECTSo, what you need to keep doing after the project start with the stakeholder’s management?I believe that success in this area came from three things:Knowing rolesHandling expectationsCommunicating effectivelyThese three represents the main questions Who? What? How?Who? You need to know who is who in your project. Some people are there just for the champagne on the podium and some are because they care, you must know which one is relevant.What? The reason many projects fails is that the scope of the project does not reflect the expectations of the stakeholders. You need to know how to handle the expectations and try to be completely clear about them, and if it is written in a document better. There is an article from the editor of knowledgeHut that give you 8 tips on how to handle it effectively.How? You need to know the type of communication you need to use in each case. Maybe is in a meeting, or by an official document, even drinking coffee, you need to understand the moment and the way to do it. For instance, if some parts are delivered with delay and it implies a financial hit to the project it's better to talk in private first and deliver the news, then write an official document. Communicate effectively.When you are working on projects that will have an extended duration you need to know that the roles will change. As certain as the sun will rise tomorrow, people will get in and out of the project or even of the company. I am a faithful admirer of the waterfall, but in the world, we are living, every information is just a stone’s throw away; you need to develop an agile approach in many things, even in this. Some will change roles within the project, maybe the project leader will become a manager and his interested will change with his power, maybe some guy has an opportunity closer to where he grew up, it doesn't matter, in a project that lasts so long change will come.There are things you need to keep doing along the project´s run:Be informed by external references:You need to be informed of all possible changes that will affect your project. Make alerts in google news or read papers, it doesn't matter, you need to stay ahead of the game. For instance, if you are working with the federal government and a scandal get to the news, you should be aware that many people will probably change, be prepared and try to follow any information.Gather information from people:If you don't like diplomacy and the importance of it, I truly advise you to see Game of Thrones. You don't need to like all the people involved, but you can make them inform, warn or advise you. Try to get ahead of the game and gather information about the new people involved or the new roles that will change. Being a Project Manager is not easy and will always require the extra mile to diminish the possibilities that some event make the project fail.Effectively archive documents:I know that it sounds absurd, but many Project Managers fail in this. If you see that some guy, that you don't know, is making all the changes when you read the history in the reply of the last emails, then this guy has influence-power in the project.Make less but effective meetings:It is absurd the amount of time we waste in nonsense meetings, so make them count and anyone involved in the project will try to be there. In them, you will update the roles of each stakeholder. Prepare meetings and give with a couple of days before so everybody knows all that will be discussed in them, try to establish who will be attending. “If you book them, they will come” Wayne Worlds 2.LONG TIME PROJECTS STAKEHOLDER´S RELATIONSHIPSMany of the success involved in getting a good relationship with the stakeholders in long projects is based on handling the expectations. Notice that you can develop a relationship of friends or you don't see them again when the project finish, but I will try to explain how to achieve good relationships, that will help you get successful project by managing expectations.Building  a great AllianceRemember when you were a kid and you will open Christmas presents? After you did an amazing letter to Santa where you describe that you want the Lego´s Falcon Millennium, there were three choices:You get the Falcon Millennium toy, not the Lego. You are getting something similar but not what you asked.You get the Lego´s Falcon Millennium. Yes, yes. Exactly what I asked.You get the USS-Enterprise. Not even close.The same happens with the expectations in a project with the possibility to see all the process from the letter, the elf determined the possibilities (if you were good or bad), the assembling, the package and delivering. So, if you see something strange you can put a red flag.That's what happens in real life. The things the stakeholders want maybe are not possible. Your client wants the project to be built in three months, your boss wants 2% of cost reduction or the subcontractor established that he will not start until all equipment is in place. These are common things, many of them need to be established when making the scope of the project, but you need to keep all of them aware of the reality of the project. Don´t accept any request if it is not the reality of the project.Some of them will bring discussions and will mean roughness in the relationship but is better to bring people down to earth from two feet that bring them at 5.000.In the paper written by Ernest Baker in 2012 “Planning effective stakeholder management strategies to do the same thing”, he mentions tools for setting and managing expectations.“…Stating the success criteria (project objectives) in the project charter.Defining what is in and out of scope in the project scope statement.Defining and getting agreement on the project deliverables documented in the WBS.Creating and sharing the project schedule or release burndown charts.Documenting who on the project team does what in a responsibility assignment matrix (RAM) or RACI chart.Creating and using a communication planning table to show how stakeholders will be kept in the loop for project information.Creating and posting project dashboards for the PMO or senior leadership.Creating, leveraging, and using project subsidiary management plans to handle all the processes necessary to define and manage the various parts of the project. These sets of guidelines, or rulebooks, list the “how's” to do the various project management processes.Conducting project kickoff meetings to publically state project objectives and set stakeholder expectations.I believed that it is also significant to have a documented change requested process, so any change made from the initial scope needs to be understood (with all the implications of it) and accepted by the stakeholder´s initially established as the ones to possibly do it. Cause, in many opportunities, you will need to change the reality to meet the expectation of some stakeholders, but need to keep track of anything that will mean a change in time, quality or cost.If you keep the expectations and project reality closed to each other, you will have good relationships during the project´s run. once it is finished, you will decide which  relations are worth keeping and those who don't. It will be because you see an opportunity in the future, because you liked them and have affinities or because you will still work with him.You need to understand that keeping track on relationships in this hi-tech world is as easy as writing congratulations on their birthday or an email once every year. Most people want to feel that meant for help in the progression of someone as if they really do than shame on you for not doing it.CONCLUSIONMany of the “magic” of an effective stakeholder management comes knowing the roles, handling expectations and being an effective communicator. It means to gather information, a bit of diplomacy, analyze information and a lot of common sense (not so common after all). But in long time projects, it is all about keeping the gap between reality and expectations the closest as possible.
Rated 4.0/5 based on 2 customer reviews

Stakeholder Management in Long Duration Projects - Project Management

341
  • by Victor Casal
  • 23rd Aug, 2018
  • Last updated on 11th Dec, 2018
  • 5 mins read
Stakeholder Management in Long Duration Projects - Project Management

If you are working in project management, you know that a key to success is to manage the stakeholders involved. There are articles, webinars, and books about how to successfully understand the science around it. In many cases, you know that you will work with many stakeholders through the years because there are many projects in common, but what if the project was one and the changes came from the roles or even the stakeholders involved?

Suppose you have a service contract management with company ABC that is due to last at least five years. So, do I have the same approach as it was a one or two-year project? And here comes the funny part, yes or no.

STAKEHOLDERS MANAGEMENT ACCORDING TO PMI

Chapter 13 of the PMBOK® defines the Project Stakeholder Management as “…the processes required to identify the people, groups, or organizations that could impact or be impacted by the project, to analyze stakeholders expectations and their impact on the project, and to develop appropriate stakeholder management strategies for effectively engaging stakeholders in project decisions and execution…”. I bring all the definition so you can see the words involved in it, identify – expectations – impact – engaging. Those are the keys to success.
Stakeholder managementAccording to the PMBOK®, the four processes in the stakeholder management are identifying the stakeholders and their planning, managing and monitoring their engagement in the project attributes. If you see the stakeholder’s management tools and techniques that are set to use in these processes, you can divide them into two main segments, the analytical and the communicational.

The Driving process :  For a better Stakeholder Management
The Driving processIn both cases, only expertise, common sense and soft skills will guide you and even then, you will probably make a mistake in some moment. Don´t worry, because mistakes are expertise for the future and, believe me, everybody makes mistakes. (That´s part of the risk management)

GET A LEVERAGE BY UNDERSTANDING THE ROLES

Part of being an effective Project Manager is known for which strings to pull and the ones you must let go. That knowledge comes from listening, seeing and analyzing the non-spoken words in meetings. Just like when in a relationship someone does all the taking but when it comes to decisions always look for the approval of others that haven't said a word, that's the one in charge but probably is not interested in the issue.

So, how can I know the level of power, interest, influence or impact of each stakeholder? Do I use the force?

How do you analyse your Stakeholder?

The first is obvious, talk to people that have been involved in previous projects and try to know the stakeholders involved in the project. You know a guy from another company that worked there? Buy him some coffee and let him explain to you who is who in the company.

Or better, some guys in your office have worked there before. Well, let's gather information on which people involved will have more impact on the project, or if someone needs to be informed about every change of scope, etc.

You will probably expect that a CEO will have more power than a Manager, so that will be a good approach.

However, that's not the case of influence. It could happen that the CEO doesn't know what you will do because that’s not his/her area of expertise, so the manager makes all the decisions and has more influence on the project.

Another hint will be clarified in time if you see an attitude from other people involved to always pass all the big decisions to someone specific.

If you have the opportunity, during the first meeting when you are developing the scope of the project try to establish how the communication processes will be. There you will see people that want to be informed, the ones that have the final voice, some just need to check on them from time to time and the people you are going to work through the entire project and need to actively be engaged.

As you may notice, each one is just an example of common sense that use the communication processes to figure out the data you need to analyze and establish the role of the stakeholders involved in the project. If you know who is who in your project, you will have a leverage.

DEVELOP AN AGILE APPROACH ON ROLES OF EVERYONE IN THE PROJECT

So, what you need to keep doing after the project start with the stakeholder’s management?

I believe that success in this area came from three things:

  • Knowing roles
  • Handling expectations
  • Communicating effectively

develop an agileThese three represents the main questions Who? What? How?

Who? You need to know who is who in your project. Some people are there just for the champagne on the podium and some are because they care, you must know which one is relevant.

What? The reason many projects fails is that the scope of the project does not reflect the expectations of the stakeholders. You need to know how to handle the expectations and try to be completely clear about them, and if it is written in a document better. There is an article from the editor of knowledgeHut that give you 8 tips on how to handle it effectively.

How? You need to know the type of communication you need to use in each case. Maybe is in a meeting, or by an official document, even drinking coffee, you need to understand the moment and the way to do it. For instance, if some parts are delivered with delay and it implies a financial hit to the project it's better to talk in private first and deliver the news, then write an official document. Communicate effectively.
Knowing rolesWhen you are working on projects that will have an extended duration you need to know that the roles will change. As certain as the sun will rise tomorrow, people will get in and out of the project or even of the company. I am a faithful admirer of the waterfall, but in the world, we are living, every information is just a stone’s throw away; you need to develop an agile approach in many things, even in this. Some will change roles within the project, maybe the project leader will become a manager and his interested will change with his power, maybe some guy has an opportunity closer to where he grew up, it doesn't matter, in a project that lasts so long change will come.

There are things you need to keep doing along the project´s run:

  • Be informed by external references:

    You need to be informed of all possible changes that will affect your project. Make alerts in google news or read papers, it doesn't matter, you need to stay ahead of the game. For instance, if you are working with the federal government and a scandal get to the news, you should be aware that many people will probably change, be prepared and try to follow any information.

  • Gather information from people:

    If you don't like diplomacy and the importance of it, I truly advise you to see Game of Thrones. You don't need to like all the people involved, but you can make them inform, warn or advise you. Try to get ahead of the game and gather information about the new people involved or the new roles that will change. Being a Project Manager is not easy and will always require the extra mile to diminish the possibilities that some event make the project fail.

  • Effectively archive documents:

    I know that it sounds absurd, but many Project Managers fail in this. If you see that some guy, that you don't know, is making all the changes when you read the history in the reply of the last emails, then this guy has influence-power in the project.

  • Make less but effective meetings:

    It is absurd the amount of time we waste in nonsense meetings, so make them count and anyone involved in the project will try to be there. In them, you will update the roles of each stakeholder. Prepare meetings and give with a couple of days before so everybody knows all that will be discussed in them, try to establish who will be attending. “If you book them, they will come” Wayne Worlds 2.

effective meetingsLONG TIME PROJECTS STAKEHOLDER´S RELATIONSHIPS

Many of the success involved in getting a good relationship with the stakeholders in long projects is based on handling the expectations. Notice that you can develop a relationship of friends or you don't see them again when the project finish, but I will try to explain how to achieve good relationships, that will help you get successful project by managing expectations.

Building  a great Alliance

Remember when you were a kid and you will open Christmas presents? After you did an amazing letter to Santa where you describe that you want the Lego´s Falcon Millennium, there were three choices:

  • You get the Falcon Millennium toy, not the Lego. You are getting something similar but not what you asked.
  • You get the Lego´s Falcon Millennium. Yes, yes. Exactly what I asked.
  • You get the USS-Enterprise. Not even close.

The same happens with the expectations in a project with the possibility to see all the process from the letter, the elf determined the possibilities (if you were good or bad), the assembling, the package and delivering. So, if you see something strange you can put a red flag.

That's what happens in real life. The things the stakeholders want maybe are not possible. Your client wants the project to be built in three months, your boss wants 2% of cost reduction or the subcontractor established that he will not start until all equipment is in place. These are common things, many of them need to be established when making the scope of the project, but you need to keep all of them aware of the reality of the project. Don´t accept any request if it is not the reality of the project.

Some of them will bring discussions and will mean roughness in the relationship but is better to bring people down to earth from two feet that bring them at 5.000.

In the paper written by Ernest Baker in 2012 “Planning effective stakeholder management strategies to do the same thing”, he mentions tools for setting and managing expectations.
“…

  1. Stating the success criteria (project objectives) in the project charter.
  2. Defining what is in and out of scope in the project scope statement.
  3. Defining and getting agreement on the project deliverables documented in the WBS.
  4. Creating and sharing the project schedule or release burndown charts.
  5. Documenting who on the project team does what in a responsibility assignment matrix (RAM) or RACI chart.
  6. Creating and using a communication planning table to show how stakeholders will be kept in the loop for project information.
  7. Creating and posting project dashboards for the PMO or senior leadership.
  8. Creating, leveraging, and using project subsidiary management plans to handle all the processes necessary to define and manage the various parts of the project. 
  9. These sets of guidelines, or rulebooks, list the “how's” to do the various project management processes.
  10. Conducting project kickoff meetings to publically state project objectives and set stakeholder expectations.

Manage stakeholder engagementI believed that it is also significant to have a documented change requested process, so any change made from the initial scope needs to be understood (with all the implications of it) and accepted by the stakeholder´s initially established as the ones to possibly do it. Cause, in many opportunities, you will need to change the reality to meet the expectation of some stakeholders, but need to keep track of anything that will mean a change in time, quality or cost.If you keep the expectations and project reality closed to each other, you will have good relationships during the project´s run. once it is finished, you will decide which  relations are worth keeping and those who don't. It will be because you see an opportunity in the future, because you liked them and have affinities or because you will still work with him.

You need to understand that keeping track on relationships in this hi-tech world is as easy as writing congratulations on their birthday or an email once every year. Most people want to feel that meant for help in the progression of someone as if they really do than shame on you for not doing it.

CONCLUSION

Many of the “magic” of an effective stakeholder management comes knowing the roles, handling expectations and being an effective communicator. It means to gather information, a bit of diplomacy, analyze information and a lot of common sense (not so common after all). But in long time projects, it is all about keeping the gap between reality and expectations the closest as possible.

Victor

Victor Casal

Blog Author

Civil engineer, PMP certified and planning enthusiast. More than ten years of experience in construction project management, maintenance and operations consultancy in concessions agreements.

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

5 Amazing Benefits Of PMP Certification

Climbing up the career ladder is not easy and it takes a lot of hard work and patience. However, with a Project Management Professional (PMP) certification, things can become a little easier. A PMP certification can increase your salary dramatically and benefit your career. It improves your project management skills and makes you better at handling projects. Here are some of the benefits of earning a PMP certification: Growth In Career The PMP certification course is an internationally accredited one and is recognized by the entire global business community. Most big corporates look for PMP certified project managers and earning this certification would surely land you with a better job. Everybody in the corporate world know the benefit of networking. When you become PMP certified, you’ll be in touch with people pursuing PMP certification courses and ones who are already PMP certified. You never know who might help you in getting a better job (and salary). The more people who you are in touch with in your field, the better it is for your career growth. Enhance Your Skills It’s not easy to get the PMP certification and you need to undergo rigorous training for the same. There is a also a significant amount of coursework involved. You get trained and educated in in five project management processes—planning, initiating, implementing, monitoring and controlling, and finally closing. In short, you learn A-Z of project management which you can implement in your company projects for better project execution. Expand Your Marketability A PMP certification can help reach to global organizations working in different parts of the world. It enhances your professional marketability to a great extent and legitimise your experience as a project manager. You’d also be in touch with individuals aspiring to take up the course and PMP certified professionals as already mentioned, through project management forums and discussion boards, helping you to master your expertise with their tips and knowledge. Earn More PMP certified project managers earn more than the non-certified ones. As soon as you get your PMP degree, you can command a higher pay and you can expect an immediate hike. Many surveys have shown that PMP certified project managers earn at least 20 percent more than the non-certified counterparts. Also PMP certified professionals have the capability to earn a six figure income. Be A Project Manager Corporates Look For Last but not the least, a PMP certification shapes you as an efficient project manager, though that depends on how seriously you take up your course. A project manager needs to take care a lot of things and all such aspects are covered under this certification course. Project managers might need to train others and evaluate team members and even potential employees. A PMP certification gives you the skills and knowledge required to handle such situations as well. The benefits of PMP certification are many and not just limited to these five. No matter what your field is—commerce, finance, research, telecom, technology, or business, a PMP credential is a ideal bet for professionals looking for better job opportunities and is your stepping stone to new markets, new industries, and even new countries. The lengthy exam process and hefty exam and course fee might demotivate you for taking it up, but your money and time (and of course effort) is worth it as the returns you get is way beyond you can think of.
Rated 4.0/5 based on 20 customer reviews
1650
5 Amazing Benefits Of PMP Certification

Climbing up the career ladder is not easy and it t... Read More

7 Basic Quality Tools for Efficient Project Management

Quality is one of the modern project constraints which leads the project management processes and activates. There are 3 processes of quality management throughout the project lifecycle. These are- Plan quality management  Perform quality assurance  Control quality  Each of the 3 processes have their own tools, but there are some tools that can be used in all the 3 processes. These 7 basic quality tools are examples of shareable tools : 1- Flow Chart :- It is a graphical description of workflow steps. So it can describe the steps of any process through graphical symbols which are connected to each other by paths that represent the direction of the workflow. The symbols can be circles, rectangles, diamonds or any other shapes which must be predefined to make the flowchart easy for understanding.We begin the flowchart by the start node, which is often represented as a circle shape. Then we represent each action or step we do by rectangle shape. When we want to make a decision  or a test that will give more than one result, each result will direct us to a different path with a different action. Flowcharts are very useful when we want to make a correction for any process. It helps us eliminate the redundancy and unuseful work steps. Also, it is very useful when we use it for creating the project statement of work. 2- Pareto Diagram :- It is a special vertical chart that is divided into categories which show all possible probabilities or events that can occur. Categories are ordered by the frequency of each category from high frequency on the left side of the vertical axis to low frequency on the right side of it. Pareto depends on the rule of 80/20, which proves that 80/100 of problems comes from 20/100 of causes. So when we know that 20/100 of causes and give more attention and resources to avoid them, we will solve 80/100 of errors and problems. So Pareto Diagram is very useful when we use it with cause and effect diagram (also called Ishikawa or fishbone). The below example shows Pareto Diagram for the reasons that lead to delay in a software project.  3- Histogram : It is a tool for showing the central tendency, statistical distribution and dispersion of a given set of measurements that will be shown on a vertical bar chart  . it is very useful when we want to know which categories have a larger frequency. We can use it in many applications such as- defining the resources that will perform the project work by using Resource Histogram which shown below  We can do the same thing with one resource in a timely manner such as dividing the categories by months and defining the number of one resource such as senior developer via each month of the project lifecycle.  4- Cause and Effect Diagram (Ishikawa or Fishbone): It is a diagram that represents the cause and effect as a fishbone. Its head represents the problem or objective and the body represents the causes of the problem or the actions that should be performed to reach the goal or objective at the head of the fishbone. When we find a problem with any process such as a process variation or an increasing number of defects, we can use the fishbone to find the source of problem. Each resource can also be divided into a number of resources, till we reach the original resources of the problem. The Fishbone problem statement often comes from the Control Chart when its measurements point to a problem in the process stability. The following diagram shows the cause and effect diagram for the delay of software projects  5- Checksheets (Tally sheets) :- Check sheet is a sheet that contains items of inspections and tests and the attribute that each test can result in. The acceptance criteria of each test must be listed on the sheet to be a guide for determining if the inspected item of the sample such as- a piece of code in the software project has passed a test item (such as a unit test). Then we gather the frequencies of each defect and represent it in Pareto Chart.  6-  Scatter Diagram : Scatter diagram (called also Correlation Diagram) is a diagram represented by two axes  X and Y. So any measurement or data shown in Scatter Diagram is represented by a pair of (X,Y). The correlation between x and y shown is based on the rule that Y is dependent on X but X is not dependent on Y. So there are many types of correlations such as- positive correlation (proportional), negative correlation (Inverse) or pattern of no correlation (Zero Correlation). An example of positive correlation is- the weight of the human and its relation to his age (between one year and 40 ). We find that the weight of the human depends on and is affected by age (increase in age will lead to increase in weight but the  reverse is incorrect). So we will consider the age is X axis and the weight is Y axis. In a negative correlation, when X is increased, Y decreases.   7- Control Chart: When we want to determine if a process is stable or not, we use a control chart. It consists of-  Upper Specification Limits (USL) and Lower Specification Limits (LSL) which come from specification  Upper Control Limits(UCL) and Lower Control Limits (LCL) which come from statistical calculation +_3 standard deviation above and below mean   Mean which equals UCL+LCL/2 The process is considered unstable if one point exceeds the UCL or LCL or seven consecutive points are above or below the mean.  When we ensure that the process is unstable, we perform a corrective action and monitor the result of these actions to measure its effect on the process stability.  So these 7 tools are very useful and can be used  throughout the project lifecycle to plan and maintain the quality associated activities.   
Rated 4.0/5 based on 20 customer reviews
7 Basic Quality Tools for Efficient Project Manage...

Quality is one of the modern project constraints w... Read More

Which one to prioritize? Quality Assurance or Control Quality?

Initial Thought behind this Debate Needless to mention, Quality management is one of the most important and critical component of Project management. With the rapid changing business environments, organizations are always striving to attract their customers by meeting their expectations. Customer satisfaction is trending to be the key focus area in many organizations. Evolution of the dedicated & formal Customer Service (CS) and Customer Relationship Management (CRM) team, Relationship Manager role, Customer Royalty Program are few of the outcomes of the said focus area. Hence organizations are now leaving no stones unturned in devising their business strategies in line with the customer expectation. Product and service quality along with Quality management as a whole is playing a vital role in ensuring total customer satisfaction. What Most of the Customer wants? Most of the customers always consider 3 main factors while selecting or shortlisting any products or services. Typically these 3 factors are high quality product/service, competitive pricing and fast delivery. However it is extremely hard to meet all these 3 expectations at the same time and hence most of the organizations seem struggling to deliver all 3 requirements and end up delivering by meeting either 1 or 2 factors. However by having an effective quality management process in place will enhance the probability of overcoming the said challenges and organizations can always make a suitable trade off among the 3 expectations as per customer priority. So the big question is which process of quality management to prioritize to experience the desired outcome? Should it be Quality assurance or Control quality? Quality Assurance Vs. Control Quality Quality assurance is about processes whereas Control quality is about products. Quality assurance is mostly proactive whereas Control quality is mostly reactive. Quality assurance happens as soon as the project starts and continues throughout the project whereas Control quality mostly happens towards the end of the project. Quality assurance is mostly related to prevention and Control quality is mostly related to inspection. Final Thought Although both are very essential for the desired outcome, it is preferable to assign higher weightage to Quality assurance then Control quality. It is believed that Prevention is better than Inspection. By prevention, we not only minimize the risk of any issues but also reduce the time, effort and cost investment in dealing with the issues. Although quality threat can be identified by performing both Quality assurance and Control quality, the impact and loss is always higher if it is detected later. By Quality assurance we not only identify any quality threat at the beginning but also minimize the impact and loss of those quality threat by taking proactive and appropriate actions before the threat is significant. Hence Quality assurance should definitely be paid special attention while implementing any Quality management system or process.
Rated 4.0/5 based on 20 customer reviews
Which one to prioritize? Quality Assurance or Cont...

Initial Thought behind this Debate Needless to ... Read More