Tag: Process Improvement

  • QA – Why Bother?

    QA – Why Bother?

    If you get the feeling that this is a question you encounter a lot, you are not alone. We get a lot of calls and emails asking us to explain this question. Of course, the answer is dependent on who is asking the question.

    People want to know why they should consider it and, more importantly, the benefit. Sometimes they are simply looking for something to carry back to the project or department.

    In order to answer the question, we need to appeal to the broader costs calculated over multiple projects.

    We define QA as Process Improvement and processes generally apply to multiple projects (or at least can be applied to multiple projects). Hence the need for long term measurements and metrics.

    The simplest example is Defect Management. A simple process to ensure all defects are addressed and handled only once by each member of the team would remove a lot of redundancy.

    Other examples include Testcase creation; Testing; Summary reporting; Development; and Requirements management.  With the advent of AI, this has become much more critical to get right. The chances of going off track at high speed have increased substantially.

  • Are you satisfied with your testing?

    Are you satisfied with your testing?

    Most people we speak to answer that question with a resounding NO; they are not satisfied with their testing. The answer may vary from stakeholder to stakeholder, and the intensity and source of the dissatisfaction may be different.  However, doing something about it is a different matter.    The most recent of many examples involved someone who complained about the testing and was promptly put in charge.  Not the result they were aiming for at the time!

    Solving the dissatisfaction is very difficult. Process improvement is resisted on many levels and there is usually a large number of potential improvements that may impact the perception.  The starting point is with a stakeholder survey and process assessment; this gives the basis for supportable incremental changes to improve satisfaction. 

    Take a look at Assessments for a starting point on what to include.

  • Is your testing Ad hoc?

    Is your testing Ad hoc?

    While most people won’t come out and say that their testing is Ad Hoc, it can usually be inferred from some of the following comments:

    1. We keep redoing things.

    2. We seem to lose everything with every iteration.

    3. We keep re-inventing the wheel.

    4. We have thousands of testcases and most of them have not been looked at in years.

    5. We miss things in every release even though we saw them in the past.

    6. We keep solving the same problems in development.

    And on the list goes.

    If you feel you are stuck in this rut, it is time to break out

    .

    But that requires a fresh look at the following items:

    * Current assets

    * Current processes

    * Missing pieces

    * Left over items and problems. Breaking out of Ad Hoc testing is very difficult. Process improvement is resisted on many levels.

  • What do Test Managers do in a project?

    What do Test Managers do in a project?

    There would be an obvious answer to that question if one replaced the word Test with the word Project. So, if we transfer in reverse the answer is the same. Since we had to answer this question …

    Please take a look at Case Study 11: https://nvp.ca/wp-content/uploads/2025/05/Case Study 12.pdf  for an answer to this question.

  • Mentoring

    Mentoring

    Frequently organizations encounter a roadblock on their Quality Assurance Processes. Most tasks are progressing well but there is a hitch or a stumble somewhere. The problem is not large enough to warrant a full consulting contract but it needs to be resolved. This is where Mentoring helps.

    Issue: A client, who creates websites for government departments and high profile clients, was having trouble with their Quality Assurance process.

    Please take a look at Case Study 11: https://nvp.ca/wp-content/uploads/2021/10/Case-Study-11-Mentoring.pdf to see how this was solved quickly and cheaply.

  • Designing Testing

    Designing Testing

    Frequently organizations grow concerned about their Quality Assurance Processes. They are not sure if they are using the best processes for their testing. Everything has been internally built with little input from outside the organization. Over time the isolation may lead to inefficient processes. There may not be an awareness of what has changed and how it might impact their work habits.

    Please take a look at Case Study 7: https://nvp.ca/wp-content/uploads/2021/06/Case-Study-7-Consulting.pdf to see how the process was redesigned.

  • Coaching

    Coaching

    Frequently organizations encounter a need for Quality Assurance Processes. A client, wanted to improve their processes but had no idea how to get there or what was involved. They were also hampered by a lack of knowledge of how other departments worked or what they did before the applications reached QA or after they left.

    Please take a look at Case Study 6: https://nvp.ca/wp-content/uploads/2021/10/Case-Study-6-Coaching.pdf for how a process issue was resolved in one case.

  • Requirements

    Requirements

    While iterative methodologies do not expect full requirements at the beginning of a project, it may still be critical to eventually capture the entire set of requirements. Traceability between testing and requirements has become popular recently to provide auditability.

    Please see https://nvp.ca/wp-content/uploads/2021/06/Case-Study-8-Requirements.pdf for an example Case Study.