KPI

Atikur Rahman

Developer Information:

Name: Atikur Rahman
Role: Mid-Level Node.js Backend Engineer
Department: Engineering
Review Period: July 1, 2024 to Aug 31, 2024

KPI REVIEW
KPI category
Metrics
Target
Actual
Comment
1
Code Quality
Number of bugs reported post-release
Fewer than 4 bugs per release (1 major 3 minor)
july 1-31 - 1
Open
2
Code review feedback
95% of code review comments implemented
July 1 -31 - 2
Open
3
Adherence to coding standards
95% compliance as measured by eslint, sonarQube
July 1 - 31 - 1
Open
4
Task Completion
Percentage of tasks completed on time
90% of tasks completed by the deadline in a sprint
July 1 - 31 -2
Open
5
Number of tasks completed versus assigned
Completion of 9 out of 10 assigned tasks or equivalent in a sprint
July 1 -31 -2
Open
6
System Performance
Average response time
All api should be running under ~2sec
Jul 1 -31 -4
Open
7
System uptime
99.99% uptime
Jul 1 -31 - 5
Open
8
Error rates
Fewer than 3 errors per week in production and the error should not repeat. And error rate 0% would be consider as excellence.
Jul 1 - 31 - 2
Open
9
Collaboration and Communication
Participation in team meetings
Attend at least 90% of meetings in the timeframe
Jul 1 - 31 - 5
Open
10
Quality of communication in team chat channels
Positive feedback from 95% of peers
Open
11
Learning and Growth
Number of new technologies/frameworks learned
Learn and apply [X] new technologies/frameworks or suggest the improvement
Jul 1 -31 - 1
Open
12
Participation in training sessions
Taking/Attend at least 2 sessions to guide/mentor the fellow teammembers
Open
13
Certifications obtained
Obtain relevant certifications is a plus
Open
14
Innovation and Problem Solving
Number of new features or improvements suggested
Suggest at least 10 new features/improvements to PM. and write down in this doc
Jul 1 - 31 - 0
Open
15
Solutions to critical problems
Successfully resolve no of critical issues. Find the solution that’s impossible to find.
Jul 1 - 31 - 0
Open
16
Contribution to technical discussions
Actively participate in 90% of technical discussions
Jul 1 - 31 - 4
Open
17
Customer Impact
User feedback
Positive feedback from 90% of users
Open
18
Number of support tickets related to backend issues
Fewer than 2 support tickets in a week
Open
19
Customer satisfaction scores
Achieve a satisfaction score of 90 or higher
Open
20
Security and Compliance
Number of security vulnerabilities found and fixed
Fix 100% of identified vulnerabilities within a week/sprint. Give security patch where needed.
Jul 1 - 31 - 0
Open
21
Compliance with data protection regulations
the target will be set by audit tool later.
Open
22
Testing
Code coverage
Maintain 90% code coverage
Open
23
Test execution success rate
100% of test cases pass without issues
Open
24
Automated test cases written
Write at least 50 automated test cases in a week/sprint
Open
25
Attendence
Did not take leave more than 14 days in a year contribute 3%
Open
There are no rows in this table


Review Process:
Review Process
Details
1
Performance Review Meetings
Scheduled for July 10,2024
2
One-on-One Meetings
Per Sprint
3
Peer Reviews
Conducted every month
4
Self-Assessments
Due
5
Automated Reports
Generated Per sprint
6
Additional Goals
7
Feedback Mechanisms
8
Development Plans
There are no rows in this table



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.