Site Tools


Hotfix release available: 2024-02-06a "Kaos". upgrade now! [55.1] (what's this?)
New release available: 2024-02-06 "Kaos". upgrade now! [55] (what's this?)
Hotfix release available: 2023-04-04a "Jack Jackrum". upgrade now! [54.1] (what's this?)
New release available: 2023-04-04 "Jack Jackrum". upgrade now! [54] (what's this?)
Hotfix release available: 2022-07-31b "Igor". upgrade now! [53.1] (what's this?)
Hotfix release available: 2022-07-31a "Igor". upgrade now! [53] (what's this?)
New release available: 2022-07-31 "Igor". upgrade now! [52.2] (what's this?)
New release candidate 2 available: rc2022-06-26 "Igor". upgrade now! [52.1] (what's this?)
New release candidate available: 2022-06-26 "Igor". upgrade now! [52] (what's this?)
Hotfix release available: 2020-07-29a "Hogfather". upgrade now! [51.4] (what's this?)
internal:pm:team_kpa

Senior Development Manager

ObjectiveDescriptionMeasurement
Project Management (50%)Assign/Monitor/Prioritize Tickets to developersIt will be measured based on mantis tickets.
Issue Escalation and ResolutionIt will be measured based on how pro-actively you communicate the problems and provide solutions
Ensure team members complete Tasks [Mantis tickets] on timeIt will be measured based on mantis tickets.
Ensure the respective team member enters the timesheet weeklyEnsure Timesheet entry by all your team members should be completed every Monday before EOD.
Ensure weekly Release to QA is completed on timeIt will be measured based on mantis tickets.
Ensure code reviews are performed by LeadsIt will be measured based on the issues raised, the tickets re-opened.
Ownership of product deliverables, process and teamIt will be measured based on the issues raised, the tickets re-opened.
Come up with innovative solutions, feedback, good suggestion to improve the process, product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Conduct Code review of Tickets completed by developersIt will be measured based on the issues raised, the tickets re-opened.
Facilitate and moderate meetings as required [Standup, “Show and Tell”, etc.]Feedback from manager
Contribute to RFP's and wiki pageFeedback from manager
Part of New Engagement InitiativeFeedback from manager
People Management (30%)Ensuring new resource undergoes the identified learning path and comes onboard within the agreed timelines100% Compliance
Team training>= 6 training days per team member per year
Groom/Hires LeadershipAtleast 10% of teams to be identified for Grooming
Certifications Atleast 5% of teams to be certified in Testing Certifications
HR process compliance on time (KPAs & Appraisal)>= 90%
Inducting new resource, team building and maintaining team moraleActuals
Attrition Management< 10% overall
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

Principal Software Engineer

ObjectiveDescriptionMeasurement
Management of non-functional requirements (25%)Technology selection, Architecture Definition and Architecture Collabration It will be measured by the frameworks defined so far.
Assist in InterviewsIt will be measured based on how many times you helped in hiring new resource for product team
Write technical design documents for all complex features and publish it in wikiIt will be reviewed by other tech lead and PM.
Build POC and deliver it for approval on timeIt will be measured against number of demos given to PM/CTO.
Defining Coding Standards and Implementing the best practices in CodingIt will be reviewed by tech lead and PM during the code review process.Your contribution on coding standard should be published in wiki and it will be reviewed by PL/PM
Ownership and Leadership (25%) Taking end to end ownership for the given task.It will be measured using mantis tickets based on the features.
Leading the team to build new features effectively It will be measured by features/framework implemented.
Escalations & Solutions It will be measured by how effectively the resource is escalating the offshore problem to the PM/CTO.
Team Collaboration & Innovation (30%) Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Provided necessary technical inputs to other teams (EONE & Impl team ) It will be measured by how many times resource helped dev team when they faced a technical problem.
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Coaching and Mentoring (20%) Provide necessary induction training to the new employeeIt can be measured by the number of resources groomed
Provide proper technology training (if required) It can be measured by the number of resources groomed
Efficient team building Make sure team is happy about what they are doing towards meeting the organization goal.
Efficient Resource Utilization Monitor each resource and make sure that their time is utilized effectively.

Product Manager

ObjectiveDescriptionMeasurement
Team Management (30%)Assign/Monitor/Prioritize Tickets to Product AnalystIt will be measured based on mantis tickets.
Conduct review of Tickets/Documentation completed by Product AnalystIt will be measured based on the issues raised, the tickets re-opened.
Issue Escalation and ResolutionIt will be measured based on how pro-actively you communicate the problems and provide solutions
Collaborate with different teams for Release Plan / RoadmapIt will be measured based on mantis tickets released and the feedback from the stakeholders
Training and Mentoring team membersIt will measured based on how you train your team member in new technology and functionalities
Assist in InterviewsIt will be measured based on how many times you helped in hiring new resource for product team
Analysis/Design (30%)Own and drive the requirements phase by participating in requirements gathering and guiding the delivery team/QA to translate business/functional requirements into technical specifications/ test cases. Develop prototypes to capture and validate business/user requirements It will measured based on the feedback/ review from stakeholders The analysis/mockups compliance should be greater than 95% as per requirements
Documentation of business requirements (Features, Functionality, Use cases, Mockups, Process, Business Rules and Data/UI Flows). It will measured based on the feedback/ review from stakeholders
Maintenance of features tickets in Mantis (Tickets work flow/Tracking/Issues) and help the Product Manager in defining the Release Plan/Roadmap.It will measured based on the feedback/ review from stakeholders
Analyze and identify gaps in requirements / proactive enhancements Perform functional testingIt will measured based on the feedback/ review from QA/Product Manager Suggest at least 10% new test cases for each requirement reviewed.
Team Collaboration & Innovation (30%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Helping other team membersIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative Features, feedback, suggestion to improve the product quality and featuresIt will measured by getting the feedback from the stakeholders
Keep domain knowledge up to date by reading and prototyping with new products / featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/business processes in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

Product Analyst

AreasDescriptionMeasurement
Analysis(20%)Own and drive the requirements phase by participating in requirements gathering and guiding the delivery team/QA to translate business/functional requirements into technical specifications/ test cases. Develop prototypes to capture and validate business/user requirementsIt will measured based on the feedback/ review from stakeholders The analysis/mockups compliance should be greater than 95% as per requirements
Analyze and identify gaps in requirements / proactive enhancements Perform functional testingIt will measured based on the feedback/ review from QA/Product Manager.
Design(20%)Documentation of business requirements (Features, Functionality, Use cases, Mockups, Process, Business Rules and Data/UI Flows).It will measured based on the feedback/ review from PM/Dev
Innovation(20%)Come up with innovative Features, feedback, suggestion to improve the product quality and featuresIt will measured by getting the feedback from the stakeholders
Keep domain knowledge up to date by reading and prototyping with new products / featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/business processes in group meetings (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Finding new innovative ways of reducing time / resources in repetitive tasks being done in your or other teams or tasks which are cumbersome.It will measured based on the feedback from PM
Team Collaboration(20%)Ownership - Should be able to own feature analysis/team coordination(internal and external) and work with the dev team to provide zero defect featureIt will be reviewed by PM when tasks are assigned
Effective internal & external team interaction and collaborationIt will measured by getting the feedback from the Team Managers.
Project management of tasks / featuresIt will measured based on the feedback/ review from PM
Internal system(20%)Advance notification of LeaveAny planned leave should be communicated before 15 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Status Mails & Daily ticket updatesSend status mails and keep the stakeholders informed about the daily/weekly and project progress. All relevant tickets you are working on need to be updated.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
Maintenance of features tickets in Mantis (Tickets work flow/Tracking/Issues) and help the Product Manager in defining the Release Plan/Roadmap.It will measured based on the feedback/ review from stakeholders
Define new process guideliness based on needsIt will measured based on the feedback/ review from PM

Team-Product Lead

ObjectiveDescriptionMeasurement
Team Management (40%)Estimate/Assign/Monitor Tickets to developersIt will be measured based on mantis tickets.
Conduct Code review of Tickets completed by developersIt will be measured based on the issues raised, the tickets re-opened.
Issue Escalation and ResolutionIt will be measured based on how pro-actively you communicate the problems and provide solutions
Help release team on code deployment and QA team to clarify their doubts on product functionality and configurationIt will be measured based on mantis tickets and the feedback from the release and QA team
Training, Mentoring and pair programming with team membersIt will measured based on how you train your team member in new technology and functionalities
Ownership - Should be able to own feature development/team coordination/release related activities and work with the team to provide zero defect codeIt will be reviewed by PM when tasks are assigned
Assist in InterviewsIt will be measured based on how many times you helped in hiring new resource for product team
Development (40%)Proper understanding of the requirements and producing zero-defect code for all assigned ticketsIt will be measured based on the issues raised, the tickets re-opened.
Tests cases should be written for all features/issues and all checkingIt will be reviewed by other tech lead and PM during the code review process.
Write technical design documents for all complicated features and published it in wikiIt will be reviewed by other tech lead and PM.
Deliver the features/issues on timeIt will be measured against the estimated time in the mantis tickets.
Follow best coding practice and contribute to coding standardsIt will be reviewed by tech lead and PM during the code review process.Your contribution on coding standard should be published in wiki and it will be reviewed by PL/PM
Provide proper release notes and detailed information for code deploymentThis will be measured from the deployment failure metrics report and issues reported by QA
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

Developer

ObjectiveDescriptionMeasurement
Development (80%)Proper understanding of the requirements and producing zero-defect code for all assigned ticketsIt will be measured based on the issues raised, the tickets re-opened.
Tests cases should be written for all features/issues and all checkingIt will be reviewed by tech lead and PM during the code review process.
Write technical design documents for all complicated features and published it in wikiIt will be reviewed by tech lead and PM.
Deliver the features/issues on timeIt will be measured against the estimated time in the mantis tickets.
Follow best coding practice and contribute to coding standardsIt will be reviewed by tech lead and PM during the code review process.Your contribution on coding standard should be published in wiki and it will reviewed by PL/PM
Provide proper release notes and detailed information for code deploymentThis will be measured from the deployment failure metrics report and issues reported by QA
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Helping other team members and pair programmingIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

Build & Release Manager

ObjectiveDescriptionMeasurement
Build/Release/Deployment (80%)a) Work with Product and Project delivery groups on release milestone planning, Establish Release Management Policy, Release cycle and standard release practices.b) Ensure successful completion of the Planned/On Demand Release Requests for overall products, as per release schedule slot c) QA/Staging/Demo Release Deployment for product d) Release build and QA Release Deployment for Support Projects e) Release build and QA Release Deployment for Implementation Projects. f) Review Release criteria (including release notes documentations, deliverables packaged, QA test reports, deployment dependencies) g) Handle Release Shipment, Communications and ensure successful deployment at UAT environment with devops team. h) Ensure successful closure of each Release up to production deployment with production support team.Percentage of Successful Release (more than 95%)
a) Establish Successful implementation of CI Server env for software development projects, b) Ensure successful flow of unit testing based integration build and deployment at iDev through CI server. Successful completion of CI Tickets assigned. (more than 95%)
a) Implement RM Process Standards on software development Projects b) Contribute to improving RM Process Standards c) Contribute to document process standards at dokuwiki page. d) Implementation of RM Tools for Software Development Projects e) Contribute to enhancement of RM tools and support for dev team.Successful completion of RM Process Tickets assigned. (more than 95%)
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Contribute to technical articles on Release Practices, Contribute to research, POC and validation of new tools and technologies relevant for Release Management.No. of RM Technical Articles/Discussion Sessions contributed (more than 3 sessions in a quarter)
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
Training and Mentoring team membersIt will measured based on how you train your team member in process, tools and technology.
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

Build & Release Engineer

ObjectiveDescriptionMeasurement
Build/Release/Deployment (80%)Complete all of the Planned/On Demand Product Release Requests as per release schedule.Percentage of Successful Release. (more than 95%)
Contribute to SCM support for dev team a) Contribute to SVN implementation for Product Repository. b) creation of branching/tagging for releases b) resolving issues with creating/deleting files c) resolve issues with branching/tagging of baseline d) regular/periodic cleanup of source repositorySuccessful completion of SCM Tickets assigned. (more than 95%)
Contribute to CI server support, a) creation of new build job at CI Server b) maintaining existing build job at CI Server c) migration of build jobs to different software version control servers d) Integration of JS and PHP unit test tools with CI server. d) ensure availability of ci server, e) provide CI server system support for dev team.Successful completion of CI Tickets assigned.(more than 95%)
a) Contribute to improving RM Process Standards b) Contribute to document process standards at dokuwiki page.Successful completion of RM Process Tickets assigned. (more than 95%)
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

QA Manager

ObjectiveDescriptionMeasurement
QA Management (40%)Assign/Monitor Tickets to QA EngineersIt will be measured based on mantis tickets.
Conduct Test Case review of Tickets completed by QA EngineersIt will be measured based on the issues raised, the tickets re-opened.
Issue Escalation and ResolutionIt will be measured based on how pro-actively you communicate the problems and provide solutions
Help release team on code deployment and QA team to clarify their doubts on product functionality and configurationIt will be measured based on mantis tickets and the feedback from the release and QA team
Training, mentoring and pair testing with team membersIt will measured based on how you train your team member in new technology and functionalities
Assist in InterviewsIt will be measured based on how many times you helped in hiring new resource for product team
QA Process [40%]Proper understanding of the requirements and Test case creation, execution and defect logging for all assigned tickets on-timeIt will be measured based on the Test Cases/ Scenario created, executed and defect logged against the feature and feedback
Test Cases/Scenarios to be prepared based on the documentation provided to cover the Functional, UI aspects and Regression of the requirements.It will be reviewed by QA Manager and Product Management group and measured based on review comments for the assigned ticket
Reporting issues and screenshots with proper description effectively in Mantis.It will be measured based on the feedback from Team-Product Lead and developers
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report

QA Engineer

ObjectiveDescriptionMeasurement
QA Process [80%]Proper understanding of the requirements and Test case creation, execution and defect logging for all assigned tickets on-timeIt will be measured based on the Test Cases/ Scenario created, executed and defect logged against the feature and feedback
Test Cases/Scenarios to be prepared based on the documentation provided to cover the Functional, UI aspects and Regression of the requirements.It will be reviewed by QA Manager and Product Management group and measured based on review comments for the assigned ticket
Reporting issues and screenshots with proper description effectively in Mantis.It will be measured based on the feedback from Team-Product Lead and developers
Team Collaboration & Innovation (10%)Effective team interaction and collaborationIt will measured by getting the feedback from the Team-Product Lead and Managers
Helping other team members and pair testingIt will measured by getting the feedback from the Team-Product Lead and Managers
Come up with innovative solutions, feedback, good suggestion to improve the product quality and featuresIt will measured by getting the feedback from the Team-Product Lead and Managers
Keep technical knowledge up to date by reading, experimenting and prototyping with new tools and techniquesIt will measured by getting the feedback from the Team-Product Lead and Managers
Prepare and present features/technical solutions in group setting (show & tell and brown bag session)It will measured by getting the feedback from the Team-Product Lead and Managers
Internal system(10%)Advance notification of LeaveAny planned leave should be communicated before 7 working days Unplanned leave should be communicated over the phone before start of the working hours
MeetingsAttend all meetings on-time If you cannot attend, please notify your manager prior to the meeting If you are staying late previous day and cannot attend the next day stand-up meeting, then kindly send your reporting manager a email update about the task completed and plans for next day
Log Timesheet on-timeTimesheet entry should be completed every Monday before EOD.
Flexible in adjusting the work schedule on need basis to meet project goalsIt will measured by getting the feedback from the Team-Product lead and Managers
CertificationUndergo certification applicable to your role
Should be available at work at least for 8 hoursThis will be measured from access log report
internal/pm/team_kpa.txt · Last modified: 2024/06/12 07:53 by 114.119.158.74