Team Lead:_______________

Date:__________

Evaluator:_________________

Synerzip Performance Review - QA Leads

Employee Name: Evaluator: Project:

Key Performance Criteria Team Leadership & Retention

Performance Level Definition (Provided as a guideline for evaluator) F (Unacceptable) D (Needs Improvement) C (Meets Expectations)
Team members don't see him/her as the leader. He doesn't set or monitor six monthly objectives. Team members are indifferent to ways of improving performance. Team members on rare occassions, look up to him/her. Rarely sets or monitors six monthly objectives.Very few members in his team achieve their six monthly objectives. Team members most of the times look up to him/her. Sets or monitors six monthly objectives.Many members in his team achieve their six monthly objectives.

B (Good)
Team members most of the times look up to him/her. Sets or monitors six monthly objectives.Many members in his team achieve their six monthly objectives. Sets objectives and expectation towards involvement in Scrum.

More than 20% turnover in the team in 6 months Never follows the performance appraisal process. Always misses the deadline

Between 15%- 20% turnover in the team per year Sometimes follows perfromance appraisal, one on one feedback meeting process. At times misses the deadline Rarely spots , nurtures and rewards technical talent.

Approx 10% turnover in the team per year Approx 8% turnover in the team per year Follows perfromance appraisal process, one on one feedback meeting process. Appraisals are completed in time. Follows perfromance appraisal process, one on one feedback meeting process. Appraisals are completed in time. Motivates people to meet objectives. Spots , nurtures and rewards technical talent and helps in assigning correct tasks.

His assessment of team member's technical skills is faulty.

Spots , nurtures and rewards technical talent.

Attention and punctuality

- Punctuality in scheduling client calls, team meetings, sending status report. - Follow upon assigned action items and closing dependancies - Leadershipin team meeting or technical discussions - Participation in Scrum - contribution to hiring

Timings that are not in sync with the Rarely schedules meetings to address rest of the team. Misses team team issues.Just on time in team meetings with team frequently. meetings and poor in organization. Team work hindered by lead absence.

Schedules meetings to address team issues regularily.Always on time in team meetings and ensures excellent organization. Assists in creating work plan for team members if required but always provided general guidance. Identifies dependancies or issues and follows up on them and raises risks as appropriate.

Schedules meetings to address team issues regularily.Always on time in team meetings and ensures excellent organization. Assists in creating work plan for team members if required but always provides general guidance. Identifies dependancies or issues and follows up on them and raises risks as appropriate. Analyses team productivity and raises discussion around process and quality of deliverable improvement..

Forgets scheduled interviews frequently

Interviews are mostly not taken on time and the detailed feedback by email is not sent many times

Interviews are taken on time and the detailed feedback by email is sent on time as a response to the meeting invite. Ensure that JD is shared with recruitment team and resumes are in line with JD, if not raises issue.

Interviews are taken on time and the detailed feedback by email is sent on time as a response to the meeting invite. Ensure that JD is shared with recruitment team and resumes are in line with JD, if not raises issue. Discusses with hiring team on one's own initiative.

Version 1.0, August 26, 2005

Team Lead:_______________

Date:__________ Well prepared and in sync for the team and clinet meetings Schedules and attends meetings on time. Follows up on team action items from last meeting and on work related dependancies.Ensures MOMs are sent and action items identified. Raises issues on time so that client planning is not at risk. Sends or contributes to status report on time and information in teh status report is presented such that the client has no queries. Ensures client team member interactions proactively on the task.

Evaluator:_________________ Well prepared and in sync for the team and clinet meetings Schedules and attends meetings on time. Follows up on team action items from last meeting and on work related dependancies.Ensures MOMs are sent and action items identified. Raises issues on time so that client planning is not at risk. Sends or contributes to status report on time and information in teh status report is presented such that the client has no queries. Ensures client team member interactions proactively on the task. Sometimes tracks risks and documents it.

Comes unprepared for meetings/calls Hardly prepared and sometimes out of sync for the meetings. Does not follow up regularily on action items or depednacies and rasies risks too late or the risk does not catch the radar. Irregular in sending status report and/or informationsent not complete.

Leaves are not planned for team Leaves are hardly planned in advance and/or self and/or client/manager/HR and HR is informed after availing the not informed regarding planned leave. leaves

Self Leaves are planned in advance and HR is informed on time. Team schedule is planned taking into account leaves of team members by solicitingthat information. Client is reminded of team vacations schedule and Synerzip holidays. Responsibilities are delegated to others before going on leave and client informed. Creates/contributes to work plan for team and self, identifies dependancies and follows up on them and raises risks as appropriate. Participates in scrum meeting giving updates on assigned task. Body language during scrum shows focus on team tasks. Gives relevant inputs for their completion. Leads discussion to be goal and progress oriented. Brings up and encorages others to bring up blocking issues. Prioritizes and refines backlog. Contributes to finalizing teh Definition of Done. Participates in estimating for stories and breaking down into tasks. Contributes to review. Contributes to the retrospective. Leads by example by following the themes of working incrementally, iteratively, beyond speciality.

Self Leaves are planned in advance and HR is informed on time. Team schedule is planned taking into account leaves of team members by soliciting that information. Client is reminded of team vacations schedule and Synerzip holidays. Responsibilities are delegated to others before going on leave and client informed. Creates/contributes to work plan for team and self, identifies dependancies and follows up on them. Sometimes raises risks and tracks them. Participates in scrum meeting giving updates on assigned task. Body language during scrum shows focus on team tasks. Gives relevant inputs for their completion. Leads discussion to be goal and progress oriented. Brings up and encorages others to bring up blocking issues. Prioritizes and refines backlog. Contributes to finalizing teh Definition of Done. Participates in estimating for stories and breaking down into tasks. Contributes to review. Contributes to the retrospective. Leads by example by following the themes of working incrementally, iteratively, beyond speciality. Facilitates team to do the retrospective surface issues and find remedies.

does not contribute to work plan for team and rarely creates one for self.

Rarely creates/contributes to work plan for team, not regular in identifying dependancies or follow up. Incomplete risk planning.

Passive contributor to scrum Participates in scrum meeting giving meetings and contribution is focussed updates on assigned task only. on self as an individual only. Body language during scrum shows focus on individual tasks mostly and sometimes team tasks. Not able to effectively lead discussion to be goal and progress oriented. Brings up blocking issues related to self assigned work only. Rarely able to help and find bandwidth to chip on dependant tasks if required. Hesitates to takes up tasks such as QA, Bug scrub etc. that are not necesssarily pure development to help complete sprint.

Version 1.0, August 26, 2005

Team Lead:_______________

Date:__________ Gets involved in technical discussions and but is not able to spot issues, able to focus more on resolving them. Initiates technical discussions especially during early phases of the project but team does not look up to his technical leadership. Follows the iterative development process creating automation for functional slices testing at diffrerent levels: - Helps somewhat in creating user stories - Able to write some test scenrios and test cases without explicit functional specifications by interrogating/discussing with PO and end customers Drives technical discussions and has the ability to spot and resolve issues. Influences technical decisions taken esp in early phases of project. Gives quality contribution to design inputs and raises quality of deliverable. Really Enjoys technology.

Evaluator:_________________ Drives technical discussions and has the ability to spot and resolve issues. Influences technical decisions taken esp in early phases of project. Gives quality contribution to design inputs and raises quality of deliverable. Really Enjoys technology.

Tech Savvyness
- technical discussion - agile skills and usage - techincal approaches described in whitepapers - criteria specific to code : (write less code to achieve more functionality and write code just enough to pass tests)

Gets involved in technical discussions and but does not have the ability to spot and/or resolve issues. Initiates technical discussions especially during early phases of the project but is not able to contribute significantly.

Not familiar with iterative development and not able to comntribute testing effort running parallely with developers. Not familiar with creating any test automation.

Follows the iterative development process by - Assists in iteration planning - Identifies and Develops additional test cases and - Creates automation for functional slices testing at diffrerent levels: - Unit - Service (without the UI) - UI (capture playback automation) - Helps in creating user stories - Assists in defining customer acceptance Plans and executes manual tests exploratory testing for the sprint. - Able to write test scenrios and test cases Familiar with some test scripting tools, without explicit functional specifications by test automation framework and record interrogating/discussing with PO and end and play back tool. customers Is able to test using the above. - Ensuring that testing is carried out parallely without handoff between developers and testers. Plans, designs and executes manual exploratory testing for the sprint. Familiar with test scripting, test automation frameworks and record and play back tools. Standardizes usage of all of above to improve testing. Is able to test very quickly with high quality.

Follows the iterative development process by - Assists in iteration planning - Identifies and Develops additional test cases and - Creates automation for functional slices testing at diffrerent levels: - Unit - Service (without the UI) - UI (capture playback automation) - Helps in creating user stories - Assists in defining customer acceptance tests - Able to write test scenrios and test cases without explicit functional specifications by interrogating/discussing with PO and end customers - Ensuring that testing is carried out parallely without handoff between developers and testers. Plans, designs and executes manual exploratory testing for the sprint. Familiar with test scripting, test automation frameworks and record and play back tools. Standardizes usage of all of above to improve testing. Is able to test very quickly with high quality. Offer QA specific line items to product backlog Ensures that QA estimates are part of overall sprint estimates. Ensures clear and precise "Definition of Done".

Does not take effort to review and document code/ design / test cases

Takes efforts in reviewing document design/ test cases of team members and peers.

Reviews design/ test cases and if possible Reviews design/ test cases and if possible code code of team members and peers and of team members and peers and provides useful provides useful comments on design. comments on design. Contributes to coding standards improvement. Follows and propagates Pair Programming/Test-Case design technique.

Version 1.0, August 26, 2005

Team Lead:_______________ Has a fixed set of skills that never seem to improve. Is unwilling to accept agile tools such as pair programming , TDD etc.

Date:__________ Takes initiative in exploring new technologies, suggests applying new techniques learnt by reading white papers. Initiates exploring QA techniques such as pair programming, Taguchi/All Pairs test case reduction technique Familiar with deployment scenarios and able to deploy teh product independantly.

Evaluator:_________________ Initiates exploring QA techniques such as pair programming, Taguchi/All Pairs test case reduction technique Team members look upto and use the recommendations provided as they respect technical ability. Able to deploy product and create deployment test scenarios and documentation guide for deploymeny.

Does not take efforts to use tools to improve code quality / raise QA efficiency.

Takes measures to introduce usage of tools to improve code quality/ QA efficiency. Not confident about application of engineering practices within team: practices such as automated , Continuous refactoring and continuous code integration, no build failures and collective responsibility for product testing.

Takes measures to introduce usage of tools to improve code quality/ QA efficiency. Ensures application of engineering prcatices such as automated testing, Continuous refactoring and continuous code integration, no build failures and collective responsibility for product testing.

Takes measures to introduce usage of tools to improve code quality/ QA efficiency. Ensures application of engineering prcatices such as automated testing, Continuous refactoring and continuous code integration, no build failures and collective responsibilityfor product testing. Mentors team members on ensures that handoff between testers and programmers is not required by following the practices.

Not interested in exploring new technology areas or techniques. Has not suggested any design improvements to client.

Rarely explores new technology areas and design techniques. At times suggests usage of new technology as improvement to design to client.

Explores new technology areas and design techniques by reading white papers and judiciously applies them independantly. Suggests usage of new technology as improvement to design to client.

Explores new technology areas and design techniques. Suggests new techniques to improve design or functionality and applies them. Takes up responsibilities of doing POCs.

Planning & Estimation

His estimates are very inaccurate often going off by more than 20%

Estimates are delivered within 1015% of the estimated time

Estimates are accurate , always tries to deliver within 5%-10% of the estimated time

Estimates are accurate , always tries to deliver within 5%-7% of the estimated time.

Follows no specific process. Rarely follows agile estimation Estimates are guesswork or what the process using planning poker or client wants equivalent process

Follows agile estimation process using Follows agile estimation process using planning planning poker or equivalent process and poker or equivalent process and refines refines estimates after every sprint. estimates after every sprint. Able to determine team velocity after first two sprints and use that as the basis for estimating.

Version 1.0, August 26, 2005

Team Lead:_______________

Date:__________

Evaluator:_________________ Estimates and plans are well documented and reviewed and re worked. Able to provide value points which highlight value of the user story after interaction with PO. Effort is made to improve planning for every sprint by becoming more accurate in commitment.

Estimation and planning is a one time Estimates and plans are rarely well Estimates and plans are well documented exercise and there is no interim documented ,reviewed and re worked and reviewed and re worked. review Able to provide value points which highlight value of the user story after interaction with PO.

Product Requirements and domain knowledge

Doesn't upgrade self domain knowledge. Reads domain related material infrequently Does not take efforts in building domain knowledge within team. His product knowledge is limited to his tasks and rarely tries to understand the big picture. Does not have insight into product competitor portfolio. Never influences product requirements and design based on competituve analysis.

Makes an effort to build required domain knowledge by reading product documentation as well as articles on other product addressing similar issues. Domain knowledge is limited to the functionalities within the product. Has understanding of the pain points the product addreses and all end to end test scenarios of the functionality of the product worked on. Has a end to end knowledge of the functionality such that can perform the role of a Sr QA (manual testing) effectively

Builds required domain knowledge by reading product documentation, articles on other product addressing similar issues and their product data sheets. Has rich domain knowledge. Participates in related discussions within organization. Has knowledge of competing products and has read comaparitive analysis of the same. Can suggest product improvements to Product management. Has understanding of the pain points the product addreses and all end to end test scenarios of the functionality of the product he has worked on.

Builds required domain knowledge by reading product documentation, articles on other product addressing similar issues and their product data sheets. Has rich domain knowledge. Participates in related discussions within organization. Has knowledge of competing products and has read comaparitive analysis of the same. Has suggested product improvements to Product management and got a deeper understanding of end users' requirements and product strategy. Has understanding of the pain points the product addreses and all end to end test scenarios of the functionality of the product he is familar with. Can define user acceptance tests.

Can't do an elevator pitch or describe Can create a product box under some Can effectively deliver an elevator pitch. user personas. Never used a product guidance. Cannot create an elevator Has exact understanding and can draw box pitch but could do an effective sales user personas/ product box. demo. Not able to hold structured conversations with PO/customer. Literally follows requirements as they are communicated without questioning them Is able to conduct structured open ended conversations with product owner/customer on user stories for parts of product familiar such that they bring to light multiple options which can be narrowed down by the PO after evaluating them. Able to elicit some user stories effectively. Is able to conduct structured open ended conversations with product owner/customer on user stories on any functional area of the product such that they bring to light multiple options which can be narrowed down by the PO after evaluating them. Able to elicit user stories such that demos demonstarte good convergence with PO. Well versed in art of creating user stories from epics. Able to create user stories for system requirement as well.

Can effectively deliver an elevator pitch. Has exact understanding and can draw some user personas/ product box. Can interrogate PO based on some user personas. Is able to conduct structured open ended conversations with product owner/customer on user stories on any functional area of the product such that they bring to light multiple options which can be narrowed down by the PO after evaluating them. Able to elicit user stories such that demos demonstarte good convergence with PO. Drives complex user story or changed user story related interrogation with PO and details out user stories to tasks. Well versed in art of creating user stories from epics. Able to create user stories for system requirement as well. Key client happy and seeks out the Team Lead directly. Needs Project Manager involvement for some critical escalations only. Able to over deliver an expectation of a client such that client makes team recommendation or appreciates without soliciting feedback. Version 1.0, August 26, 2005

Client Relations
- client delight focus - appreciation without soliciting

Routinely requires involvement from Project Manager Client personnel often have questions about trust and integrity

Routinely requires involvement from Project Manager Escalations occur every six months.

Requires involvement from Project Manager only for escalations. Able to deliver an expectation of a client such that client makes team recommedation or appreciates without soliciting feedback.

soliciting

Team Lead:_______________ Client expresses explicit dissatisfaction on one or more occasions Does not participate in retrospective meetings

Date:__________ Client never expresses satisfaction. Client expresses satisfaction rarely and most work goes without acknowledgement. Client prefers project manager involvement. Drives part of or all retrospective meetings and takes effort to initiate them regularily. Raises valid operational issues, anticipates client concerns and initiates discussion on them.

Evaluator:_________________ Client expresses satisfaction and trust when solicited and contribution in releases acknowledged. Client relies on lead. Drives part of or all retrospective meetings and takes effort to initiate them regularily. Raises valid operational issues, anticipates client concerns and initiates discussion on them. Plans for and presents Synerzip value add to the client.

Ocassionally participates in retrospective meetings

Business Development

Takes no initiative in identifying new opportunities. Reluctant to engage in any presales activity required to start a new project

Takes some initiative in identifying new opportunities. Is reluctant to engage in any presales activity required to start a new project, more comfortable only with a known client.

Takes good initiative in identifying new opportunities. Is willing to engage in any presales activity required to start a new project

Takes good initiative in identifying new opportunities. Is willing to engage in any presales activity required to start a new project. Able to converse with client in pre sales discussion and demonstrate knowledge.

Performance Summary - Actual Performance against last 6 monthly objectives (to be filled by Evaluator only)

Objectives for Next 6 months(to be filled by Evaluator only)

Version 1.0, August 26, 2005

Team Lead:_______________

Date:__________

Evaluator:_________________

eview - QA Leads

GRADE

FOR SELF APPRAISAL

A (Outstanding)
Team members look up to him/her. He does a monthly review of six monthly objectives for his team. All members in his team achieve their six monthly objectives Sets objectives and expectation towards involvement in Scrum. Able to persuade, guide and mentor people towards accepting Agile Practices. Less than 8% turnover in the team per year Follows perfromance appraisal process, one on one feedback meeting process. Appraisals are completed in time. Motivates people to meet objectives and able to find interesting tasks for individuals. Spots , nurtures and rewards technical talent and helps in assigning correct tasks. Promotes team members doing tasks outside their specilization. Final grade Schedules meetings to address team issues regularily.Always on time in team meetings and ensures excellent organization. Assists in creating work plan for team members if required but always provides general guidance. Identifies dependancies or issues and follows up on them and raises risks as appropriate. Analyses team productivity and raises discussion around process and quality of deliverable improvement. Attempts communicate these by playing innovative games.

Interviews are taken on time and the detailed feedback by email is sent on time as a response to the meeting invite. Ensure that JD is shared with recruitment team and resumes are in line with JD, if not raises issue. Discusses with hiring team on hiring issues and analyses improvements. Uses past learnings.

Version 1.0, August 26, 2005

Team Lead:_______________ Well prepared and in sync for the team and clinet meetings Schedules and attends meetings on time. Follows up on team action items from last meeting and on work related dependancies.Ensures MOMs are sent and action items identified. Raises issues on time so that client planning is not at risk. Sends or contributes to status report on time and information in teh status report is presented such that the client has no queries. Ensures client team member interactions proactively on the task. Pays particular attention to risk management by tracking risk till completely mitigated and dicumented in status report. Maintains plans and udpates them when changes come. Impacts of changes on delivery is accuarately conveyed in meeting and status report. Self Leaves are planned in advance and HR is informed on time. Team schedule is planned taking into account leaves of team members by solicitingthat information. Client is reminded of team vacations schedule and Synerzip holidays. Responsibilities are delegated to others before going on leave and client informed.

Date:__________

Evaluator:_________________

Creates/contributes to work plan for team and self, identifies dependancies and follows up on them. Raises risks amd tracks their mitigation.

Participates in scrum meeting giving updates on assigned task. Body language during scrum shows focus on team tasks. Gives relevant inputs for their completion. Leads discussion to be goal and progress oriented. Brings up and encorages others to bring up blocking issues. Prioritizes and refines backlog. Contributes to finalizing teh Definition of Done. Participates in estimating for stories and breaking down into tasks. Contributes to review. Contributes to the retrospective. Leads by example by following the themes of working incrementally, iteratively, beyond speciality. Contributes to surfacing the gap between the team and the PO and working with team to reducing the gap. Plays the role of scrum master.

Final grade Version 1.0, August 26, 2005

Team Lead:_______________ Drives technical discussions and has the ability to spot and resolve issues. Influences technical decisions taken. Gives quality contribution to design inputs and raises quality of deliverable. Really Enjoys technology.

Date:__________

Evaluator:_________________

Follows the iterative development process by - Assists in iteration planning - Identifies and Develops additional test cases and - Creates automation for functional slices testing at diffrerent levels: - Unit - Service (without the UI) - UI (capture playback automation) - Helps in creating user stories - Assists in defining customer acceptance tests - Able to write test scenrios and test cases without explicit functional specifications by interrogating/discussing with PO and end customers - Ensuring that testing is carried out parallely without handoff between developers and testers. Plans, designs and executes manual exploratory testing for the sprint. Familiar with test scripting, test automation frameworks and record and play back tools. Standardizes usage of all of above to improve testing. Is able to test very quickly with high quality. Offer QA specific line items to product backlog Ensures that QA estimates are part of overall sprint estimates. Ensures clear and precise "Definition of Done". Able to create and plan a regression suite for all sprints and for the entire release such that it runs on nightly builds regularily.

Reviews code of peers and comments on design, contributes to coding standards improvement. Follows and propagates Pair Programming technique. Uses retropective to analyse and discuss quality and efficiency improvement.

Version 1.0, August 26, 2005

Team Lead:_______________ Initiates exploring QA techniques such as pair programming, Taguchi/All Pairs test case reduction technique Team members look upto and use the recommendations provided as they respect technical ability. Able to deploy product and create deployment test scenarios and documentation guide for deploymeny. Analyses a test strategy during sprint planning and terospective and applies it to every sprint

Date:__________

Evaluator:_________________

Takes measures to introduce usage of tools to improve code quality/ QA efficiency. Ensures application of engineering prcatices such as automated testing, Continuous refactoring and continuous code integration, no build failures and collective responsibility for for product testing. Can take responsibility for builds and the build integration ennvironment. Mentors team members on ensures that handoff between testers and programmers is not required by following the practices.

Explores new technology areas and design techniques. Suggests new techniques to improve design or functionality and applies them. Takes up responsibilities of doing POCs. Provides technical comparions for using new technologies and other teams in teh organization refer to these. Final grade Estimates are accurate , always tries to deliver within 5% of the estimated time. Follows agile estimation process using planning poker or equivalent process and refines estimates after every sprint. Converts estimates to commitment based on data collected on team velocity and assigns a time range for commitment and gives schedule commitments based on that. Able to determine team velocity after first two sprints and use that as the basis for estimating. Collects data over several sprints for determining team velocity.

Version 1.0, August 26, 2005

Team Lead:_______________ Estimates and plans are well documented and reviewed and re worked. Able to provide value points which highlight value of the user story after interaction with PO. Effort is made to improve planning for every sprint by becoming more accurate in commitment. Contributes to discussion towards scope changes if commitments cannot be made. Final grade Builds required domain knowledge by reading product documentation, articles on other product addressing similar issues and their product data sheets. Has rich domain knowledge. Participates in related discussions within organization. Has knowledge of competing products and has read comaparitive analysis of the same. Has suggested product improvements to Product management which have been accepted as features for future releases. Has got a deep understanding of end users' requirements and product strategy. Has understanding of the pain points the product addreses and all end to end test scenarios of the product. Can define user acceptance tests.

Date:__________

Evaluator:_________________

Can effectively deliver an elevator pitch. Has exact understanding and can draw user personas/ product box. Can interrogate PO based on these user personas.

Is able to conduct structured open ended conversations with product owner/customer on user stories on any functional area of the product such that they bring to light multiple options which can be narrowed down by the PO after evaluating them. Able to elicit user stories such that demos demonstarte good convergence with PO. Drives complex user story or changed user story related interrogation with PO and details out user stories to tasks. Well versed in art of creating user stories from epics. Able to create user stories for system requirement as well. PO solicits inputs regarding various approaches and priorities. Final grade Key client extremely happy and seeks out the Team Lead directly. Trust lead to resolve escalations. Able to over deliver most expectation of a client such that client makes team and individual recommendation or appreciates without soliciting feedback. Version 1.0, August 26, 2005

Team Lead:_______________ Build a broad and deep relationship with client personnel seen as the "Go To Person" by client personnel

Date:__________

Evaluator:_________________

Drives part of or all retrospective meetings and takes effort to initiate them regularily. Raises valid operational issues, anticipates client concerns and initiates discussion on them. Plans for and presents Synerzip value add to the client. Initiates regular feedback with client middle management and incorporates progress from sprint retrspectives in these meetings. Final grade Naturally grows the existing client engagement increasing team size and Synerzip scope of involvement. Enthusistic about new projects. Creates whitepapers for Synerzip.

Final grade

GPA

Version 1.0, August 26, 2005