ITIL Tutorials, Templates and advice

Each template comes with:

Microsoft Project plan tried and tested on real projects
100s of tasks covering the whole project lifecycle
Compatible with other Microsoft Project versions
Detailed user guide to configuring your plan
A 30 minute video guide to configuring your plan
Plans for software projects, events, and websites

ITIL Dictionary of Terms

A - Z Dictionary of terms for ITIL. This is the official Dictionary of terms for ITIL, which is a set of practices for IT Service Management. ITIL® is a registered trade mark of AXELOS Limited. View the Agile Dictionary. Managing Successful Programmes (MSP) Dictionary. Project Office Dictionary (P30). Full PRINCE2 glossary of terms. See also Risk Management Dictionary and Project Management Dictionary.

A - acceptance to availability plan | B - back-out to business unit | C - call to customer-facing service | D - dashboard to driver | E - early life support (ELS) to external service provider | F - facilites management to functional escalation | G - H - gap analysis to hot standby | I - identity to ITIL | J - K - job description to known error record | L - lifecycle to live environment | M - maintainability to monitoring | N - near-shore to notional charging | O - objective to overhead | P - pain value analysis to PRojects IN Controlled Environments (PRINCE2) | Q - qualification to quick win | R - RACI to running costs | S - Sarbanes-Oxley (SOX) to system management | T - tactical to Type III service provider | U - underpinning contract (UC) to utility | V - validation to vulnerability | W - warm standby to workload

J to K - job description to known error record

job description

A document that defines the roles, responsibilities, skills and knowledge required by a particular person. One job description can include multiple roles – for example, the roles of configuration manager and change manager may be carried out by one person.

Download FREE Job Descriptions for Project Manager roles

job scheduling

(ITIL Service Operation) planning and managing the execution of software tasks that are required as part of an IT service. Job scheduling is carried out by IT operations management, and is often automated using software tools that run batch or online tasks at specific times of the day, week, month or year.

Kano model

(ITIL Service Strategy) A model developed by Noriaki Kano that is used to help understand customer preferences. The Kano model considers attributes of an IT service grouped into areas such as basic factors, excitement factors, performance factors etc.

Kepner and Tregoe analysis

(ITIL Service Operation) A structured approach to problem solving. The problem is analysed in terms of what, where, when and extent. Possible causes are identified, the most probable cause is tested, and the true cause is verified.

key performance indicator (KPI)

(ITIL Continual Service Improvement) (ITIL Service Design) A metric that is used to help manage an IT service, process, plan, project or other activity. Key performance indicators are used to measure the achievement of critical success factors. Many metrics may be measured, but only the most important of these are defined as key performance indicators and used to actively manage and report on the process, IT service or activity. They should be selected to ensure that efficiency, effectiveness and cost effectiveness are all managed.

knowledge base

(ITIL Service Transition) A logical database containing data and information used by the service knowledge management system.

knowledge management

(ITIL Service Transition) The process responsible for sharing perspectives, ideas, experience and information, and for ensuring that these are available in the right place and at the right time. The knowledge management process enables informed decisions, and improves efficiency by reducing the need to rediscover knowledge. See also Data-to-Information-to-Knowledge-to-Wisdom; service knowledge management system.

known error

(ITIL Service Operation) A problem that has a documented root cause and a workaround. Known errors are created and managed throughout their lifecycle by problem management. Known errors may also be identified by development or suppliers.

known error database (KEDB)

(ITIL Service Operation) A database containing all known error records. This database is created by problem management and used by incident and problem management. The known error database may be part of the configuration management system, or may be stored elsewhere in the service knowledge management system.

known error record

(ITIL Service Operation) A record containing the details of a known error. Each known error record documents the lifecycle of a known error, including the status, root cause and workaround. In some implementations, a known error is documented using additional fields in a problem record.