Kudler_Fine_Foods

Kudler Fine Foods Frequent Shopper Program Paul Poland BSA/375 November 15, 2011 Bashar Elkhatib Kudler Fine Foods Frequent Shopper Program Installation Process and Training Summary The key to a success for business is current, up-to-date technology, and providing a good, quality customer satisfaction. Kudler Fine Foods prides itself on doing just that by implementing a Frequent Shopper Program. In order for Kudler’s frequent shopper program to be a success and for them to bring in more cash revenue they must incorporate a newly redesigned program that would involve updating their technology in each of the locations. Installation Installation will be conducted throughout each of the Kudler Fine Foods locations. The installation will take approximately six months to a year to be up and running smoothly. The first installation will be conducted in the La Jolla store. The programmers as well as the testers will run the program and thoroughly test it for any types of bugs that may come about. This process should take no longer than 3 months to complete. Then once the first team is done they will then move on to the remaining stores to spin them up. The second team that will consist of the network specialist will install all the Dell OptiPlex 775 with the operating system consisting of Windows Vista. They will also ensure that all the printers and the checkmate application are compatible with the operating system. This process should take no longer three to complete and once they have finished they move on to the other store locations as well. Training The training process will be conducted in the main branch of Kudler Fine Foods. The training session will take one month to conduct. This will be a thorough training process because they will have a tour of the whole infrastructure and they will receive PowerPoint presentations as well as practical application session. The training will be conducted through the week and the employees will get paid as if they or going to work. Documentation Plan A documentation plan is used to establish the documentation requirements for a specific project. It helps the Project Manager, Senior Technical Writer and other writers: a. Prepare cost estimates for the project duration b. Schedule resources across the project lifecycle c. Ensure requirements are identified in advance of project kickoff d. Ensure documents are scoped correctly with the appropriate level of detail e. Understand the relationship to other projects f. Defining the target audience who will use the document (Klariti, 2007) Providing documentation for all areas of the program will be essential for its continued success and operation. There will be two distinct types of documentation: pamphlets and leaflets for the customer base and technical manuals for the employee base. Customer Documentation The company will need to provide pamphlets to its customers so that they will know how to access the program on the web. They can be designed in a tri-fold style which will keep the size to a minimum. The pamphlets will inform the customers how to go about logging onto the system, registering to create a personalized username and password, checking how many points have been accumulated and, if they wish, redeeming points for the various prizes available. Employee Documentation Since not every employee is fully computer savvy, there will need to be technical manuals available to assist them in the functions of the new hardware and software being used. These will range from basic information sheets instructing the employee where to click or what button to press to fully written technical drawings and flow charts that will mainly be used by the companies technical department. Once the documentation is complete, if future questions come up that cannot be answered with current manuals in the companies library, the manufacture of the equipment will need to be contacted so that amplifying information can be received an added. Support and Maintenance Plan Summary Support and maintenance is an ongoing process in maintaining the Frequent Shopper Program for Kudler Fine Foods. This is extremely important in the beginning once the process is implemented, to ensure that any needed corrections are made to the beginning process if the need arises. Also important is the need to continue supporting the program. This includes adapting the program as the team receives feedback from customers, enhancing the program as new possibilities arise and monitoring the systems and application to be aware if any changes need to be made to repair or replace and of the hardware or to update the networks as Kudler Fine Foods continues to grow. (Apollo, 2007) At this time Kudler has two computer support specialist who report to Harvey Stephens, the Director of Finance and Accounting. As Kudler will be expanding their use of technology, the computer support will need to develop into a department with enough employees to support and maintain the systems in all the Kudler stores. There will also need to be a change control board set up consisting of a team of employees from each of the departments. These employees will control which systems get modified and in which order. There also needs to be a system set up to handle the change request so that they reach the change control board for consideration. A system also needs to be set up to rate the priority of the request so that the most important changes are at the top of the list. Versioning The computer support team will need to develop a version control system so that changes are recorded as versions and not just made at will. Each version will need to be identified in the application so that testers and users can identify the version they are working on. (Satzinger, Jackson, & Burd, 2004, 636/16) The documentation that was developed for the original implementation will need to be updated as the new versions are introduced and the version number on the documentation should correspond with the version numbering of the application to make the information consistent and easier for someone to come on board and quickly figure out what is going on with the process. (Apollo, 2007)