Quality Assurance at Auxo

Quality Assuarance is a crucial part of making top-notch products for global companies, this is why at Auxo we take it seriously. Auxo's QA team sits between the client/end user and the development team, helping to define the project's requirements, test objectives, and helping the development team to verify that the product works correctly before before it reaches the end user. It also plays a crucial role for support tickets in applications deployed in production. Quality Assurance at Auxo is comes to reality by a well defined process that we have defined through our years of experience making quality digital products. Our process is organized into 8 phases:

Phase 1: Start of the project

This phase allows us to understand in great depth what is the objective that we want to fulfill in the project, as well as to put ourselves in the role of the end user by defining that user and thus be able to carry out future testing thinking towards whom it is oriented.

  • Understand what the customer needs and what value is to be generated for the end user with the product.
  • Know the business and the client for which the project will be developed
  • Know the profile and/or type of user for whom the product is going to be developed.

Phase 2: Team Socialization

This information allows us to get to know the client and its end user; Bearing this in mind as QA you can make suggestions or observations of improvements in the project taking into account what you want to generate.

  • Understand the functionalities of the project and the flows that the client handles with its end use
  • Understand the value that you want to generate with the development of the project, in the client-user relationship

Phase 3: Definition of the MVP

At this point we must define what the minimum viable product of the project will be, we will know what functionalities are going to be developed in the project and in what order they will be done according to the priority that has been assigned (define if possible the amount of Sprints required).

  • Know and help define the functionalities that the product will have and its prioritization (MPV)
  • Support the construction of User Stories.

Phase 4: Design stage

As QA we can observe inconsistencies or necessary improvements between what is already defined and what is presented in the UX/UI designs, thus putting ourselves in the role of the end user, anticipating possible problems in time and we can also identify improvements.

  • Know the flows of the processes that will be handled in the development of the project
  • Validate that all the necessary supplies are ready to develop each Hu's (DoR)
  • Validate that the UX/UI design complies with what has been defined in the project so far.

Phase 5: Planning

At this stage it is already clear what is going to be developed and everything is ready to start with the Sprint, the QA team can start with the design of test cases.

  • Participate and detailed creation of the acceptance criteria of each user story
  • Comment and socialize doubts you have about user stories
  • Validate that the design presented by UX/UI finally complies with what has been established in the user stories
  • Identify the types of users and other data that we need to execute the different test scenarios
  • Propose test cases for user stories and share it with developers
  • Participate in point estimation for user stories

Phase 6: Daily's

In this way, the aim is to be all aligned and to know how the progress of the Sprint is going. It is possible to briefly comment on inconveniences that arise and the priority they require in terms of their solution and not affect or block the team.

  • Participate and listen by the What did I do yesterday? What am I going to do today? And what impediments do I have? (In case you have them)
  • Inform how the execution of the testing process is going. (taking into account versions, environments, etc.)
  • Comment if bugs or improvements have been found that we have identified and that should be considered.

Phase 7: Product demo and meetings with customers

The presence and participation of the QA team in demo meetings and others allows us to provide support to the team present since there are times when the client may have doubts or confusion about what they are seeing developed of the product, and we as QA will be able to help answer those questions.

  • Have available what may be necessary such as URLS / Test Accounts / TEST Elements such as accounts to carry out test transactions, documents, etc.
  • Support the team in socializing the incidents that have arisen in the sprint
  • Take note of the observations or conclusions presented at the meeting in order to manage them later

Phase 8: Retrospective

At the end of the sprint, the retrospective is carried out as QA, like the rest of the team, there must be the willingness to communicate and listen to each contribution; It is also important that when communicating a 'failure point' we go directly to the fact and not to the person, what really matters is to improve the way of working, not to point out other people as guilty.

  • As QA, like the rest of the team, we must identify possibilities for improvement in terms of people, relationships, processes and tools, to implement in the next sprint.
  • Find better ways of working.

Recent articles