Enjisst offers a systemic approach to ensure software product quality on a continuous basis. Use a metaphor of a basketball game where goals (test cases) are defined from the beginning. It has a board that shows the result of the "party" (product status) in real time, analyzing quality from different perspectives such as risks, modifications, test coverage, among others. This allows you to make informed decisions about the output.

Introduces "Braided Development", inspired by basketball, where three key roles (Requirements, Testing and Development) work closely together. From the definition of the backlog, acceptance criteria are defined as testing ideas in Enjisst, guiding the team towards scenario thinking. Testing is automated from the start, providing developers with insight into the scenarios the code must meet and a way to run tests in their environment without extensive efforts.

The Quality-Focused Development proposed by Enjisst seeks to fluidly integrate the roles of Requirements, Testing and Development from the initial stages of the project. The methodology follows these steps:

1. Defining the product backlog: When defining the product requirements in the backlog, the acceptance criteria are also specified in the form of test ideas using the Enjisst platform. This leads the entire team to think in terms of test scenarios from the beginning.
2. Preparation of test sketches: Initial test ideas evolve into more detailed sketches with the major steps to follow for the interaction and validation of the system. AI tools and other facilities help detail executable steps.
3. Pre-development test automation: Before starting to code, detailed tests in the sketches are automated. This provides developers with a clear view of the scenarios they must meet and a suite of executable tests from the start.
4. Test-Driven Development: Developers use automated test cases to guide their coding process, aligning with agile practices such as ATDD (Acceptance Test-Driven Development).
5. Constant feedback: By having automated tests, developers can continuously run them in their environment and get quick feedback on their progress and code quality.

This methodology seeks to break traditional silos, closely integrating the Requirements, Testing and Development teams around a central artifact: automated tests in natural language. This allows for smoother collaboration, clear alignment with acceptance criteria from the start, and early detection of defects before starting to develop.

Compare the collaboration between QA and developers to a basketball team. The QA team creates automated tests tailored to different stages of the project, which developers can use to measure their performance and work on their “game” before “matches.” Additionally, there are different levels of tests, from simple (individual skills) to complex (game strategies). Enjisst has a solid architecture for the entire team to work collaboratively around testing.

Compare the flexibility of the development team to a basketball team where each player can play multiple roles. Enjisst allows each team member to take on test automation tasks, speeding up the process and improving efficiency. The definition of tests is carried out in colloquial natural language, guided by test cases, both for system actions and validation of its behavior. Promotes collaboration as any tester can run and view tests designed by other team members.