This is the official performance evaluation framework for ibGuru developers.
Overview
We evaluate developers monthly using 5 dimensions:
1.
Delivery & Velocity
2.
Quality & Stability
3.
Autonomy & Initiative
4.
Collaboration & Communication
5.
Product Thinking & Impact
Each area scored 1–5 using a qualitative rubric.
KPI Categories
Delivery & Velocity
Measures: shipping frequency, ability to complete tasks, momentum.
5 – Outstanding
•
Ships high-value tasks weekly
•
Consistently delivers ahead of schedule
•
Unblocks themselves proactively
3 – Expected
•
Completes sprint tasks on time
•
Stable delivery pace
1 – Poor
•
Frequently blocked
•
Very slow iteration
•
Deadlines constantly pushed
Quality & Stability
Measures: bug frequency, regressions, need for rework.
5 – Outstanding
•
Stable releases
•
Rare bugs
•
Code requires minimal rework
3 – Expected
•
Typical bug rate
•
Occasionally needs revisions
1 – Poor
•
Many urgent fixes
•
High rework and instability
Autonomy & Initiative
Measures: ability to work without being told what to do.
5 – Outstanding
•
Independently earns tasks
•
Comes with proposed solutions
•
Anticipates problems
3 – Expected
•
Works independently once directed
•
Rarely needs reminders
1 – Poor
•
Needs step-by-step instructions
•
No initiative
Collaboration & Communication
Measures: clarity, alignment, documentation.
5 – Outstanding
•
Communicates early
•
Shares context
•
Predictable, transparent
3 – Expected
•
Reports progress weekly
•
Communicates blockers
1 – Poor
•
Silent working
•
Surprises late
•
No visibility
Product Thinking & Impact
Measures: does this person build features, or just write code?
5 – Outstanding
•
Understands user impact
•
Challenges bad ideas
•
Suggests better UX/feature choices
3 – Expected
•
Implements tasks correctly
1 – Poor
•
“Ticket taker”
•
Writes code without thinking product
Example monthly evaluation
KPI | Score (1–5) | Notes |
Delivery & Velocity | 4 | Completed all sprint stories |
Quality & Stability | 3 | Small issues, quickly resolved |
Autonomy | 5 | Proactively solved API issues |
Collaboration | 3 | Could communicate earlier |
Product Thinking | 4 | Suggested a better UX flow |
Total Score: 19/25
Rating: “Very Good”
Reflection
1. What did you accomplish this month?
(short bullet list)
2. Why did / didn’t deadlines get met?
(be honest—no blame)
3. What slowed you down?
•
unclear spec?
•
missing design?
•
technical blocker?
•
my own unfamiliarity?
•
communication?