Kickoff

Step 2

The kickoff phase is the opportunity to organize all the stakeholders of the project to formally begin the project (typically starting as a kickoff call).  This allows for an event to discuss and collaborate with the client/customer all the many details of the scope, in preparation to the Build.

This also gives all the "players" a chance to meet and begin the customer relationship of the team.  It becomes crucial for building relationships of trust during this process, and throughout.

Ivinex will try to gain as much information as possible, and make sure to follow up and do everything that was promised.

The kickoff call has several purposes:

1.  Introduce People:  Individuals from the client side, Ivinex, and inContact (or even another third-party if required).

2.  Identify who we will be working with.

3.  Identify overall goal of the Ivinex implementation.

4.  Identify business processes (fill in details not defined by sales).

5.  Identify business modules required in the Ivinex system.

6.  Identify reports (sometimes clients do not know yet).

7.  Identify integrations.

8.  Identify how the customer does things now, and what problems they have with a solution.

9.  Identify timelines + Go Live Date.

At the end of the kickoff call, everyone should know with a high degree of certainty what is expected by the client.  If there are still unknowns of the scope, action items need to be created with assignments (with dates) on those action items for completion.

Immediately after the kickoff call the Ivinex implemenation engineer (project manager) will send to the client a list of everything that was discussed, and gain clarity for any additional questions.  The Project Manager will be the main contact for Ivinex.

This documentation will then serve as scope of the project.

The Ivinex implementation engineer (Project Manager) will then take all the assimilated information and compose a detailed Business Requirements Document (BRD).  The BRD will define project-specific activities, deliverables, timelines, and functional requirements necessary for Ivinex to provide the Professional Engineering Services as identified during the sales process.

It will include detailed technical requirements that identify systems and other integration points to interface with Ivinex (inContact).  This results in the BRD being the blueprint for development.  Ivinex will only perform implementation tasks related to functionality that is specified in this document.

Approval and Authority to Proceed:

Once the Business Requirements Document (BRD) is signed/approved by the customer -- the implementation Build phase will begin.  Determine with the customer a Go Live Date for purposes of what everyone is shooting for.

By signing the BRD, the customer will agree that the document completely defines and covers the implementation scope.

At this point, all that is required from inContact by Ivinex is all the customer contact information, and that a Business Unit is created, and given credentials.  See the Server Information credentials required by Ivinex below for Dialer settings. 

inContact Server Information in Dialer Settings for Ivinex.