You are here

Quality Planning

15 January, 2016 - 09:16

Adrienne Watt

It’s not enough to make sure you get a project done on time and under budget. You need to be sure you make the right product to suit your stakeholders’ needs. Quality means making sure that you build what you said you would and that you do it as efficiently as you can. And that means trying not to make too many mistakes and always keeping your project working toward the goal of creating the right product.

Everybody “knows” what quality is. But the way the word is used in everyday life is a little different from how it is used in project management. Just like the triple constraint (scope, cost, and schedule), you manage quality on a project by setting goals and taking measurements. That’s why you must understand the quality levels your stakeholders believe are acceptable, and ensure that your project meets those targets, just like it needs to meet their budget and schedule goals.

Customer satisfaction is about making sure that the people who are paying for the end product are happy with what they get. When the team gathers requirements for the specification, they try to write down all of the things that the customers want in the product so that you know how to make them happy. Some requirements can be left unstated. Those are the ones that are implied by the customer’s explicit needs. For example, some requirements are just common sense (e.g., a product that people hold can’t be made from toxic chemicals that may kill them). It might not be stated, but it’s definitely a requirement.

“Fitness to use” is about making sure that the product you build has the best design possible to fit the customer’s needs. Which would you choose: a product that’s beautifully designed, well constructed, solidly built, and all around pleasant to look at but does not do what you need, or a product that does what you want despite being ugly and hard to use? You’ll always choose the product that fits your needs, even if it’s seriously limited. That’s why it’s important that the product both does what it is supposed to do and does it well. For example, you could pound in a nail with a screwdriver, but a hammer is a better fit for the job.

Conformance to requirements is the core of both customer satisfaction and fitness to use, and is a measure of how well your product does what you intend. Above all, your product needs to do what you wrote down in your requirements document. Your requirements should take into account what will satisfy your customer and the best design possible for the job. That means conforming to both stated and implied requirements.

In the end, your product’s quality is judged by whether you built what you said you would build.

Quality planning focuses on taking all of the information available to you at the beginning of the project and figuring out how you will measure quality and prevent defects. Your company should have a quality policy that states how it measures quality across the organization. You should make sure your project follows the company policy and any government rules or regulations on how to plan quality for your project.

You need to plan which activities you will use to measure the quality of the project’s product. And you’ll need to think about the cost of all the quality-related activities you want to do. Then you’ll need to set some guidelines for what you will measure against. Finally, you’ll need to design the tests you will run when the product is ready to be tested.