Sunday, 15 November 2015

Roles and Responsibilities of QA Lead

A test lead is most commonly responsible for the following activities:
#1. He must be able to identify how his test teams aligns within an organization and how his team would achieve the roadmap identified for the project and hence organization.
#2. He has to identify the scope of the testing required for a particular release based on the requirements document.
#3. Put out the test plan after discussions with the test team and have it reviewed and approved by the management/ development team.
#4. Identifying the required metrics and work to have them in place. These metrics could be an inherent goal for the test team as well as what is being testing.
#5. Identifying the needed testing effort by calculating the sizing needed for the given release and plan the effort needed for the same.
#6. Figure out what skills are needed and balance the test resources accordingly with those needs based on their own interests as well. Also identify if there are skill gaps and plan training and education sessions for the identified test resources.
#7. Identify the tools for test reporting, test management, test automation, etc. and educate the team as required to be able to use those tools. Again, plan knowledge transfer sessions in case required for team members for the tools they would use.
#8. Retaining skilled resources by instilling leadership in them and provide guidance to junior resources as and where needed which would help them to grow.
#9. Create a fun and conducive environment for all resources to make sure they have maximum throughput.
Manage the test teams effectively by:
#1. Initiate the test planning activities for test case design and encourage the team to hold review meetings, ensure the review comments are incorporated.
#2. During the testing cycle monitor the test progress by constantly assessing the work assignment to each of the resources and re-balance or re-allocate them as required.
#3. Check if there might be any delays in achieving the schedule and hold discussions with testers to figure out the issues they may be facing and strive to resolve them.
#4. Hold meetings within the test team to make sure everyone is aware of what the fellow team members are doing.
#5. Present the timely status to the stakeholders and management and instill confidence about the work being done.
#6. Prepare any risk mitigation plans in case there are any delays are foreseen.
#7. Bridge any gaps and differences between the testing team and the management and form a clean two way interface channel.

No comments:

Post a Comment

Tweets by @sriramperumalla