Struggling with Employee Target Sheets: What Should I Include for Effective Reviews?

Hi all,

I am an HR Manager with a software development organization. I am stuck with designing a sheet on targets for employees. This is more related to:

1. Number of productive hours spent in the office.
2. Targeting goals for next year's review.
3. Performance management.
4. Project status, etc.

Can somebody help me with the format or explain what all parameters should be covered to get the overall status of individuals that help to decide next year's increments and goal settings in the future?

You appear to have some misgivings about the concept of targets. Targets are not based on productive hours but on the cost of the output, resources used in delivering the output, time taken to deliver the output, and the output itself. It is the HOD's job to design the targets, not yours. HR is only a process facilitator or process owner of PMS. In my previous query that was similar to yours, I provided an exhaustive reply. You may click the following link to refer to it: https://www.citehr.com/526357-kpi-kr...-download.html

In addition to this, I have uploaded my video on PMS. You may click here to refer to it.

Thanks,

Dinesh Divekar

Dear Dinesh,

Thank you! I have gone through the thread. So, what are the criteria to understand the productivity that can be helpful for next year's appraisals? Or, can I create a system/process that shows the growth of an individual considering career path, promotions, hikes, etc.

Hi there,

I am having the same issue. A timesheet could be a solution for this. Can anyone post a template of a timesheet in Excel? Thank you.

I am providing below a sample JD and KPI for a developer. I hope this is helpful to you.

Product Development:

- Coding
- Bug Fixing
- Documentation

Project Delivery:

- Follow agile and scrum methodology for executing the project
- Ensure that the features are delivered on time
- Contribute to the design and architecture of the product
- Perform self and peer code review

Quality Assurance:

- Follow coding standards
- Perform proper unit testing

Process and Compliance:

- Follow the organization's policies and processes
- Maintain the quality of the work environment

Domain Expertise:

- Should be abreast of the latest trends and technology in the domain

Innovation:

- Provide new ideas for the product

KPI Ratings:

Product Development:

- 5 - No reopen bugs
- 4 - Out of total bugs assigned, up to 20% bugs reopened
- 3 - Out of total bugs assigned, up to 40% bugs reopened
- 2 - Out of total bugs assigned, up to 50% bugs reopened
- 1 - Out of total bugs assigned, more than 50% bugs reopened

Project Delivery:

- 5 - All user stories completed as per initial estimate with no bugs
- 4 - 80% user stories completed as per initial estimate with less than 5 bugs
- 3 - 60% user stories completed as per initial estimate between 6-10 bugs
- 2 - 50% user stories completed as per initial estimate between 11-15 bugs
- 1 - Less than 50% user stories completed as per initial estimate and more than 15 bugs

The work hours need not be directly linked to productivity in the case of a software developer; emphasis should be on the outcome, bug-free codes, etc.