Quality starts at the Beginning
It has been said before. By Boehm and many others. You save a lot of time and money if you pay extra attention to the beginning of a project where you define your plans and collect your requirements. But actually quality starts even before that. The real beginning of change is what is actually running in production. Therefore you need to know what is in production. Is it documented? Is it modelled? That would help build (regression) test cases.
IT changed and so did Quality
Over the last ten years, due to agile and devops, testing is not only done by testers but also by other IT consultants and maintenance people. Do they have the knowledge? Or is it just monkey testing that they do? Is it documented? Do you know what the coverage of those tests is? Do you only test the happy flow or also the rainy day scenarios? Do you have a regression test that covers your landscape so we know what we need to test when changes come in?
Laying a proper foundation is crucial
We miss a lot, when we don’t have a proper foundation. Not only do we create operational vulnerabilities, but security vulnerabilities as well. So now we are back where we started: at the very beginning. Set up testing properly, with what is required with a limited amount of paperwork. Know your “as is”. Test your architecture and use it. Of course automate as much as possible… when you know what to automate. Maintain your regression test. Put a backup of your production environment (which you need for business continuity anyway) to test the “as is” as well as possible and improve the “as is”. Not to “to be” because “to be” does not exist, the world changes continuously. You change to the next “as is”.
If you need support please mail or call me.