It is difficult to describe project quality management. Because each project is unique, there are many approaches to quality management. While there are best practices, they don’t offer any practical advice. There are many quality standards that are more complex and general.
Understanding the basics of project quality management is essential. These concepts will help you understand what you need to do for your project.
You will be able to see the structure of the article if you read the article.
Pin it to your Project Management Board. [iStock/milanvirijevic]Definition of Quality
Three key definitions of quality are equally important.
Quality refers to the degree at which a product or service meets the requirements.
This means that the project’s results should be as close as possible to what was requested. It doesn’t mean you shouldn’t suggest improvements to the requirements.
There is a catch.
It is not sufficient. It is possible to create a product that meets the requirements. It doesn’t necessarily mean that it will satisfy the customer.
If you do project management right, you will know what your customers want. What they want to gain from your project. What business cases they are interested in winning.
Top project managers don’t follow the customer’s requirements to a T. These managers are quick to obtain all requirements in order to implement them.
A quality product, service, or result must always meet the expectations of customers and stakeholders.
This means that you will need to help clarify the requirements. It is important that they understand the underlying expectations.
Last but not least. The project’s final results should not contain any defects.
A defect is an occurrence, quality, or state of a product that isn’t expected by the requirements.
In practice, however, it is impossible to guarantee a 100% defect-free product. It is important to agree on the types of defects that you should invest your time, money and effort in the first place.
It is a good idea to determine the severity of a defect. The severity of a defect is crucial for the success of a project.
Respect the Grade Requirement
You don’t need an iPhone for every mobile phone design. Not every building needs to be a palace.
It can be ugly, but it can also be functional. It might be inexpensive, but it still has to meet the needs of the market.
There will be results that are low-grade, but high-quality.
This requirement of a grade must be respected.
Do I need total quality?
My goal is to create a product that meets all requirements and has no defects. All stakeholders should be happy
It is too expensive. It may even be impossible.
You must meet certain requirements. Customers should not be disappointed by any defects.
But how do we draw the line?
It should be agreed upon by your customer and sponsor. It is within the constraints of time, budget, and scope.
How can you help them make the right decision? Explaining the Cost of Quality.
Make Your Decisions based on the Quality Cost
What is the cost of delivering a high-quality outcome?
You are familiar with the classic constraints. You know the definition. Quality is best incorporated into the scope of work.
This means that all work required to meet the requirements must include activities that ensure quality delivery right from the start.
There may be times when you need to quickly create a prototype and then polish it later.
You will need to compare the costs of these activities. Your goal is to answer a single question. Is it better for defects to be prevented or found and fixed?
ISO has been a symbol of prevention for many years.