Bajaj Allianz - Assistant Vice President - User Acceptance Testing

Assistant Vice President - User Acceptance Testing

JOB PURPOSE (Summarize in one statement why the job exists; and how it contributes to the overall objective of the company) :

- Plan, organize and lead execution of User Acceptance Testing for functions related to new products, audit / compliance issues, finance and enhancements X

PRINCIPAL ACCOUNTABILITIES:

(Accountabilities associated with the job):

1. Planning:

- Analyze the calls released for the day per UAT on the request tracker model; Allocate the calls to the individual testers

- Review the status of the calls and update the status for individual calls on the request tracker model

2. Product specification/ draft document:

- Participate in the development meetings and provide input for change requests, enhancements and new products; Brainstorm and seek clarification on the filed product document from the product development team or other stakeholders in cases of high complexity

- Analyze and study the draft product specifications documents with product specifications provided by product development team to understand the end to end system perspective; Identify the gaps and give inputs on the same e.g. maturity implications from a system point of view

- Enable finalization of change requirements by showing the current system and options available/ feasible; Participate in discussions on complex cases of change requirements and provide inputs

3. Validation document vs. product specification analysis:

- Study and analyze the validation documents prepared by It team for new products and other change requests

- Upon development, identify the gaps between validation document and product specification by preparing flows and guiding team to conduct functional testing; Validate with other stakeholders such as finance team if accounting is in line with expectations

- Provide testing sign-off post user check and approval

4. User acceptance testing:

- Based on the finalized Business Requirement Document (BRD) between IT BA and business user, break the document requirements into various scenarios and expected results; Lead the team to build cases with specification requirements (convert BRD requirements into scenarios)

- Convert the scenarios into test cases into the system and match the system results with requirements; Share feedback with the IT development team and retest the iterations until testing is cleared

- Identify gaps and communicate impact and missing areas to Development team; Identify reasons for issues in the developed systems

- Escalate issues to the Head of Development as required, based on the extent of changes required, delays and changing priorities

5. Vendor management:

- Periodically monitor timelines and review the performance and quality of delivery of the vendor; Provide performance feedback to ensure desired objectives are met

- Review calls/ scenarios, calls managed by individual testers, pending calls with/ without finance impact, etc. on a day to day basis; Analyze the reasons for delays / time taken to prepare scenarios

- Conduct a review with the vendor team, number of scenarios and number of calls cleared by each outsourced team member to monitor quality and productivity

- For inconsistent performers provide feedback and reasons for non-performance to the vendor to ensure adequate training and support is given

6. Policy admin migration:

- Review the as-is process documentation for the policy admin migration project across the processes of operations, sales functions (IB & Agency) and finance

7. Team management:

- Participate in selection process to identify the right talent for the team

- Motivate, engage and retain key talent in the team

- Establish individual performance expectations and evaluation metrics, and regularly review individual performance

- Identify and create development opportunities for team members to enhance functional knowledge

3. MAJOR CHALLENGES:

(Challenges faced on an on-going basis in carrying out the job):

- Frequent changes in the prioritization impact date of delivery (DoD) and add to delivery pressures

- Multiple iterations for any development

4. DECISIONS:

(Key decisions taken by job holder at his/her end):

Following decisions are taken by the role:

- Final approval on the UAT and sign off for production

- Justifications on the UAT decisions/ reports

- Decision related to prioritization of calls

5. INTERACTIONS:

(Key working relationships a job holder needs to have INSIDE and OUTSIDE the company to accomplish the job):

Internal Clients:

- Roles you need to interact with inside the organization to enable success in your day to day work

- All functions and business: To ensure scenarios are tested and iterations are made to meet the change request requirements

- IT development team: To explain the gaps, impact and iteration requirements

External Clients:

- Roles you need to interact with outside the organization to enable success in your day to day work

- Vendors: To monitor timelines and review the performance and quality of delivery of the vendor

6. DIMENSIONS:

(Key numerical data which will reflect the scope and scale of activities concerning this job):

Financial Dimensions:

- (These should be quantifiable numerical amounts)

- Other Dimensions (FY 19)

- (Significant volume dimensions associated with the job)

- Total Team Size: 4

- Number of Direct Reports: 4

- No. of outsourced employees: 15

8. SKILLS AND KNOWLEDGE:

- Minimum acceptable proficiency for this job which best indicates the education and/or experience requirements of this job and not the incumbent

Educational Qualifications:

a) Qualifications:

- B. Tech / MBA IT

b) Work Experience:

- 10 years of experience

- Strong experience in testing with insurance domain experience of 1-2 years