The scope of this document is to outline the process and procedures take to ensure the Kudler Fine Foods is in the best position to maintain the Frequent Shopper Rewards program that Smith consulting has put into place.
The following document is a tool for Kudler Fine Foods to use to make sure that there is a checks and balances system in place as they move toward expanding the Rewards program and growing their customer base. To complete this task Smith Consulting has compiled a list of criteria to follow based on the technical architecture document.OrganizationThe first step in the organization of a quality System is to put the people in place to oversee the processes. The first person to implement in this system is the quality manager. The quality manager will be responsible for overseeing the day-to-day task of the quality group.
The quality manager will also be responsible for hiring the QA Organizational team. Together this team will be responsible for the Internal and External documents and procedures for the Frequent Shopper Rewards Program. The quality manager will appoint one team member for each of the three store Locations. Independently these three team members will be responsible for the maintenance and updating of the documents at each location. Together the team will work toward an efficient control policy that will ensure that the Kudler Rewards Program is a quality piece of software.Quality ProceduresThe first set of task will include the procedures of the Quality System. The first step within a quality system is to create and maintain a set of QA documentation.
Second will be the documentation of the steps for quality in the frequent shopper program. Third will be the steps taken to follow and log compliance with all quality procedures. Prepare procedures and ensure compliance and attendance of all inspections and meetings. Create procedures for post-unit testing and audits. Third will be participation and feedback for all activities related to QA and unsure there is a format for all relevant feedback. Fourth will be to monitor all areas of the project and ensure that project leaders provide timely updates on project statuses.The outline for individual tasks completed by each stores QA follows.
First it is noted that every team member is responsible for ensuring the quality of each member’s work. Each team member is responsible for maintaining an issues database for the assigned store. Each team member is responsible for collecting data relevant to the project to ensure all monitoring and metrics stay current. The individual QA is also responsible for all reviews and inspections at each location to prove that the Customer Rewards Program is operating at its highest level.
StructureWithin each department a system is implemented to ensure a quality product. The qa manager will ensure the compliance of every policy and procedure. The QA manager will review and approve every action taken by the QA organizations team. The QA team will also be responsible for all testing. The project leader will be responsible for scheduling all testing procedures with the QA manager. Once the proposal is approved the project leader submits a Microsoft Project timeline so the project will get proper monitoring.
Metrics and GoalsThe metrics should reflect current time spent on the preparation and review of documents and processes. The metrics should also reflect and monitor defects for each. Last there is a quality self-assessment of all processes and performance. The quality self-assessment is maintained to reflect current performance statistics.
The goals for the project revolve around usability and error ratio. First will be the goal that any delivered software will not contain critical or serious defects. Second is on requirements: this shall be detailed as no more than three trivial or one medium defect per 100 lines of code.
The third goal will cover the design stage: there is no more than one medium defect per five diagrams. The fourth goal will cover pseudo code: there is no more than two medium defects per 1000 lines. The fifth and final goal will cover all other code: there is no more than two medium defects per 1000 non-commented code line.TestingFirst Smith Consulting will outline the idea behind the testing phases of implementation. First is to identify the magnitude and sources of development risk reducible by testing. The second idea is to perform testing to reduce identified risk.
The third is to know when testing is complete. Last is to manage testing as a standard project within the development project. Testing is the phase where careful attention is on any areas that may be missed. Testing can only verify the product or system and its operation against predetermined criteria.The first is unit or module testing; this will cover the website and database for all entries and shopping cart modules. Second is the process of data testing and ensuring that all entries from the websites shopping cart along with the field entries for user sign-ups go into the appropriate databases and fill the forms correctly.
The data testing will be the most crucial step as the customer rewards program relies exclusively on customer-related data. The third step is hardware testing, this will cover the bar code scanning at the three store locations. Testing the bar code scanners on all existing and future products and enshrining that all data is read by the system correctly. Last is personal testing, this step is in place as a sanity check to test if all personnel that will be using the new system have received training and have obtained enough knowledge to operate the software.
ImplementationThe final resolution of all steps leads to full implementation or “Live Status.” The eight activities that need to be followed to complete this stage follow. The first is the construction and testing of the website and software at each of the stores dealing with the bar code scanners.
The second activity is to construct and finish testing a production-ready database. When the database is considered production-ready will depend on the phases of testing that are completed. The third step is to ensure all bar code scanners installed operate correctly on all registers. The fourth would be to set the date that program will go live so everyone involved will prepare for each role. The fifth step is to test the hardware configurations and ensure the usability of all systems involved. The sixth step is to show that all documentation is in place and ready to go when needed. The seventh step is to check with all stake-holders, employees, and managers to make sure the project is ready to launch. The last and final step is to complete the training of all users who will work with the system.
ConclusionThe steps taken above and following this outline will ensure that Kudler Fine Foods has a successful launch of the Kudler Fine Foods Customer Rewards Program. Every step has been taken to account for all possible abnormalities and all software and hardware has been thoroughly tested. All matrix and goals are in place to start accounting for data and trends.