Congratulations! You have signed a Statement of Work (SOW) with enChoice and have become a valued Customer.
At this stage you will be assigned a Project Manager who will review your scope of work with our Professional Services team, identify your project team members, and prepare for your kick-off meetings.
Your Account Executive will schedule a call with all involved parties including Professional Services (including the Project Manager and Architect), and Managed Services. This call is to introduce the enChoice team to you and the first part of building a cohesive team.
Once this transition has begun and preliminary questions are answered we will move on to kick-off.
Kick-off is a two-part process: first with our internal team and then with our client. During this internal kick-off meeting your Account Executive will share information and insight into your project objectives, company culture, and any potential constraints such as critical dates. Your Project Manager will review and walk through your SOW with the team and outline how the project will be run, who is responsible for which project aspects, and what does the preliminary timeline looks like.
The second phase of kick-off is our customer project kick-off meeting. This meeting will preferably take place at your site, unless there are extenuating circumstances. This meeting will include your critical team members along with your enChoice Account Executive, Sales Engineer, Project Manager, and Solution Architect (SA). It may also include our PMO Director, Director of ERM or ECM as appropriate and members of our Senior Management team. Your enChoice Project Manager will lead this kick-off meeting and is also responsible for coordinating with the client’s Project Manager or project lead. This onsite client kick-off meeting can be scheduled for between one to five days depending on the complexity of the solution.
While at the client site during kick-off, enChoice will gain a deeper understanding of your business processes and the requirements needed to help you improve. An enChoice Business Analyst or Solution Architect will manage this process with assistance from the Project Manager, who will facilitate the information gathering. Although limited to the parameters of the SOW and the line of business we are working with, we’d prefer this to be the time for an open-ended conversation. To deliver a stronger value-added solution to our clients, we need to get a complete understanding of HOW your company works end-to-end and not necessarily just within the confines of those aspects associated with the SOW. The requirements phase is also the time where we collect organization process assets such as flow charts or process diagrams of the current as-is processes. If none are available we may attempt to sketch them out at a high-level during the meetings.
Immediately following kick-off, the enChoice team will meet to synthesize the requirements gathered into a Business Requirements Document. The team will identify those requirements that can be implemented out-of-the-box (OOTB) through configuration, those that require customization, and those that require additional product features. The delivery team will then hold a meeting to discuss your requirements with the Account Executive and Sales Engineer to finalize scope. The enChoice Sales and delivery teams will work with you to clarify scope, expectations and, when necessary, add scope to the project via the Project Change Request (PCR) process.
Your enChoice team – under the guidance of the Project Manager, the Solution Architect, and the Director of ECM or ERM – will assign work effort to all the items in Scope to understand if there is a delta between your SOW and identified work. Your enChoice team will have a final review with you of all items in scope and prioritize and/or break the project up into multiple phases, if necessary.
At the Architecture stage, for complex solution projects, the enChoice Solutions Architect will create a Conceptual Design document that will define the overall design of the solution necessary to meet the requirements defined and documented in the prior phases of the delivery process. This document is detailed enough to give you a clear idea of how the solution will be implemented, ensures that all your requirements are met, and will be used to facilitate upcoming project planning.
For less-complex projects, e.g., migrations, the team will create an Approach document defining the steps that will be taken, the tools that will be used to deliver the project, basic architecture diagrams (when necessary), and basic configuration information.
During the planning phase, your delivery team will plan the execution of your project. The goals of this planning phase are to:
As with any project, the resulting plan is dynamic and capable of adjusting with the ongoing demands of your project.