Hello,
the following is the KRA developed by myself for the engineering grades followed in my Organization. I would request you to evaluate the same and help me with valuable comments.
At our Organization we follow three engineering grades MTS , SMTS and PMTS, and each grades has 2-3 levels.
KEY RESPONSIBILITY AREA
MTS:
Definition:Provide technical advice to other roles on component architecture, design and technology alternatives.
Planning:Estimate tasks, define detailed schedules, evaluate technologies, develop prototypes, contribute to design issues.
Development: Develop product and its elements, build internal releases, work with testers
Delivery:Repair reported problems and bugs, bring documentation up to release standards.
Evolution: Fix bugs, start new cycle for next version, transition to maintenance/Customer support
Roles & Responsibilities•Code/ develop applications to program specifications by:
oGrasping the functional requirements and understanding the detailed application design.
oAdhering to agreed time frames
oMeeting agreed standards and best practices
•Understand and apply application processes, their standards and guidelines
•Write unit test code, using tools and writing test cases
•Support deployed solutions (debugging and fixing problems)
•Participate in analyzing customer requirements and reviewing code
•Play the role of a technical lead when and where required and guide small groups
Take-up complete ownership of the work assigned in terms of quality and timeliness.
SMTS:
Definition:Provide technical advice to other roles on system architecture, design and technology alternatives.
Planning:Map functional spec, and non-functional requirements onto 1 or more system structures.
Development:Define and control subsystem interfaces; insure integratability with COTS elements.
Delivery:Resolve integration bugs, support release process as needed.
Evolution: Transition knowledge to lead maintainer, plan for next cycle.
Roles & Responsibilities:
•Platform development: Lead a team of engineers in the development of major Platform elements and drive their adoption into business applications
•Platform definition:
oInteract with external and internal customers to understand the needs
oTranslate the business requirements into high level design specifications
oPropose and drive new strategic directions for the Platform
oSales and client management: Participate in pre-sales activities such as building proposals. Address technology concerns and issues of current clients
•Process: Contribute to the definition of the company's development processes, and ensure that the team adheres to them
•Take up responsibility of managing the project in the absence of the project manager
•Setup architecture and design guidelines to enforce best practices across the projects and consult with other teams to share knowledge
•Promote code reuse by componentizing software and continuous refactoring; support and promote Aelix’s platform strategy
Mentor and manage team members, by giving constant on the job feedback and by providing guidance
PMTS:
Definition: Define project objectives, charter and organization.
Planning: Draft functional spec, create project plan and schedule for development, set ship date.
Development: Track and control project, and changes, issues, risks, etc.
Delivery:Coordinate release process
Evolution: Start definition of new version, analyze user surveys.
Roles & Responsibilities:
•Clearly defining project roles and responsibilities, escalation paths and ownership
•Actively participating in creation of specifications; overseeing and ensuring validation of the technical architecture/ specifications
•Establishing good project metrics, exit criteria by deliverable and project phase
•Establishing a scope management process
•Sourcing the Aelix’s team to construct project team
•Managing project execution remotely (offshore development)
•Conducting periodic project meetings with client and project team
•Ensuring quality of the end deliverables
•Managing day-to-day team and personnel issues
•Maintaining project costing metrics, comparing to proposal and taking necessary corrective action
•Staging and executing User Acceptance of the end deliverable
•Establishing and executing the roll out strategy
•Adherence to processes and execution metrics
•Customer expectation management
•Preparing project reports, plan risks & issues, and define scope
Adapting a project execution structure and process from a base established model
regards,
Veena Jain
the following is the KRA developed by myself for the engineering grades followed in my Organization. I would request you to evaluate the same and help me with valuable comments.
At our Organization we follow three engineering grades MTS , SMTS and PMTS, and each grades has 2-3 levels.
KEY RESPONSIBILITY AREA
MTS:
Definition:Provide technical advice to other roles on component architecture, design and technology alternatives.
Planning:Estimate tasks, define detailed schedules, evaluate technologies, develop prototypes, contribute to design issues.
Development: Develop product and its elements, build internal releases, work with testers
Delivery:Repair reported problems and bugs, bring documentation up to release standards.
Evolution: Fix bugs, start new cycle for next version, transition to maintenance/Customer support
Roles & Responsibilities•Code/ develop applications to program specifications by:
oGrasping the functional requirements and understanding the detailed application design.
oAdhering to agreed time frames
oMeeting agreed standards and best practices
•Understand and apply application processes, their standards and guidelines
•Write unit test code, using tools and writing test cases
•Support deployed solutions (debugging and fixing problems)
•Participate in analyzing customer requirements and reviewing code
•Play the role of a technical lead when and where required and guide small groups
Take-up complete ownership of the work assigned in terms of quality and timeliness.
SMTS:
Definition:Provide technical advice to other roles on system architecture, design and technology alternatives.
Planning:Map functional spec, and non-functional requirements onto 1 or more system structures.
Development:Define and control subsystem interfaces; insure integratability with COTS elements.
Delivery:Resolve integration bugs, support release process as needed.
Evolution: Transition knowledge to lead maintainer, plan for next cycle.
Roles & Responsibilities:
•Platform development: Lead a team of engineers in the development of major Platform elements and drive their adoption into business applications
•Platform definition:
oInteract with external and internal customers to understand the needs
oTranslate the business requirements into high level design specifications
oPropose and drive new strategic directions for the Platform
oSales and client management: Participate in pre-sales activities such as building proposals. Address technology concerns and issues of current clients
•Process: Contribute to the definition of the company's development processes, and ensure that the team adheres to them
•Take up responsibility of managing the project in the absence of the project manager
•Setup architecture and design guidelines to enforce best practices across the projects and consult with other teams to share knowledge
•Promote code reuse by componentizing software and continuous refactoring; support and promote Aelix’s platform strategy
Mentor and manage team members, by giving constant on the job feedback and by providing guidance
PMTS:
Definition: Define project objectives, charter and organization.
Planning: Draft functional spec, create project plan and schedule for development, set ship date.
Development: Track and control project, and changes, issues, risks, etc.
Delivery:Coordinate release process
Evolution: Start definition of new version, analyze user surveys.
Roles & Responsibilities:
•Clearly defining project roles and responsibilities, escalation paths and ownership
•Actively participating in creation of specifications; overseeing and ensuring validation of the technical architecture/ specifications
•Establishing good project metrics, exit criteria by deliverable and project phase
•Establishing a scope management process
•Sourcing the Aelix’s team to construct project team
•Managing project execution remotely (offshore development)
•Conducting periodic project meetings with client and project team
•Ensuring quality of the end deliverables
•Managing day-to-day team and personnel issues
•Maintaining project costing metrics, comparing to proposal and taking necessary corrective action
•Staging and executing User Acceptance of the end deliverable
•Establishing and executing the roll out strategy
•Adherence to processes and execution metrics
•Customer expectation management
•Preparing project reports, plan risks & issues, and define scope
Adapting a project execution structure and process from a base established model
regards,
Veena Jain
3 Attachment(s) [Login To View]