Category: Process Improvement

  • Testing for System Integrators – Part 2

    Testing for System Integrators – Part 2

    Two days ago we asked two $10,000 dollar questions and this week we promised the possible answers. Unlike the questions, which are specific to the final client and the suppliers, the answers are more general and apply to both.

    1. The contracts state the following specifically about Quality Assurance and everyone is in agreement
    2. The contracts says nothing about it so far but we have Quality Assurance as a topic and the contract will not be finalised without this discussion
    3. The contracts says nothing about Quality Assurance so far but now that you have brought it up we will add it.
    4. There is something in the contracts about Quality Assurance and we can look it up for you (contracts are signed).
    5. There is nothing in the contracts (contracts are signed) and there is no intention of putting anything in the contracts about Quality Assurance
    6. We don’t know (but that is a good question)
    7. We don’t know (and we don’t care)

    Suffice to say the items in the above list have an obvious gradation from good to terrible in the order they are presented. If you get the first answer, you’re well on your way. If you get some of the middle answers you have some work to do, but you may be in time to effect some change. If you get the last few answers, you are in trouble!

    Next: What to do with the answers.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072
  • QA as an Afterthought

    QA as an Afterthought

    Why QA is so often an afterthought?

    1. Is it because QA is ‘traditionally at the end of the project”?
    2. Is it because people have too much else going on at the beginning of a project and cannot think about QA?
    3. Is it because QA does ‘not fit anywhere’ at the corporate level so ends up nowhere?
    4. Is it because QA is regarded as a necessary evil which no one wants to acknowledge?
    5. Is it because we do not know when QA is needed and by the time we find out it is too late to make a difference?
    6. Is it because QA does not do a good job of selling ourselves?
    7. Is it because …

    We could certainly go on with all the reasons that QA seems to be frequently ignored. 

    Not surprisingly, when people do take the time to consider the Return on Investment for QA, they are often shocked by how much it benefits them.

    #QA,#QualityAssurrance,#SoftwareTesting,#SoftwareTestingStrategy,#TASSQ,#NVP

    https://www.linkedin.com/newsletters/7399187902221443072
  • Focused decision-and-action engagement

    Focused decision-and-action engagement

    Stop release chaos: clearer priorities, faster decisions, and quality you can trust.

    Focused decision-and-action engagement with department managers and key stakeholders – 2 weeks – This engagement is designed to identify the most important measurable impediments affecting confidence, flow, responsiveness, adoption, and maintainability, align leadership around the issues that matter most, and produce a practical 90-day action plan that can be used immediately.

  • Importance of Counting             

    Importance of Counting             

    In a previous post we discussed the perception that QA may be counting too much.  Before we go deeper into that consideration, one of the other concerns is the reliability of the measurement.  We define Reliability as getting the same result if the measurement is taken under the same conditions twice.  Whether that result is correct is a different question but if the measurement is different when taken under the same conditions, it is not only invalid; it is also unreliable.  This can cause real problems, as it has in some projects.  Measurements taken by the vendor differed from the ones taken by the customer.  Not surprisingly the vendor measurement showed less outstanding defects than the customer’s ‘equivalent’ measurement.  It was eventually traced to one label used on only a few defects that was being excluded by an earlier filter on the vendor side.   Once that condition was removed, the counts agreed. 

  • Count the ‘Bouncebacks’

    Count the ‘Bouncebacks’

    “Bouncebacks’ is not a technical term in common use. In our usage here we are counting the number of times a defect (or issue) bounces back and forth between tester and developer (or other personnel). It is common for a defect to have a count of at least 2 and maybe 4 if some clarification is required. Here we are looking for defects or issues that are bouncing back and forth between development and testers too many times. One of our clients recently did this and then concentrated on the items that had high counts. Not surprisingly they discovered that the majority of the issues with high bounceback counts revolved around poorly written requirements. Instead of getting the requirement correct in the first place, the concept was being clarified by continuous back and forth communication late in the project with a high overhead and testing cost.

  • Out of Ideas

    Out of Ideas

    What happens if you are out of ideas of what or how to improve?

    Not surprisingly this has been considered by some of the pioneers of Quality Assurance. They understood that there was a limit to the number of ideas a person could generate.  The recommendation was to change the composition of the group coming up with the solutions while retaining continuity. One recommendation was to change everyone except the group note-taker.  There is nothing to prevent people coming back in a few years with new solutions to new problems (or suggesting them to the new group once they have had a chance to recharge).  Giving a break can work wonders for creativity.

  • No plan survives – Part 2

    No plan survives – Part 2

    No plan survives contact with the enemy

    An earlier post referenced the fact that the Quality Assurance and Business Plan need to be integrated to be successful.  In addition, the last post made the comment that a Quality Assurance initiative can be derailed by passive or active resistance (as can all plans).  The additional concern is that QA initiatives are small incremental long-term improvements.  The ROI does not fit nicely into a financial quarter or even an annual plan.  We also referenced the need to know the Stakeholders and their wishes to address them pre-emptively.

    However, the key consideration is to ensure accurate and supportable measurements that can be used to demonstrate any successes and to start with small improvements to have demonstrable successes reasonably quickly.  Then we build on those successes to make more changes that have more substantial impacts.

  • TASSQ and National Software Testing and Quality Engineering Conference 

    TASSQ and National Software Testing and Quality Engineering Conference 

    TASSQ April 2026 Meeting

    Presenter: Ari Rowland [Future proofing yourself in the AI world]

    Location: Online – Zoom

    When: Tuesday April 28, 2026

    Networking 6:00 – 6:30

    Presentation 6:30 p.m. (until 7:30 p.m.) EST

    Cost: $20.00 (CAD)
    Register at https://tassq.org/events.  (Still coming)

    Presentation Abstract: Will be coming

    National Software Testing and Quality Engineering Conference 

    The National Software Testing and Quality Engineering Conference is scheduled to take place on May 26, 2026, at the Delta Marriott in Downtown Toronto– 75 Lower Simcoe St, Toronto, ON M5J 3A6, Canada

    This conference is specifically designed for experts in software testing, quality assurance, and quality engineering, and it aims to provide a thrilling new gathering tailored to their needs.

    The field is currently experiencing a revolution with the introduction of AI, making this an ideal moment for professionals to take charge and stay ahead of the curve.

    By attending this one-day event in May, participants will have the opportunity to network with industry pioneers who are shaping the future, as well as leverage the power of AI through interactive workshops.

    For further details.