NVP Software Solutions

Category: 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.

  • Isn’t there a better way to Test?

    Isn’t there a better way to Test?

    This is a question that gets asked very frequently especially at the end of projects that have not gone well.

    While there are many people who will advocate one methodology or another for testing and tell you their way is the only way, every method must adapt to the project at hand, the risks and the desired outcomes.  There is no one way to test but there are ways to improve the testing.

    The first need is time at the end of the project to evaluate what went right and wrong before people forget.

    Some common concerns:

    1. Too much documentation:  It is acceptable to reduce documentation if the same testers will be available for the next project but not so effective if the next project will be staffed with new people unfamiliar with the project.
    2. Too little documentation:  This can be solved but it takes time or can be fed through AI to generate the complete documentation.  Always review anything produced by AI.
    3. Too much repetition:  This is a process error that can be solved by RCA and then implemented but is not likely to have much effect for at least a project or two.
    4. Unused testcases:  This is a classification issue that can be solved with AI at this point.
    5. Too many escaped defects:  Again RCA with the aid of AI can address this but it is too late to implement the solution for the existing project.
  • 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.

  • 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.

  • Privacy

    Privacy

    Privacy of data is becoming increasingly important to the industry. With increasing regulations and increased scrutiny from the press, no organization can hide data breaches for too long.

    Issue The client was facing a privacy audit from one of their customers.

    Please take a look at Case Study 10: https://nvp.ca/wp-content/uploads/2021/06/Case-Study-10-Privacy.pdf to see what was provided.

  • 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.