ajtest
-
Upload
quickofficesqa -
Category
Documents
-
view
218 -
download
0
Transcript of ajtest
-
8/3/2019 ajtest
1/12
Team Lead:_______________ Date:__________ Evaluator:_________________
Employee Name:
Evaluator:
Project:
Key Performance
Criteria
F (Unacceptable) D (Needs Improvement) C (Meets Expectations) B (Good)Team members don't see him/her as
the leader. He doesn't set or monitor
six monthly objectives. Teammembers are indifferent to ways of
improving performance.
Team members on rare occassions,
look up to him/her. Rarely sets or
monitors six monthly objectives.Veryfew 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 teamachieve 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 achievetheir six monthly objectives.
Sets objectives and expectation towards
involvement in Scrum.
More than 20% turnover in the teamin 6 months
Between 15%- 20% turnover in theteam per year
Approx 10% turnover in the team per year Approx 8% turnover in the team per year
Never follows the performance
appraisal process. Always misses thedeadline
Sometimes follows perfromance
appraisal, one on one feedbackmeeting process. At times misses the
deadline
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 arecompleted in time.
Motivates people to meet objectives.
His assessment of team member'stechnical skills is faulty.
Rarely spots , nurtures and rewardstechnical talent.
Spots , nurtures and rewards technicaltalent.
Spots , nurtures and rewards technical talentand helps in assigning correct tasks.
Timings that are not in sync with therest of the team. Misses team
meetings with team frequently.
Team work hindered by lead absence.
Rarely schedules meetings to addressteam issues.Just on time in team
meetings and poor in organization.
Schedules meetings to address teamissues 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 dependanciesor issues and follows up on them andraises risks as appropriate.
Schedules meetings to address team issuesregularily.Always on time in team meetings and
ensures excellent organization.
Assists in creating work plan for team membersif required but always provides general
guidance. Identifies dependancies or issues and
follows up on them and raises risks asappropriate.Analyses team productivity and raises
discussion around process and quality of
deliverable improvement..
Forgets scheduled interviewsfrequently
Interviews are mostly not taken ontime and the detailed feedback by
email is not sent many times
Interviews are taken on time and thedetailed feedback by email is sent on t ime
as a response to the meeting invite.
Ensure that JD is shared with recruitmentteam and resumes are in line with JD, if
not raises issue.
Interviews are taken on time and the detailedfeedback by email is sent on time as a response
to the meeting invite.
Ensure that JD is shared with recruitment teamand resumes are in line with JD, if not raises
issue.
Discusses with hiring team on one's own
initiative.
Performance Level Definition (Provided as a guideline for evaluator)
Team Leadership &
Retention
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
Synerzip Performance Revi
Version 1.0, August 26, 2005
-
8/3/2019 ajtest
2/12
Team Lead:_______________ Date:__________ Evaluator:_________________
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 reportand/or informationsent not complete.
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.
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.
Leaves are not planned for team
and/or self and/or client/manager/HR
not informed regarding planned
leaves
Leaves are hardly planned in advance
and HR is informed after availing the
leave.
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.
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.
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.
Creates/contributes to work plan for team
and self, identifies dependancies and
follows up on them and raises risks as
appropriate.
Creates/contributes to work plan for team and
self, identifies dependancies and follows up on
them.
Sometimes raises risks and tracks them.
Passive contributor to scrum
meetings and contribution is focussed
on self as an individual only.
Participates in scrum meeting giving
updates on assigned task only.
Body language during scrum showsfocus 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 completesprint.
Participates in scrum meeting giving
updates on assigned task.
Body language during scrum shows focuson 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.
Participates in scrum meeting giving updates on
assigned task.
Body language during scrum shows focus onteam 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.
Version 1 0 August 26 2005
-
8/3/2019 ajtest
3/12
Team Lead:_______________ Date:__________ Evaluator:_________________
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.
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.
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.
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.
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 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 byinterrogating/discussing with PO and
end customers
Plans and executes manual
exploratory testing for the sprint.
Familiar with some test scripting tools,
test automation framework and record
and play back tool.
Is able to test using the above.
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.
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 automationframeworks 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
code of team members and peers and
provides useful comments on design.
Reviews design/ test cases and if possible code
of team members and peers and provides useful
comments on design. Contributes to coding
standards improvement. Follows and propagates
Pair Programming/Test-Case design technique.
Tech Savvyness- technical discussion
- agile skills and usage
- techincal approaches
described in whitepapers
- criteria specific to code : (write
less code to achieve morefunctionality and write code just
enough to pass tests)
Version 1 0 August 26 2005
-
8/3/2019 ajtest
4/12
Team Lead:_______________ Date:__________ Evaluator:_________________
Has a fixed set of skills that never
seem to improve. Is unwilling to
accept agile tools such as pair
programming , TDD etc.
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.
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 deploymenttest 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 newtechnology areas or techniques.
Has not suggested any design
improvements to client.
Rarely explores new technology areasand design techniques. At times
suggests usage of new technology as
improvement to design to client.
Explores new technology areas anddesign 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 designtechniques.
Suggests new techniques to improve design or
functionality and applies them.
Takes up responsibilities of doing POCs.
His estimates are very inaccurate
often going off by more than 20%
Estimates are delivered within 10-
15% of the estimated time
Estimates are accurate , always tries to
deliver within 5%-10% of the estimatedtime
Estimates are accurate , always tries to deliver
within 5%-7% of the estimated time.
Follows no specific process.
Estimates are guesswork or what the
client wants
Rarely follows agile estimation
process using planning poker or
equivalent process
Follows agile estimation process using
planning poker or equivalent process and
refines estimates after every sprint.
Follows agile estimation process using planning
poker or equivalent process and refines
estimates after every sprint.
Able to determine team velocity after first two
sprints and use that as the basis for estimating.
Planning &Estimation
Version 1 0 August 26 2005
-
8/3/2019 ajtest
5/12
Team Lead:_______________ Date:__________ Evaluator:_________________
Estimation and planning is a one time
exercise and there is no interim
review
Estimates and plans are rarely well
documented ,reviewed and re worked
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.
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.
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 nothave 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 theproduct 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 thesame.
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 describeuser personas. Never used a product
box
Can create a product box under someguidance. Cannot create an elevator
pitch but could do an effective sales
demo.
Can effectively deliver an elevator pitch.Has exact understanding and can draw
user personas/ product box.
Can effectively deliver an elevator pitch. Hasexact understanding and can draw some user
personas/ product box.
Can interrogate PO based on some user
personas.
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 thePO 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 afterevaluating 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.
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.
Routinely requires involvement from
Project Manager
Routinely requires involvement from
Project Manager
Escalations occur every six months.
Requires involvement from Project
Manager only for escalations.
Key client happy and seeks out the Team Lead
directly. Needs Project Manager involvement for
some critical escalations only.
Client personnel often have questions
about trust and integrity
Able to deliver an expectation of a client
such that client makes team
recommedation or appreciates without
soliciting feedback.
Able to over deliver an expectation of a client
such that client makes team recommendation or
appreciates without soliciting feedback.
Product
Requirements and
domain knowledge
Client Relations- client delight focus
- appreciation without
soliciting
Version 1.0, August 26, 2005
-
8/3/2019 ajtest
6/12
Team Lead:_______________ Date:__________ Evaluator:_________________
Client expresses explicitdissatisfaction on one or more
occasions
Client never expresses satisfaction. Client expresses satisfaction rarely andmost work goes without
acknowledgement. Client prefers projectmanager involvement.
Client expresses satisfaction and trust whensolicited and contribution in releases
acknowledged. Client relies on lead.
Does not participate in retrospectivemeetings
Ocassionally participates inretrospective meetings
Drives part of or all retrospectivemeetings and takes effort to initiate them
regularily. Raises valid operational issues,
anticipates client concerns and initiatesdiscussion on them.
Drives part of or all retrospective meetings andtakes 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.
Business
Development
Takes no initiative in identifying new
opportunities. Reluctant to engage inany presales activity required to start
a new project
Takes some initiative in identifying
new opportunities. Is reluctant toengage in any presales activity
required to start a new project, morecomfortable only with a known client.
Takes good initiative in identifying new
opportunities. Is willing to engage in anypresales activity required to start a new
project
Takes good initiative in identifying new
opportunities. Is willing to engage in anypresales activity required to start a new project.
Able to converse with client in pre salesdiscussion and demonstrate knowledge.
ec ves or ex mon s(to be filled by Evaluator only)
Performance Summary - Actual Performance against last 6 monthly objectives (to be filled by Evaluator only)
Version 1.0, August 26, 2005
-
8/3/2019 ajtest
7/12
Team Lead:_______________ Date:__________ Evaluator:_________________
G
RADE 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 towardsaccepting 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 inassigning 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 aroundprocess 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 analysesimprovements. Uses past learnings.
w - QA Leads
Version 1.0, August 26, 2005
-
8/3/2019 ajtest
8/12
Team Lead:_______________ Date:__________ 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.
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 conveyedin 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.
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 workingincrementally, 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
-
8/3/2019 ajtest
9/12
Team Lead:_______________ Date:__________ Evaluator:_________________
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.
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
-
8/3/2019 ajtest
10/12
Team Lead:_______________ Date:__________ 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.
Analyses a test strategy during sprint planning and
terospective and applies it to every sprint
Takes measures to introduce usage of tools to improve
code quality/ QA efficiency.
Ensures application of engineering prcatices such as
automated testing, Continuous refactoring andcontinuous 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 overseveral sprints for determining team velocity.
Version 1.0, August 26, 2005
-
8/3/2019 ajtest
11/12
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.
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 Productmanagement 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.
Can effectively deliver an elevator pitch. Has exactunderstanding 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 demonstartegood 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
-
8/3/2019 ajtest
12/12
Team Lead:_______________ Date:__________ Evaluator:_________________
Build a broad and deep relationship with client personnel -
seen as the "Go To Person" by client personnel
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