**Executive Summary **
Scope: The focus of my project is the Customer Service Department located at Winn-Dixie Marketplace. The main Objective is to eliminate redundant steps required to process refunds on a daily basis. I will also attempt to reduce the unnecessary paper work that is produced during the refund procedures. Which will reduce the customer's waiting time during a refund transaction.
The rest is in a zip file.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
3) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site).
### **The Project Plan** Your approach should be to convince me, a member of your senior management, to authorize/fund your project.
As the Project Manager, appointed at the inception of the project, you will demonstrate in your Project Plan; (1) the objectives of the project, (2) what activities will take place, (3) what cash outlays will be made to accomplish the objectives of the project, (4) what resources will be needed to do the work, and (5) what schedule you will follow in completing the project.
The Project Plan really accomplishes two functions. Initially, it is used to receive authorization for the project and most importantly, it is a planning tool for the PM to think through every step of the work. In this process, scope, manpower, materials, schedule, and budget, at a minimum, are carefully defined and documented.
If you will be building a facility, the process will be significantly different than if you choose to develop a software application or a Lan installation. The following is a good list of activities for HW/SW development. This planning process is based on the Life Cyle events common to SW/HW development:
* Concept Evaluation
* Requirements Identification
* Customer Test and Evaluation
* OPerations and Maintenance
**Project Plan Elements** that are suggested for Non-HW/SW Projects are:
* General Approach
* Contractual Aspects
* Evaluation Methods
* Potential Problems
Evaluate your project in terms of these elements and ask if they adequately describe the product and environment your project will be launched into.
**Evaluation** of the project in terms of industry standards, such as Mil Standards, Architectural, engineering or building codes is essential. We had to build to North Carolina Building Commission standards as a rule. In the fall, NC is adopting the national standard. Any new project we do will need to be verified against this new set of standards. Consider what standard your project will be evaluated against
**Potential Problems**, also know as **Risk Analysis** is the last activity that needs to be planned into the project. How can things go wrong? If they go wrong, what will need to be done to get back on schedule/budget? Think about the weather, employee problems, design errors/omissions, and the myriad other things that could cause delay and extra expense.
Windows 98 or higher and it must operate in MS Project 2000.