This delivery model includes a number of worksheets, best practices and examples to assist with your implementation process. If needed, these worksheets can be combined into a single functional specification or requirements document for sign offs and developer notes. Much of the process, including form creation, can be done by analysts, while developers are concerned with creating the framework.
We've bought the product, but how are we going to actually make it successful? Getting the project moving means informing, provisioning and engaging the team
- Getting the team together (Participants, Contacts): Project Participants Document
- Starting with a good project plan assures that milestones are met and expectations are realistic—the plan should then be updated and approved after the branding and definition portions of the implementation are complete
Training provided by Kinetic Data can help make your team more productive in a shorter amount of time. Classes are offered for both the analysts and technical groups.
How your portal and forms look and feel to your internal and external customers can make a big impact on whether or not they'll use the solution versus calling the service desk.
- Use your organization's existing brand elements, existing web pages and style sheets to drive the look and feel of your portal: Styling Your Catalog & Forms
Organizing the Service Portfolio
Defining how your customers will find and interact with your services, helps organize an often diverse portfolio.
Defining Your Service Request Forms
Now that the broad plan is in place, start defining individual service items. These translate to forms that a user can access via the catalog.
- Form Templates: Well designed form templates are key to a responsive Kinetic Request deployment. By creating templates others can clone, implementing a new service can be quick and painless.
- Define the Individual Service Requests: Using use cases is a very effective way to drive your process definition, which will drive your form definitions, which will help your determine your task definitions, so you end up with your individual requirement or blueprint documents.
Don't leave your report planning until after deployment. Determining up front what your users and managers will want to see reduces the number of changes that need to be made later.
- Reporting Checklist
Kinetic Request supports a number of different authentication schemes from anonymous access to a Single-Sign-On (SSO) approach. Before or during installation, the business should decide how users will be identified and authenticated.
- Users, Groups, External Authentication, SSO and more
Building Your Portal
Once the requirements are defined and the application installed, the catalog framework can be built. Often a developer will put together the look and feel of the portal page(s) with direction from the documents created earlier.
Building Your Forms
A developer will likely create form templates and handle some of the more technical details of building a form. However, once this is set up, an analyst or other non-technical staff can create many of the forms needed by an organization. Kinetic Data also offers training to get your staff creating forms quickly using best practices.
- You've got the requirements for the branding, the templates, and service items. Now go build it: Kinetic Request User Guide.
Testing & Deployment
Make sure all requirements were met by implementing a test plan for new forms/services as they are finished and ready to go online. In addition, a migration strategy is needed to move new and modified forms from a development environment to a production environment. Kinetic Request includes a migration tool to assist in moving forms when needed.