Common EIT Roles

Welcome to the initial version of the EITBOK wiki. Like all wikis, it is a work in progress and may contain errors. We welcome feedback, edits, and real-world examples. Click here for instructions about how to send us feedback.

 

Role Name	Description
Access manager	The access manager executes policies defined in information security management and grants authorized users the right to use a service, while preventing access to non-authorized users.
Application analyst	The application analyst manages applications throughout their lifecycle. This role plays an important part in the application-related aspects of designing, testing, operating, and improving EIT services. It is also responsible for developing the skills required to operate the applications required to deliver EIT services.
Application developer	The application developer is responsible for making available applications and systems that provide the required functionality for EIT services. This includes the development and maintenance of custom applications as well as the customization of products from software vendors.
Application owner	An application owner is the individual or group with the responsibility to ensure that the program or programs, which make up the application, accomplish the specified objective or set of user requirements established for that application, including appropriate security safeguards. See http://itlaw.wikia.com/wiki/Application_owner.
Architect	An EIT architect is responsible for the design of a computing system and the logical and physical interrelationships between its components. The architecture specifies the hardware, software, access methods, and protocols used throughout the system. Larger organizations may opt to introduce specialist architect roles such as business architect, application architect, information architect, and infrastructure architect.
Architecture team	See Architect.
Availability manager	The availability manager is responsible for defining, analyzing, planning, measuring, and improving all aspects of the availability of EIT services and for ensuring that all EIT infrastructure, processes, tools, roles, and related items are appropriate for the agreed service-level targets for availability.
Backup process manager	The backup process manager is responsible for defining and ensuring the viability of the enterprise's backup processes. Backup and recovery are essential to ensuring service continuity. The recovery procedures are defined first, and then backup procedures and their frequency are based on the needs of the recovery procedures.
Business analyst/SME	Business analysts work as liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.
Business architect	A business architect is concerned with developing and maintaining business capabilities of the enterprise in line with the corporate strategy, as well as contributing to the business strategy and plans.
Business architecture team	See Business architect.
Business continuity manager	The business continuity manager identifies potential threats to an organization and the impacts to business operations those threats, if realized, might cause, which provides a framework for building organizational resilience.
Business executive	A business executive is a person appointed and given the responsibility to manage the affairs of an organization and the authority to make decisions within specified boundaries. See http://www.businessdictionary.com/definition/executive.html.
Business management team	See Business manager.
Business manager	1. Person authorized to grant access to a service or application. 2. A user representative authorized to negotiate with EIT on behalf of the business area.
Business owner	See Business product owner.
Business partner	A business partner is a commercial entity with which another commercial entity has some form of alliance. Businesses that cooperate, to any degree, such as a computer manufacturer who works exclusively with another company who supplies them with parts. See http://www.businessdictionary.com/definition/business-partner.html.
Business product owner	This role is not clearly differentiated from that of the product owner (in agile terms) or the product manager (in commercial software companies). The product owner (PO) is the member of the team responsible for defining stories and prioritizing the team backlog so as to streamline the execution of program priorities, while maintaining conceptual and technical integrity of the features or components the team is responsible for. See scaledagileframework.com/product-owner/.
Business relationship mgr/mgt team	The business relationship manager is responsible for maintaining a positive relationship with customers, identifying customer needs, and ensuring that the service provider is able to meet these needs with an appropriate catalog of services.
Business subject matter expert	See Subject matter expert.
Business unit Business unit lead	A logical element or segment of a company (such as accounting, production, or marketing) representing a specific business function, and a definite place on the organizational chart, under the domain of a manager. Also called department, division, or functional area. See www.businessdictionary.com/definition/business-unit.html.
Capacity manager	The capacity manager is responsible for ensuring that services and infrastructure are able to deliver the agreed capacity and performance targets in a cost-effective and timely manner, considers all resources required to deliver the service, and plans for short, medium, and long-term business requirements.
Change advisory board (CAB)/ Change control board (CCB)/ Change board	A group of people that advises the change manager in the assessment, prioritization, and scheduling of changes. This board is usually made up of representatives from all areas within the EIT organization, the business, and third parties such as suppliers. Strictly speaking, the CCB is responsible for managing the change control process. The CCB is aided by the CAB, consisting of subject matter experts (SMEs) who can advise on the risk of making (or even not making) a change. Some organizations also have a CCB that focuses on specific configuration changes such as firewall and port configurations. The CCB is aided by the release coordination function, which is responsible for managing the change calendar. A subset of the CAB, the emergency change advisory board (ECAB), is sometimes used to make decisions about clear-cut, high impact emergency changes. Membership of the ECAB may be decided at the time a meeting is called, and depends on the nature of the emergency change.
Change board member	See Change advisory board.
Change manager (process)	The change manager controls the lifecycle of all changes, and receives guidance on potential impacts from the change advisory board.
Chief compliance officer (CCO)	A chief compliance officer (CCO) is a corporate official in charge of overseeing and managing compliance issues within an organization, ensuring, for example, that a company is complying with regulatory requirements and that the company and its employees are complying with internal policies and procedures.
Chief data officer (CDO)	A chief data officer (CDO) is a corporate officer responsible for enterprise-wide governance and utilization of information as an asset, via data processing, analysis, data mining, information trading, and other means. CDOs report mainly to the chief executive officer (CEO).
Chief executive officer (CEO)	The chief executive officer (CEO), the highest-ranking corporate officer, is responsible for making managerial decisions and determining the direction of the corporation.
Chief financial officer (CFO)	The chief financial officer (CFO) is a corporate officer primarily responsible for managing the financial risks of the corporation. This officer is also responsible for financial planning and record keeping, as well as financial reporting to higher management.
Chief information officer (CIO)	Chief information officer (CIO) is an executive job title commonly given to the person at an enterprise in charge of EIT strategy and the computer systems required to support an enterprise's objectives and goals.
Chief risk officer (CRO)	The chief risk officer (CRO) is the corporate executive tasked with assessing and mitigating significant competitive, regulatory, and technological threats to an enterprise's capital and earnings. The position is sometimes called chief risk management officer or simply risk management officer.
Chief technology officer (CTO)	A chief technology officer (CTO), sometimes known as a chief technical officer, is an executive-level position in a company or other entity whose occupation is focused on scientific and technological issues within an organization.
C-level officers	The highest-level executives in senior management usually have titles beginning with "chief" forming what is often called the C-suite. Such officers are chief executive officer (CEO), chief operations officer (COO), chief financial officer (CFO), and so on.
Communications manager	Communications managers are responsible for conveying an organization's internal and external messages. Communications management is the systematic planning, implementing, monitoring, and revision of all channels of communication within an organization, and between organizations; it also includes the organization and dissemination of new communication directives. May include marketing communications managers.
Compliance manager/ Agent/ Auditor (external)	The compliance manager's responsibility is to ensure that appropriate standards and guidelines are used, that proper, consistent accounting or other practices are being employed, and that external legal requirements are met.
Configuration manager	The configuration manager is responsible for maintaining current information about all configuration items required to deliver EIT services, including maintaining a logical model of the components of the EIT infrastructure (CIs) and their associations. This position should not to be confused with the software configuration manager, who controls changes to software under development until it is released to operations.
Consumer	End user of a service or solution.
Continual service improvement (CSI) manager	The continual service improvement (CSI) manager is responsible for managing improvements to EIT service management processes and EIT services by continually measuring the performance of services and design improvements to processes, services, and infrastructure in order to increase efficiency, effectiveness, and customer satisfaction. Continual service improvement follows the tenets of total quality management.
Contracts manager	The role of the contracts manager is to develop and implement procedures for contract management and administration in compliance with company policy; as appropriate, to contribute to or influence company policies and to monitor compliance by company employees with established procedures.
Customer	End user of a service or product.
Data architect	A data architect is responsible for designing, creating, deploying, and managing an organization's data architecture. A data architecture is composed of models, policies, rules, or standards that govern which data is collected, and how it is stored, arranged, integrated, and put to use in data systems and in organizations.
Data management	1. Data resource management is the development and execution of architectures, policies, practices, and procedures that properly manage the full data lifecycle needs of an enterprise (definition from DAMA International). 2. Administrative process by which the required data is acquired, validated, stored, protected, and processed, and by which its accessibility, reliability, and timeliness is ensured to satisfy the needs of the data users. See www.businessdictionary.com/.
Data modeler	A data modeler is responsible for what is often the first step in database design and object-oriented programming, as the designers first create a conceptual model of how data items relate to each other. Data modeling involves a progression from conceptual model to logical model to physical schema.
Data quality team	This team is responsible for data quality management, which entails the establishment and deployment of roles, responsibilities, policies, and procedures concerning the acquisition, maintenance, dissemination, and disposition of data.
Demand manager	The demand manager is responsible for understanding, anticipating, and influencing customer demand for services and works with capacity management to ensure that the service provider has sufficient capacity to meet the required demand.
Deployment manager	The deployment manager oversees the plans and execution of software and hardware updates, migration, and remote maintenance projects tasks for enterprise information systems.
Disaster recovery team	The disaster recovery team consists of members who are responsible for restoring service across the organization. Facilities—General responsibility Hardware—Replacing and restoring all servers, desktops, and other devices Applications/data—Obtaining backups, restoring data, and loading software images Network—Replacing and restoring firewall, routers, cabling, and other equipment to make data available External services—Restoring power, Internet, and phone services Engineering—Ensuring that the environment is safe and suitable for work Finance—Providing approval for spending and documentation for insurance Human resources—Contacting people to report or not report, and providing support Media relations—Contacting media, coordinating information to public Management—Liaising with boards, making critical decisions, and removing obstacles
EIT analyst	This role covers a wide spectrum of specific analyst roles, including technology, business, database, networking, programming, and systems analysts.
EIT community	This term may apply to the people in the EIT organization or to the wider group of professionals in information technology who work for private companies, government agencies, educational institutions, and any other entity that relies on computers for their daily operations. They install computer servers, design computer programs, provide technical support to staff members, install networks, and keep business and customer data secure.
EIT engineer	This broad term may refer to anyone who is employed in the use of any computers, storage, networking, and other physical devices, infrastructure, and processes to create, process, store, secure, and exchange all forms of electronic data. Generally, it applies to all EIT staff.
EIT management team	Members of this team include all managers responsible for the process of planning, organizing, and executing activities for the successful achievement of the EIT organizations' specific information technology goals.
EIT manager	See EIT management team.
EIT product manager	This role has long existed in software and hardware product companies, but is emerging in EIT. Responsibilities include: Managing the entire product line lifecycle from strategic planning to tactical activities. Specifying customer requirements for current and future products by conducting market research in conjunction with on-going discussions with business units to determine and prioritize needed functionality. Driving a solution set across development through market requirements, product contract, and positioning in the EIT portfolio. Developing and implementing a company-wide launch plan, working with all departments to execute. Analyzing potential partner relationships for the product.
EIT service continuity manager	The EIT service continuity manager is responsible for managing risks that could seriously impact EIT services by reducing the risks to an acceptable level and planning for the recovery of EIT services, ensuring that the EIT service provider can provide minimum agreed service levels in cases of disaster. (See also Risk manager.)
Enterprise architect	See Architect.
Enterprise risk manager	The risk manager is responsible for identifying, assessing, and controlling risks by analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.
Executive sponsor	The business person at the organization's executive level who is responsible for the success of the project.
Facilities manager	The facilities manager is responsible for managing the physical environment, for example power and cooling, building access management, and environmental monitoring—anything that is part of the physical environment where the EIT infrastructure is located.
Financial manager	The financial manager is responsible for managing an EIT service provider's budgeting, accounting, and charging requirements.
Governance body	A group of people who formulate policy and direct an institution along with its management (for a specified level in context).
Information security manager	The information security manager is responsible for ensuring the confidentiality, integrity, and availability of an organization's assets, information, data, and EIT services, and is the security management for the entire organization.
Infrastructure owner	The EIT person responsible for the effective functioning of the EIT technologies.
Internal messaging team	The group responsible for timely and accurate communication of changes, events, etc., to the employees of the organization.
Knowledge manager	The knowledge manager's goal is to improve efficiency by reducing the need to rediscover knowledge by ensuring that the EIT organization is able to gather, analyze, store, and share knowledge and information.
Operations manager	The operations manager manages day-to-day infrastructure operations to provide delivery of systems and services in order to meet or exceed agreed services levels.
Operations management team	Supports operations manager.
Operations team member/operations team	Supports operations manager.
Portfolio manager	The portfolio manager provides managers with an inventory of the company's software applications and metrics to illustrate the business benefits of each application to support decisions about building, buying, maintaining, and retiring applications.
Problem manager	The problem manager is responsible for managing the lifecycle of all problems. For this, they maintain information about known errors and workarounds. In ITIL terms, this role differs from incident manager, who is responsible for effective implementation of the incident management process to help restore service to the user and carries out the corresponding reporting. They represent the first stage of escalation for incidents. Incident management handles any unplanned interruption to or quality reduction of an EIT service, whereas problem management handles the root causes of incidents.
Process architect	The process architect is responsible for maintaining the process architecture (part of the enterprise architecture), coordinating all changes to processes, and making sure that all processes cooperate in a seamless way. This role often supports all parties involved in managing and improving processes, in particular the process owners and change managers.
Process owner	A process owner is responsible for ensuring that a given process serves its designated purpose and interfaces appropriately with other processes by sponsorship, design, and continual improvement of the process and its metrics. Larger organizations may have separate process owner and process manager roles, where the process manager has responsibility for the operational management of a process.
Procurement manager	Procurement manager duties include identifying suppliers and comparing prices, specifications, terms, and delivery dates to determine the optimum one to use, preparing purchase orders and subcontracts, responding to internal and supplier inquiries, and reviewing requisition orders to verify accuracy, specifications, and terminology. Must prepare, maintain, and review purchasing records, produce management reports, track the status of requisitions, contracts, and orders, approve bills for payment, monitor contractor performance, calculate the cost of orders, assign invoices to the appropriate accounts, and monitor in-house inventory transfer for project consumption.
Procurement team	See Procurement manager.
Project management office (PMO)	The project management office (PMO) is a group or department in an enterprise that establishes and implements best practices and maintains standards related to project management, planning, and execution. The PMO also serves as an organization's central hub for project documentation, guidance and success metrics. See https://www.techopedia.com.
Project manager	The project manager is responsible for planning, acquiring, and coordinating the resources to complete a given project within the predicted cost, time, and quality estimates.
Quality analyst	A quality analyst is responsible for the systematic examination of the extent to which an EIT product is capable of satisfying stated and implied needs.
Quality manager	The quality manager is responsible for quality management, which includes the processes and activities of the performing organization that determine quality policies, objectives, and responsibilities so that the project satisfies the needs for which it was undertaken. While not limited to testing, quality management sets standards for planning, performing and reporting testing and results.
Quality team	See Quality manager.
Regulatory authority	Any entity whose regulatory requirements demand an organization's adherence to laws, regulations, guidelines, and specifications relevant to its business. Violations of regulatory compliance regulations often result in legal punishment, including federal fines.
Release manager	The release manager is responsible for overseeing and controlling the movement of releases from construction and test to transition and live environments. This role may be performed by a senior software configuration manager. The primary objective is to ensure that the integrity of the live environment is protected and that the correct components—as tested and approved—are released into the proper environments.
Release management team	See Release manager.
Risk manager	This role has the overall responsibility for the identification, assessment, and prioritization of risks (defined in ISO 31000 as the effect of uncertainty on objectives) followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities. Risk management's objective is to ensure that uncertainty does not deflect the endeavor from the business goals.
Security architect	The security architect, more properly the information security architect, is responsible for the enterprise security architecture, providing the conceptual design of the network security infrastructure, related security mechanisms, and related security policies and procedures. The enterprise security architecture links the components of the security infrastructure as one cohesive unit. The goal of this cohesive unit is to protect corporate information.
Security manager	The EIT security manager performs two core functions for the enterprise. The first is overseeing the operations of the enterprise's security solutions through the management of the organization's security analysts. The second is establishing an enterprise security stance through policy, architecture, and training processes. See http://www.itbusinessedge.com/itdownloads/job-description-it-security-manager/88518 accessed 11/11/2016.
Service catalog manager	The service catalog manager is responsible for maintaining the service catalog, ensuring that all information within the service catalog is accurate and up to date.
Service design manager	The service design manager is responsible for producing quality, secure, and resilient designs for new or improved services, as well as producing and maintaining all design documentation.
Service level manager	The service level manager is responsible for negotiating service level agreements (SLAs) and ensuring that they are met, making sure that all EIT service management processes, operational level agreements (OLAs), and underpinning contracts are appropriate for the agreed service level targets. The service level manager also monitors and reports on service levels.
Service manager	The service manager represents all EIT provided services to users and is responsible for overall ABC customer satisfaction with service support and service delivery actions taken to ensure they meet business needs as well as EIT requirements.
Service owner	The service owner is responsible for delivering a particular service within the agreed service levels, typically acting as the counterpart of the service level manager when negotiating operational level agreements (OLAs).
Service portfolio manager	The service portfolio manager decides on a strategy to serve customers in cooperation with the EIT steering group, and develops the service provider's offerings and capabilities.
Service request manager	The duty of providing information to the user is part of the service request management. Its most important actor is the service desk. The service desk is responsible for the acceptance, classification, and routing and reporting of requests.
Service strategy manager	The service strategy manager is responsible for communicating and implementing the service strategy.
Solution architect	The solution architect handles requests for customized operational solutions, consults with business and EIT staff to identify solution requirements, and coordinates solution build activities with the release analyst.
Solution architecture team	See Solution architect.
Solution developer	Solution developers play a key role in the design, installation, testing, and maintenance of application software, and leverage information technology to solve business problems through decision support, analytics, and data warehousing systems. Based on project requirements, may be responsible for coding entirely new custom software applications, or may use "off the shelf" software that may require modification and integration into an existing system to meet business needs.
Solution management team	Solution management works with project stakeholders (including customers) to create and maintain the product's vision, roadmap, and value stream, and to make sure that requirements for third-party capabilities are well-understood. They work with customers to build and prioritize the solution backlog.
Stockholder	1. Intended meaning in this context: An individual, group, or organization that holds one or more shares in a company, and in whose name the share certificate is issued. Also called shareholder. 2. British: A company or individual who holds supplies for manufacturers. See http://www.businessdictionary.com/definition/stockholder.html.
Subject matter expert (SME)	A subject matter expert (SME) is defined as follows: person with direct knowledge of what is done in the job, what knowledge, skills, abilities, and other characteristics (KSAOs) are required, and the general background of persons who are able to do the job successfully. These may include those currently doing the job, recent incumbents, those who supervise others doing the job, and other acknowledged job experts. See http://definitions.uslegal.com/s/subject-matter-expert/.
Supplier manager	The supplier manager is responsible for ensuring that suppliers deliver value, making sure that contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.
Support team (1st, 2nd, 3rd level)	1st level support The responsibility of 1st level support is to register and classify and document received incidents in the appropriate database and to supply known corrective advice or workarounds. If no solution can be provided, the incident is transferred to 2nd level support. 1st level support also processes service requests and keeps users informed about their incidents' status at agreed intervals. 2nd level support These are service specialists who provide in-depth technical expertise and may adjust the incident information supplied by 1st level support in the database If necessary, 2nd level support requests external support, e.g., from software or hardware providers. If no solution is achieved, work performed is documented in the database and the incident is passed on to problem management. 3rd level support 3rd level support is typically provided by hardware or software providers (whether in-house or third-party suppliers). Depending on the severity of the incident, the solution may be deferred to the next release or supplied as a hardware replacement, software patch, or full update.
System architect	The system architect is responsible for a comprehensive solution based on principles, concepts, and properties logically related and consistent with each other. The solution architecture has features, properties, and characteristics satisfying, as far as possible, the problem or opportunity expressed by a set of system requirements (traceable to mission/business and stakeholder requirements) and lifecycle concepts (e.g., operational, support) and are implementable through technologies (e.g., mechanics, electronics, hydraulics, software, services, procedures, human activity). See http://sebokwiki.org/wiki/System_Architecture.
System specialist	An information technology specialist applies technical expertise to the implementation, monitoring, or maintenance of EIT systems. Specialists typically focus on a specific computer network, database, or systems administration function. See http://www.webopedia.com/TERM/I/information_technology_specialist.html.
Team manager/lead	The team manager is the leader of a group of employees, overseeing the daily operations of one section within a company. These leaders must perform a wide range of duties that correspond to the kind of team they manage. A team manager may use certain principles to manage the team.
Technical analyst	The technical analyst provides technical expertise and support in the technical aspects of designing, testing, operating, and improving EIT services.
Technology architect	A technical architect is responsible for defining the overall structure of a program or system, ensuring a quality system design that provides good system performance, an effective human-machine interface, optimal operational cost, and flexibility for future change. In addition, the role often provides a focal point for all technical issues and initiatives on the project, ensuring that all components of the technical architecture are properly implemented.
Test manager	The test manager verifies that proper testing occurs for all changes to be released into the production environments, that releases and the resulting services meet the project's release criteria and that EIT operations is able to support the new service.
Test team	See Test manager, Tester.
Tester	The tester is responsible for executing assigned tests, verifying defects, and correctly documenting all related information in the defect database.
Training team	See Trainer, technical.
Trainer, technical	A technical trainer is responsible for preparing, conducting, and evaluating technical training programs, writes literature and materials to be used in programs and designs exercises to enhance lectures, conducts classes regarding safety, security, installation, programming, maintenance, and repair of software, machinery, and equipment.
Transition architect	The person responsible for the successful transition of a process or technology change into the organization.
Transition manager	The transition manager coordinates activities that are needed for service transition: Transition planning and support Change management Release and deployment management Service validation and test Service asset and configuration management End-of-service lifecycle Knowledge management
User (service user)	Consumer or end user of a service or solution.
User experience (UX) manager	UX defines interaction models, user task flows, and UI specifications, and communicates scenarios, end-to-end experiences, interaction models, and screen designs to stakeholders, develops and maintains design wireframes, mockups, and specifications.
User experience team	See User experience (UX) manager.
Verification and validation (V&V) team	Verification and validation are independent procedures that are used together for checking that a product, service, or system meets requirements and specifications and that it fulfills its intended purpose. Validation is intended to ensure that a product, service, or system (or portion thereof, or set thereof) results in a product, service, or system (or portion thereof, or set thereof) that meets the operational needs of the user. Verification is intended to check that a product, service, or system (or portion thereof, or set thereof) meets a set of design specifications.
Vendor	Seller of equipment, services, or other items of interest.