Performance Review Matrix - New
Performance Review Matrix - New
Performance Review Matrix - New
The final weighted score must be translated into the scale appropriate to the HR department in your office
Process
Start
Before a review
During a review
After a review
Scoring
Each competence should be rated 1 ~ 5
1 = unacceptable
2 = below average
3 = satisfactory
4 = above average
5 = excellent
The final weighted score must be translated into the scale appropriate to the HR department in your office
Process
Employees should be given this matrix when they start at GrapeCity and at the beginning of each review period
Before a review
Employees should do the following to prepare for the meeting
1. Select 2 items (expectations) where you feel you have done well
2. Select 2 items (expectations) where you feel you need improvement
3. Write 2 goals for the next period. They should be concrete and relate to one of the expectations (probably an item you mar
(Note: You do not need to score yourself for every item or compentence)
During a review
The review meeting will proceed as follows:
1. The employee can share their points, goals, and any additional comments/questions
2. The manager will share the scores and talk through any relevant points
3. The manager can help validate or revise the employee's goals based on the feedback
After a review
1. The manager will use the results of the Performance Review Matrix to fulfill any review documentation required by HR
2. Submit all documentation to HR
3. Submit all documentation to the Division Head and discuss any recommendations (regarding employees or the Performance
Competence Rating Weight Score Employee
Did well
Productivity 0 2 0
Customer Orient
0 1 0
Mindset
Design 0 1 0
Management 0 0 0
Mentoring 0 1 0
Research 0 1 0
Other/Intangibles 0 2 0
Overall 13 0.00
Employee
Need to improve Goal
* Does the developer get a reasonable amount of work done in a given period of time?
* Is the developer's velocity on bug fixing sufficient?
* Is the developer always take actions to avoid his assignment obstruct others’ assignment or slow
the project progress.
* Is the developer committed to delivering software on time?
* Suggest improvements to UI/UX of application, when appropriate
* Think of what the final customer want when making decision
* Figure out the user story
* Ensure we design robust, scalable and maintainable code
* Contribute to the design of new feature
* Improve the current design
* Ensure all defects are identified and handled with appropriate urgency. No critical defects should
ever make it into production
* Create high-quality code and demonstrate consistent improvement in speed and quality
* Make wise technical decisions
* Know when to communicate and when to apply for reasonable code review depending on
importance and complexity of his module
* Code work as designed
*Practice clear inter-team and intra-team communication. No one should suffer negative impacts
from preventable issues stemming from lack of or miscommunication
*Ensure all issues that arise are promptly communicated to stakeholders at the appropriate level
* Work alongside new employees you are assigned, which includes mentoring new trainees or
bringing veterans up to speed
Productivity 0 2 0
Design 0 1 0
Development 0 3 0
Communication 0 2 0
Management 0 0 0
Mentoring 0 1 0
Research 0 1 0
Research 0 1 0
Other/Intangibles 0 2 0
Overall 13 0.00
Employee
Need to improve Goal
Pgm Evaluation
QA Expectation
* Build test cases that thoroughly cover the requirements for each task
* Ask questions when important details are missed or unclear
* Complete assigned tasks on time
* Have a clear expectation but not say something like "it doesn't work as same
as…"
* Suggest improvements to UI/UX of application, when appropriate
* Think of what the final customer want when making expectation
* Figure out the user story
* Design and maintain test plans to handle regression mitigation, deployment
confirmation, and concurrency testing
* Ensure all defects are identified and handled with appropriate urgency. No
critical defects should ever make it into production
* Knowledge of the software should grow over time, as well as the speed and
quality
* Test every story to your best ability and communicate your findings
appropriately
* Test base on the specification and confirmations
* Practice clear inter-team and intra-team communication. No one should suffer
negative impacts from preventable issues stemming from lack of or
miscommunication
* Ensure all issues that arise are promptly communicated to stakeholders at the
appropriate level
* Organize and present sprint/training demos smoothly and consistently
* Work alongside new employees you are assigned, which includes mentoring new
trainees or bringing veterans up to speed