Join my daily Newsletter

Subscribe to get my latest content by email.

    I respect your privacy. Unsubscribe at any time.

    preloader

    Process and Product Quality Assurance

    • Tuesday, Sep 22, 2015
    blog-image

    Watch what you’re doing

    The CMMI Handbook says:

    The purpose of Process and Product Quality Assurance (PPQA) is to provide staff and management with objective insight into processes and associated work products.

     

    If you read what they have to say, it is very much geared towards larger organisations. But clearly, quality is something all customers have a right to expect, regardless of their contractor’s size.

    So how does one “assure” quality?

    They go on to explain that the steps to do that are:

    • Objectively evaluating performed processes and work products against applicable process descriptions, standards, and procedures
    • Identifying and documenting noncompliance issues
    • Providing feedback to project staff and managers on the results of quality assurance activities
    • Ensuring that noncompliance issues are addressed

    Now, if you read that, it comes down to planning, finding out whether you remain on track, and correct whatever discrepancies you discover.

    Sounds totally straight-forward, and simple, and exactly what you should do. Except, of course, that it’s easier said than done – I know.

    The crucial aspect is once again to create a plan in advance. Milestones, specifications, whatever that specifically means for you in practice. It doesn’t need to be much, or be complicated. But it has to be there.

    If you neglect this step, you will never have a clear understanding of how your project is doing. If you haven’t yet read the posts in this series dealing with planning, now might be a good time.

    Process Quality Assurance

    Wow, totally something the Toyotas of the world would do, with their big QA departments and vice presidents and all that other big-sounding stuff. But you?

    Of course.

    After all, small organisations can have lightweight processes.

    Say, every Friday, you sit down for ten minutes and compare your project progress with your plan. There. Process.

    Now think back: have you done this last Friday? And if not, how can you make sure you do it coming Friday? There. Quality Assurance.

    That’s all there is to it: come up with a plan, and watch whether you stick to it. And if not, why not?