An NCR (Non-Conformance Report) from an Audit is the last thing anyone wants to see. Especially if you are not familiar with how to handle it. Your business is in production of high precision parts, or providing groceries to consumers, or a business-to-business solution. The last thing you need is an auditor asking questions about your software processes.
Please take a look at Case Study 3: https://nvp.ca/wp-content/uploads/2019/07/Case-Study-3.pdf for how an NCR was resolved in one case.
The role of a Test Lead varies widely between organisations and even within some large organisations. Some test leads execute a plan, other build and manage and some run multiple projects with other test leads running particular aspects. If you are in this position, you may be wondering what to do.
Please take a look at Case Study 2: https://nvp.ca/wp-content/uploads/2019/06/Case-Study-2.pdf for how training was organised in one particular example.
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.
Test Automation is critical to any ongoing test efforts. Without automation., there is no way that testing can keep up and it is almost impossible to complete regression testing or any sort of Performance Testing. Tracking current status is also difficult. With AI coming into the mix in both the product and the test tool, the need is greater than ever to understand what is available and how it works.
Please take a look at the Case Study 5: https://nvp.ca/wp-content/uploads/2019/07/Case-Study-5.pdf for more information
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.
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.