For the past three weeks in our special Project Management Roadmap series, we’ve been discussing three key components of basic project management — scope, schedule, and cost. Here in Week 4, you’re going to start thinking about quality in ways you may not have considered.
Want to turn that Spec Assignment into a paying client, or want to ensure your current client comes back again? Then you MUST deliver a quality product.
But how is that defined? And what tools and techniques can be used to ensure you deliver a quality product?
When I evaluate the quality of a project, I consider three primary areas — fulfillment of the project scope, the technical quality of the copy, and the quality of the entire process I used to complete the project. Let’s take a look at each of these in more detail.
Managing Customer Expectations
You’ll recall Week 1 of this series, we discussed the project scope. Specifically, I talked about the fact that a clearly defined project scope provides a list of all the project deliverables and the associated customer expectations. Well, the first and most important part of evaluating quality is simply this — did you deliver what you said you were going to deliver in the project scope?
To answer that question, you’ve got the choice to pull out your original proposal or develop a custom checklist. Either way, before you deliver the final product to the customer, you should go through your project scope and confirm you’ve met every aspect of it.