Kra Templates For Project Leaders m2b6i

Role: Project Leader (Technical) Objectives 1. Deliverables a. Schedule adherence - Complete Module on time

b. Ensure Code performance meets expectations c. Meet Process Audit requirements d. Meet norms for code quality

e. Standards f. Effort g. Quality of deliverables 2. Customer Interaction(if direct) a. Develop effective relationship with customer 3. Team Management a. Develop & maintain a motivated productive team b. Develop select subordinates to take on higher roles within one year c. Complete appraisal on time with regular to subordinates

Code: R2 Measurement Meet all project milestones as planned No. of review comments on DS to be less than defined target based on size of project. No. of review comments on code No. of NCs on Testing, Documentation & Coding standards  Defect density norms defined by SQA  Leakage of errors from one phase to another (target to be defined based on FP count/size of project) e.g. Zero Design related error leakage to R1 ST stage; Design related error leakage to construction phase less than defined %  Minimum errors at UAT stage – as per proposal or as defined at beginning of project No. of –ve deviations Compliance to documentation and coding standards Ensure completion of modules within planned effort Ensuring acceptance of deliverables from Customer Customer to become a Happy customer No. of –ve escalations or ambiguity Employee qualitative Level of communication/information dissemination within team Develop at least one backup for the PL role who can operate independently Performance every Quarter or at end of project, whichever is earlier

Timely & immediate where required 4. ReUse a. Meet targeted ReUse components in a project Target as agreed in Cut phase / Customer meeting 5. PrimeSourcing Initiatives a. On-site T&M Time Sheet Entry to be captured, approved  100% compliance in the same week. b. Approval of Time Sheet to be obtained in the same week  0% slippage for invoicing purposes. c. PeopleSoft updates by individuals  Change of project should be reflected within 2 working days of the new project’s start d. RRTS system utilization & updates to be on-line e. “Compliance” f. Project Completion, Case Study & Knowledge Sharing to be done within 1 month of project’s closure. g. PID Application h. PID Extensions i. PID Closure (Engineering) Below the Line item Ideating & Thought Leadership by writing articles & accepting speaker slots during events

1.

  

0% slippage 100% 100%



0% resources deployment before PID application.



To be initiated before expiry



Within one month of project’s end.

# of articles committed v/s actual