Implementation Plan 1

Implementation Plan

Carl Hagerman

CMGT/445

11/15/2015

John Harvey

Project Name or Identification:

Kudler Fine Foods Service Request SR-kf-013

Project Stakeholders

Store Manager

Project Description

The purpose of this project is to provide Kudler Fine Foods with a new database system to keep track of the customer’s purchases.

The main challenge of this project will be to create a database that will contain specific purchases and a customer purchase tracking system. There is an added challenge of dealing with reward programs/customer information by tracking purchases, information retrieval, review program points, and items that have reward points

The desired outcome of this project is for Kudler Fine Foods to have a database that keeps track of customer purchases and their reward program information.

Measurable Organizational Value (MOV)

The primary measure of value for this project will be introducing a new database into Kudler Fine Foods. The database with specific purchases will show the differences between non-reward purchases and reward purchases. This database will also contain the information of the customer. When dealing with the rewards program, we will continue with the current product database but injunction with an updated with tags that are qualified for rewards. Using a tag will help indicate what the point value of each item is worth and the length of time for the reward program. A rewards tracking system will need to be created so customers or employees can use it to track purchases, information retrieval, review program points, and items that have reward points.

Project Scope

Project Schedule Summary

Project start date : Nov 03, 2015
Project end date : Nov 30, 2015
Timeline of project phases and milestones:
Delivery of data expected on Nov 6, 2015
First design of the new database onNov 12, 2012
Milestone – Successful design of new database ready
Next coding for the new database ready on Nov 18, 2012
Milestone – Successful installation and testing
Next set up of the new system on Nov 20, 2015
Milestone – Successful installation and testing
Next installation of the new database on Nov24, 2015
Milestone – Successful installation and testing
Next new database goes live to customers on Nov29, 2015
Milestone – Successful installation and testing
Project Goal – Successful installation and testing of the new database
Ongoing testing, maintenance, and employee surveying to determine satisfaction with the new database
Project Completion – Nov 30, 2015

Project Budget Summary

Quality Issues

Adhering to the schedule is essential to keep labor costs within budget.
Customer and user satisfaction is essential to project success so testing must meet or exceed protocol standards.

Resources Required

Assumptions and Risks

Assumptions used to develop estimates
Database Team able to complete task by assigned date
Key risks, probability of occurrence, and impact
Back up personnel may be required if team member is out
Maintenance requirements may slow the upgrade schedule
Key staff may be required to perform other mission critical duties
Constraints
Work on this project cannot negatively impact the IT departments daily functions or the operation of Kudler Fine Foods
Dependencies on other projects or areas within or outside the organization
The IT staff implementing this change must work closely with transportation to ensure that the database schedule goes according to plan without impacting Kudler Fine Food services

Project Administration

Communications plan
The communication plan to spread the word about the new Kudler Fine Foods database will be announced on their website. They will hold a one day flash sale in order to prompt their new database and rewards system
Scope management plan
The primary aim of the scope management plan isto provide Kudler Fine Foods with a new database system to keep track of the customer’s purchases
Implementation and project closure plan
The technical implementation of the new database for Kudler Fine Foods will be for users and customers. It will give the users the ability to track and maintain purchase orders and reward points. It will also give customers the ability to track and see where they stand in reward points.

Implementation and Continued Maintenance and Project Closure Plan

Down time:
All changes will be made during nonbusiness hours
How will the integration be communicated?
Through Email and Website
How will the new system be deployed (pilot, phased, parallel, plunge, and so on)?
Pilot
Support and maintenance

Week 1: Training- This week will be dedicated to the training of employees on the new system. The training will include the information about how the program works for customers, how to use the new system at the point of sale, how to answer questions that customer have, and a hand on use of the online interface and point of sale system. Every employee must go through this training and be tested on their knowledge and comprehension of the new program.

Week 2: Installation- This will be when the new system is installed and the data centers are put together to house all the system’s information. The point of sale and online applications will also be implemented during this week. All this must be completed this week because this is the week the system is installed.

Week 3: System goes live: This is the week that customers can start signing up for the program and their transactions will be tracked for the benefits.

All maintenance and scheduled updates will be performed by Database Junkies Inc.

References

Valacich, J. S., George, J. F., & Hoffer, J. A. (2012).

Essentials of Systems Analysis and Design,(5th ed.). Retrieved from The University of Phoenix eBook Collection database.

Kudler Fine Foods.(2014).

Retrieved from Foods