Change, problem & release management — found from sitemap — Matrix42 Service Management

Cited by

Facts read from this source

• Change types Report an error

  “According to ITIL (Information Technology Infrastructure Library) best practice, change management divides the requests into three different types: Standard Changes, Non-Standard Changes, and Emergency Changes.”

• Change workflows Report an error

  “Workflows are used to describe and automate the various different change management processes, depending on the classification of tickets or any other related information.”

• Change workflow activities Report an error

  “With the provided workflow activities, even complex change workflows can be easily configured, mixing approvals with manual tasks or even technical automation tasks.”

• Default workflows Report an error

  “Default workflows support a quick start and allow simple modification of standard processes.”

• Standard change cab Report an error

  “The risks, costs and required implementation tasks are known and the Change Advisory Board (CAB) approval is not required.”

• Standard change provisioning Report an error

  “Standard changes can therefore be used as provisioning actions for services that are ordered from the Matrix42 Service Catalog.”

• Nonstandard change phases Report an error

  “Therefore, they need to pass all change processing phases including analysis, approval and review.”

• Nonstandard change entry points Report an error

  “Non-standard changes can be requested by email, through the Matrix42 Self Service Portal, or created directly in the application.”

• Nonstandard change provisioning Report an error

  “As the final costs and tasks are not known at the time of the request, they should never be used as provision actions for services.”

• Emergency change phases Report an error

  “The analysis and approval phases are skipped – approval is usually given verbally by the ECAB (Emergency Change Advisory Board) – and the implementation phase is usually finished.”

• Emergency change creation Report an error

  “Emergency changes can be created only by change management directly in Matrix42 Service Desk.”

• Emergency change purpose Report an error

  “They are usually created in the system after the implementation and are used only for documenting the changed settings and coordinating a proper review.”

Scores citing this record

• The Change & Configuration Manager Service desk, incidents & requests
• The Change & Configuration Manager Change, problem & release management
• The Change & Configuration Manager Self-service portal & service catalog
• The MSP Owner Service desk, incidents & requests
• The MSP Owner Change, problem & release management
• The Municipal IT Lead Service desk, incidents & requests
• The Municipal IT Lead Change, problem & release management
• The Service Desk Lead Service desk, incidents & requests
• The Service Desk Lead Change, problem & release management
• The Skeptic Service desk, incidents & requests
• The Skeptic Change, problem & release management
• The Solo IT Admin Service desk, incidents & requests
• The Solo IT Admin Change, problem & release management