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.
Tag: Quality Control
-
TASSQ May 2025 Webinar
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 -
Quantifying Intangibles – 3
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.
-
Quantifying Intangibles
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.
-
Why is QA Difficult to Understand?
It is difficult to quantify some aspects of QA, particularly the intangible aspects that cannot be costed. If they are lumped under the overall category of being long term improvements or ‘good for the company’, it is very difficult to justify that type of expense out of a project budget. It is no wonder that these types of ideas get very little exposure in your typical IT project.
-
TASSQ April 2025 Talk
Toronto Association of System and Software Quality -TASSQ is pleased to announce our Webinar for Aprilh 2025.
Topic: The Pursuit of Failure
Presenter: Chris Armstrong
Location: Online/Zoom
When: Tuesday April 29 at 6:15 p.m. until 7:30 p.m. EST
Cost: $14.00 CAD
Register at: TASSQ
Presentation Abstract:
As testers, we often seek balance: risk & quality, introvert & extrovert, holistic & granular, failure & success.
Throughout my twenty years in testing, I have had the longest relationship with failure. It has the power to demotivate, derail, break, and end progress.
Is our identity as testers in finding bugs, in pointing out where things are incorrect, do we only bring negativity, are we diametrically opposed to developers in this saga called software development?
What you will learn:
- Methods of reflection and retrospection to break the cycle of failure into success.
- The language that we use as testers has power.
- Awareness, movement, and relevancy – software is ever evolving, and we need to change with and help to shape its future, without burning out
-
Process for a Quality Assessment – Step 8
Implementation
Having completed, presented and obtained approval for the assessment, the next step is implementation. While this may be done either by the client or by the consultant supplying the assessment, one of the key aspects is to ‘assess the assessment’. In other words, make sure that what was correctly discovered is noted along with any misconceptions that might have been included in the assessment. These findings will feed into updates and course corrections along the way.
-
Process for a Quality Assessment – Step 7
Complete the Assessment
Build the report making sure to emphasize the critical points first and providing the supporting information in the appendices. Redacted report formats are available from NVP if you need it. Please contact us.