Skip to content
English
  • There are no suggestions because the search field is empty.

Things to consider before starting the implementation of HappySignals products: Basics, Persons, Environments

This is a short checklist of things needed to consider and take care of when planning the implementation of HappySignals.

Basics

  1. HappySignals Agreement must be signed before starting the HappySignals implementation.
  2. Contact persons' information shall be provided to HappySignals with the signed agreement or work order: a) the customer’s rollout coordinator/project manager, and b) the person responsible for installation in the customer’s environment.
  3. The customer's main objectives and focus area for using HappySignals shall be communicated to HappySignals. We want to ensure that we can provide support, especially in this focus area, during the rollout.
  4. Resources shall be allocated for a successful rollout. Below is a list of required roles, along with a rough estimate of the time needed for each.

Persons

  1. Person responsible for the (ITSM) system, 2 days. Participates in definition and specification work, representing the tool and process perspectives.
  2. Person responsible for making (ITSM) system and process decisions, 1 day. Participates in definition and specification work, representing the customer's business needs from a service management and reporting perspective.
  3. Person responsible for the installation of HappySignals, 2 days. Participates in defining and specifying work, and installs and configures HappySignals in the customer environment. Typically, a partner's employee.
  4. Person(s) testing HappySignals integration, 1 day. Test the product to verify the configuration before the go-live decision.
  5. Person responsible for coordination, 3 days. Plans and coordinates rollout tasks, and is responsible for ensuring the effective use of the product within the organization.

Environments

HappySignals will create environments and provide access for customer use, usually at least:

  • Development
  • Test
  • Production

This will allow the customer to implement the solution according to their own release model.

Note: This article is part of the HappySignals Self-Service Implementation Tour.
To proceed to the next step in the tour,  click here.