🛫On-boarding QA

QA's major role in a Software Development team was to make sure that the product quality requirements is fulfilled. An outcome that can be derived using different approach and testings.

QA's are not just a plain testers that waits for a released product to be tested. Together with the Developers, QA's has its own preparations and setting up plans for the test.

In Agile development, QA's once on-boarded are expected to taught it self about the project. Below are the preparations of QA when on-boarded.

1. Onboard from the start of the project

   This is the ideal way of on boarding a QA, where it has time to prepare its Requirement Analysis.

   1. Are expected to be working closely with the Project manager

   2. Be involve during the planning and discussion of development styles

   3. Do self research on alternate apps/software that has the same objectives with what the team are building

   4. Ask for the epics and user stories from PM

   5. Be involved in the creation of user flow

   6. Will do Visual QA

      1. Review the design in line to the user-stories

      2. Raise queries and suggestions on designs that are vague

   7. Will help clarify the whole concept of the User stories

      1. Raise question and suggestions to BA and PC

      2. Write acceptance criteria of the user stories (In Scenario: Gherkin syntax)

   8. Test planning (Define QA's testing approached to the product).

      1. Scopes and limitations

      2. Testing types

      3. Automation

      4. Tools

   9. Testing phase

   10. User acceptance Criteria testing

   On-boarded on the project kickoff, QA gains more knowledge about the product as well as can provide clarification ahead to the product scopes.

2. Joined when the project has started

   QA on-boarded in the middle of the development is very challenging. It took a week in order to have familiarize the product and reviewed the documentations. There is a possibility of communication gap since developers are more aware of the product than the QA. What must it do was:

   1. Get information about the scope, goal and limitations of the product.

   2. Ask for the priorities and closed P1 task

   3. Ask for product documentation

      1. Epics and User stories

      2. Product design

      3. Test plan (if there is)

   4. Do a better communication with every person in the team

   5. Inform yourself by exploring the products features

   6. Review what are needed that a QA can provide

      eg: Test plan, Acceptance criteria

   7. If no QA documentations, create a documentation. (This is no longer Priority 1 since the project testing are started).

   8. Provide suggestions or processes that would make the development clear and with no ambiguous requirements

   9. User acceptance Criteria testing

To be an effective QA, enlightening oneself on the product is a must. This goes by asking. raising questions and gave suggestions. A traits of a good communicator.