This document outlines key result areas and key performance indicators for evaluating a developer role. It discusses the following key result areas: result, process, product/project/service, growth, and goal. It then provides examples of KPIs for evaluating a developer's coding, programming, testing, documentation, delivery, estimation, and research skills. Specific KPIs include lines of code per day, code standard adherence, maintainability, reusability, testability, comment analysis, number of bugs, delivery timeliness, estimation accuracy, and knowledge sharing. The document provides details on how each KPI would be set up and measured.

1. Key Result Areas

2. What
Result => Generic
Areas that directly impacts the final result
Process => All
Roles that directly impacts the final process
Product/Project/Service => Customers
Resources that directly impacts the final product
Growth => Organizations/Institutions
Plans that directly impacts the final growth
Goal => Individuals
Dreams that directly impacts the final goal

3. How to find those areas?
Define Objectives
List activities performed by each Role - Customer, Organization, Individual
Analyze impacts of those activities on the final result
Prioritize/Filter activities
Define Key Performance Indicators
Define metrics
Define process to measure KPI metrics

4. KRA - Developer Role
Coding
LOC, Coding Standard Adherence
Programming
Maintainability, Reusability,
Testability
Research
Knowledge Sharing [Blog, Presentation], Building/Maintaining Organization Frameworks, PoC/Demo
Documentation
Comment vs Self Document
Code
Testing
Bugs Count and Critical vs
Blocker bugs
Deployment/Delivery
Timely Delivery, Deliverable
Items
Estimation
Estimation Accuracy Rate

5. KPI: Coding - LOC
Average LOC per day during project duration
Measurement varies based on technology, experience or excellence
How to setup?
git blame tool
repository analysis tool
How to measure?
Daily
100-500 LOC 100%

6. KPI: Coding - Standards
Define important standards technology wise
Average broken standards per day based on LOC
How to setup?
fxCop
Visual Studio
ReSharper
How to measure?
Daily
10 violations per n LOC - 100%

7. KPI: Programming - Maintainability
Design Patterns, Architectural Patterns review
Reviewed on each delivery instead of continuous measurement
Complexity measurements per n LOC
How to setup?
nDepend
Manual Review
How to measure?
Quarterly
Leaders will do it

8. KPI: Programming - Reusability
Coupling measurement.
Reviewed on each delivery instead of continuous measurement
Amendment in Common Functions/Frameworks
EmailSend(from, to, business_type)
EmailSend(from,to,subject,content)
EmailSend(EmailParameter parameter)
How to setup?
How to measure?
Manual Review
Measure Quarterly
>6 Amendments - 100%
2-5 Amendments - 70%
1 Amendment - 20%

9. KPI: Programming - Testability
TDD
How to setup?
How to measure?
Visual Studio
Manual Review

10. KPI: Documentation
Comment Analysis
HowTo comment
Logical comment
Authoring comment
Percentage of comment per n LOC.
Comment vs Self documenting Code
int count = list.length vs int total_emails = inbox.length
How to setup?
How to measure?
Each Delivery
Customize tool that measures comment lines
Manual Review
15% comment should be there for n LOC

11. KPI: Testing - Bugs
Total number of bugs
Bugs per story
Bug reopened rate
Critical vs Blocker bug rate
Measure on each delivery
How to setup?
How to measure?
Each Delivery
0-2 Critical Bugs - 100%
3-6 Critical Bugs - 70%
7-10 Critical Bugs - 50%
>10 Critical Bugs - 0

12. KPI: Delivery - Time
Able to deliver based on committed time
How to setup?
How to measure?
Each Delivery
0 day extend - 100%
1 day extend - 70%
2 days extend - 50%
3 days extend - 20%
>4 days extend - 10%

13. KPI: Delivery - Deliverables
Ensures all deliverables are delivered
How to setup?
How to measure?
Each Delivery
>Artifacts
Release Note missing/improper - 50%
Forgot to tag version control - 50%
Forgot to send test results - 50%
>Requirements
0 Missing Requirements - 100%
1 Missing Requirements - 50%
2-3 Missing Requirements - 20%
>3 Missing Requirements - 0%

14. KPI: Estimation - Accuracy Rate
Ensures accuracy of estimation
How to setup?
How to measure?
Each Delivery
0-10% Accuracy Deviation - 100%
11-20% Accuracy Deviation - 70%
21-30% Accuracy Deviation - 30%
>30% Accuracy Deviation - 0%

15. KPI: Research
Helps to improve organization knowledge pool
Public blogs/presentations may help to increase company brand
How to setup?
How to measure?
Quarterly
>Knowledge Pool
1 Presentation - 100%
>Public Brand
1 Blog - 0-50% [Based on content]
1 Presentation - 0-50% [Based on content]

16. Thanks