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.
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.
Bridging the Gap between vendors and the final client can be difficult for a System Integrator. It is one thing to actually make the decision, purchase the software, integrate the software and deliver it. It is very much another situation when you come to the various levels of testing and need to coordinate multiple vendors, one System Integrator, and a client with multiple departments with differing needs.
Please take a look at the Case Study 1 : https://nvp.ca/wp-content/uploads/2019/06/Case-Study-1.pdf for one occurrence.
Refining and maintaining the value of intangibles is an on-going task that must be re-visited with every project and at least once a year the entire list needs to be validated to confirm that they are useful items to be included in a project costing. Items that were important may no longer be necessary and new ones may need to be added.
Toronto Association of Systems and Software Quality (TASSQ) is pleased to announce our Webinar for May 2025.
Topic: Back to Basics
Presenter: Huib Schoots
Location: Online, Zoom
When: Tuesday May 27 at 6:15 p.m. (EDT)
Cost: $14.00 CAD
Register at https://tassq.org/events
Presentation Abstract:
Back to Basics
Organizations are often concerned that testing is not sufficiently focused on finding the problems that really matter. Testers often don’t know how to determine when they’ve tested enough. Testers are naturally inclined to test too much. So we test too much and probably regularly test the wrong things… The solution is simple: back to basics!
Presenter Bio:
My personal mission is to improve software quality by shaping better people by connecting, innovating, facilitating, coaching, enabling, and teaching. I’m fascinated by mindset, thinking, behaviour, communication, and collaboration. I’m active in many communities. Some keywords about me: humanist, servant leader, open, direct, creative, idea generator, result-driven, humorous, problem solver, curious, confronting, critical thinker, passionate and energetic, lifelong learner, entrepreneurial, analytic, and continuous (world) improver. I like hanging out with friends, singing in a rock band, playing trombone in a brass band, board & computer games, LEGO, photography, running, beer brewing, magic tricks, travelling, and reading. I work as a quality & test consultant, trainer & coach.
Plenty of reasons to Attend TASSQ Webinars:
As a professional involved in QA you will:
Get prompt information on topics and thought leadership affecting the QA community
Last week we gave a partial list of intangibles: Better Quality; Strategic decisions; Opportunity and Innovation; Flexibility and Information and Decisions. We recommended setting a base level cost so they had some value. It should not start out too high but as you gain information over the projects, it should be possible to refine the benefit and get a more accurate benefit figure.
Last week we talked about quantifying the intangibles related to a project without stating what they were. The inability to actually state what they are contributes to the inability to quantify them. So here is a partial list: Better Quality; Strategic decisions; Opportunity and Innovation; Flexibility and Information and Decisions.
Last week we talked about how missing Quantifying the Intangibles caused issues in people supporting QA efforts. When intangibles cannot be costed (but still take effort) and the benefits the provide may not be immediate they become a (not so hidden) cost on the project. At the very least we need to put a baseline cost on the intangibles.