7 STEPS TO WIZEHIVE IMPLEMENTATION SUCCESS I II III IV V VI VII

7 STEPS TO WIZEHIVE IMPLEMENTATION SUCCESS
I
Kickoff / requirements call
II
Documenting the requirements
III
Obtaining approval on the requirements
IV
Building the solution and training
V
Testing your programs
VI
Making changes to your program
VII
Go-live with your program
collect, organize, and manage anything
Our Premier Customer Support Team & Implementation Delivery
When your contract has been awarded, it’s time to get started. WizeHive’s Implementation
team is made up of a series of seasoned systems professionals. The team applies a
standard project life cycle methodology for implementation of your program methodology
for implementation of your program. To begin this process, WizeHive will immediately
assign an Implementation Lead to your account, taking into account the nature of your
program(s) and the types of configuration knowledge that will be required. Your
Implementation Lead will reach out to you quickly after being assigned to schedule a
Kickoff/Requirements call with you.
I
II
III
IV
V
VI
VII
Step I: Kickoff / requirements call
Depending upon the nature of your program(s), the time estimated for your program
implementation may vary. Your Implementation Lead will lead your Kickoff call, during
which time you will be asked to explain the way your program works today. You will also
be asked to clarify what you are looking for WizeHive to do to further automate and
improve that process. Your Implementation Lead will listen to your needs and then ask a
series of probing questions to make sure they understand the flow of your program. This
is a critical call and sometimes requires more than one session. The Implementation Lead
will ask questions regarding your goals, your timeline, specifics about who needs to
perform specific steps, how an application should be completed, how your review process
should take place and the kind of reporting that you need to do. They will also make you
aware of functions that are available to you within WizeHive based on the subscription
level you have selected with your contract.
Once your Kickoff Call occurs to clarify the purpose and nature of your program, we then
discuss your program timeline and configuration. Where warranted, the Implementation
Lead will provide alternative solutions to you so that you can understand how the solution
might be implemented and to gather further knowledge about the process and your
intent. They will then guide you to select the most effective solution and clarify that for
your understanding.
Once the right option for configuration has been identified, we then document
requirements.
collect, organize, and manage anything
I
II
III
IV
V
VI
VII
Step II: Documenting the requirements
Following your Kickoff call, your Implementation Lead will document your requirements.
The requirements will include a summary of your program or programs, including what the
program is for and the goal of the program. They will indicate the steps in your process
and the build components of the configuration in WizeHive. For each component, they
may specify detailed requirements to meet your defined needs. A timeline will be created,
to clarify what information and what portion of the configuration needs to be made
available by what date. This will ensure that you have a clear understanding of the
approach by which the build of your program will occur and who is responsible for each
step.
I
II
III
IV
V
VI
VII
Step III: Obtaining approval on the requirements
The Implementation Lead will forward the resulting Timeline/Plan and Requirements
Documentation to you as a way of formalizing an understanding of the needs of your
program. You will be asked to formally approve this document as a record of the
agreement of what is to be delivered. The Implementation Lead will send the
Requirements Document to you for review via email. You then have the opportunity to
review that document and indicate where changes are required in order to accurately
reflect the approach to building/configuring your program. You will have the opportunity
to discuss your changes with your Implementation Lead so that the approach can be finetuned for items that they may have misunderstood, need clarification on, or that you might
elect to change. Once the document accurately reflects your intent for the build of the
program, your approval is required for the Implementation Lead to continue with the
configuration/build.
Once approved, WizeHive formally begins the “build” of the program configuration with
you.
collect, organize, and manage anything
I
II
III
IV
V
VI
VII
Step IV: Building the solution and training
Once you have approved the defined timeline, requirements, and list of items/activities
that you, as the customer, are responsible for, we then begin the “build” of the
configuration.
The Implementation Lead will configure WizeHive with you, to the solution that has been
approved. Where agreed, there will be steps that you will need to perform. WizeHive will
provide various administrative training during this period, so that you become well-versed
in the product and feel comfortable making updates to your forms and review portals as
needed. You will find the product easy to use if you take the time to partake in
administrative training and begin to do form updates on your own! We strongly
recommend training and WizeHive certification.
Once the solution is fully built, it’s time to test the program!
I
II
III
IV
V
VI
VII
Step V: Testing your programs
With the completed configuration we begin conducting testing within WizeHive to ensure
that the configuration appears to be set up appropriately and is operating as defined in
the requirements.
Once configured, WizeHive will perform form and portal tests to ensure that the
Workspace setup is working as defined in the requirements. You must test the solution
with a variety of applications or entry forms and with the setup of reviewers, review portals
and reports. You’ll want to make sure that the program is tested from start to finish in
order to ensure that you can forecast the types of questions that might be asked by
applicants or reviewers while you program is live. You will also want the opportunity to
identify any issues so that they can be rectified well in advance of your planned go-live
date.
collect, organize, and manage anything
I
II
III
IV
V
VI
VII
Step VI: Making changes to your program
Changes do occur, whether because you have changed your mind, your business changes,
or just because you forgot to mention a requirement. Regardless of the reason, we’re here
to help you! We have a formal change process that allows us to document any changes
you have in mind relative to the original Requirements document and plan that was
outlined for your Program. Your Implementation Lead will help you through this and will
provide you with alternatives for making updates in conjunction with your timeline and in
conjunction with the impact of the changes required. We want you to be happy with your
service and want what we are building to be completely transparent to you.
We encourage you, the customer, to do user acceptance testing as an applicant, as an
administrator, and as a judge or evaluator. We strive to make sure that your configuration
is set up 3 to 4 weeks in advance of your go-live date in order to ensure that you have
sufficient time to test and that we have sufficient time to resolve any issues that are
identified. There should be no last minute issue resolution in preparation for your go-live
date. Any changes that are identified through testing or post go-live are tracked as change
requests that you must approve and that we must also approve. Change requests can
have cost impact, but do not always have cost impact.
I
II
III
IV
V
VI
VII
Step VII: Go-live with your program
Once you have fully tested your WizeHive configuration for your program you are ready to
go! Simply provide us the go-ahead that all of your requirements have been addressed,
and you can now set your forms and portals to go-live.
collect, organize, and manage anything

Download Report