Defect Prevention Methodology

We use the Defect Prevention methodology in product development and within our iterations. Basically, this methodology follows the following principles:

1. Failure analysis during the requirements gathering phases.

2. Code quality testing: Tools such as CodeClimate are used to evaluate code quality and identify possible bugs. The code is also subjected to peer review by programmers.

3. Performance testing: Runtime analysis and stress testing.

4. Activation of Logs and error traces: We use the logs of the tools themselves that are accessible from the console or from text files, but we also use tools such as Sentry that notify the team via email of failures and execution errors. These tools are deployed in production instances to respond proactively when an error is detected.

5. Analysis of causes and preventive measures: Implementation of changes, brownbag meetings for the analysis of complex problems, expert advice on specific issues.

6. UAT tests: These are tests with end users, crucial in the context of a project to detect and control possible situations that may occur in the interaction with users.
7. Constant monitoring of the tool and its use: Cloud Service Monitoring Measures.