PROJECT PLAN REPORTDate: April 15, 2015

Project Title:Greenhouse CSA

Project Manager: John Noel

Project Overview

Greenhouse CSA has reached a point now where using different spreadsheets and depending upon consistent record-keeping by members and staff has become an impediment to the operational goals of this organization. Increasingly valuable time is wasted in maintaining records with accuracy and consistency, as well as sorting through a progressively growing pile of spreadsheets in order to conduct proper analysis of the more efficient crop-yields. This is time that the organization could be using to visit schools, create awareness, educate the public and local farmers, bring in visitors, network, gain membership and support, and analyze crop-yields.

The database-driven web application that this project will implement is a database system that will provide a much easier-to-access and organized system that is web-based. This means that it provides a central location for all with given access to utilize, review, and record new data. It also standardizes the way new data is input, thus allowing for the far easier maintenance and consistency this organization increasingly needs in its crop-records. This will save time and money, but most importantly, it saves that valuable time that can be focused on growing the invaluable sphere of help Greenhouse CSA provides to local growers and farmers.

In the Alternatives and Selection section, the different systems to meet the goals of this project are discussed, and the reasons behind the final choice is also explained. The Feasibility Assessment is divided into six parts describing the feasibility that this project can be completed. In it, is discussed the technical needs, and if Greenhouse CSA possess them. The cost-justification and estimated return on investment is also analyzed. The legal feasibility assessment discusses potential legal issues and what will be done about them. The Operational feasibility assessment describes changes that will have to take places, mostly training, and how those changes will be implemented. Aside from time taken for training, all operational systems will remain as per normal in the immediate, however, may subtly change over time due to the efficiency of the new system. The schedule of work-times during the implementation of the project is discussed at the end of the Feasibility Assessment. The milestones and project time line are also discussed.

The “project management conventions and standards” section describes the way the project team members will communicate and keep abreast of the progress of the project and any issues that may arise. It will also describe the structure of the team members as well as the way documentation will be created and kept. The “project deliverables” section describes in greater detail exactly what is expected to come out of this project, from what is expected to make access easier to what will make data-entry more accurate and consistent.

Alternatives and Selection

Three alternatives were considered for the Greenhouse CSA information system. First, a “no change” option was evaluated in which the current methods for maintaining greenhouse information continues as is. Second, a customized version of the off-the-shelf software package called “Agriculture Information Management” (AIM) was evaluated. The third alternative was to have a custom database application built for Greenhouse CSA by Software Associates.

The first option was eliminated because of the problems with data quality and time needed to maintain data. The second option was eliminated because the high initial software purchase price of AIM $8,000, the required maintenance agreement of $3,000 annually, and the need to customize some of AIM’s forms and reports. In addition, there would be an annual Oracle license payment.

The third alternative was chosen because it had a better cost-benefit outcome and would provide a database application designed for the needs of the Greenhouse CSA. The database application will be a database-driven web application developed with Oracle APEX and Oracle DBMS.

Feasibility Assessment

  • Technical Assessment

The team has the knowledge required to develop and sustain the custom database application. Greenhouse CSA has the infrastructure needed for the implementation of the new system, however new hardware will be acquired. There will be no need to hire outside expertise.

  • Economic Assessment

The ROI of 33.1% exposes the benefits of installing the new system, making the initial investment justifiable. Greenhouse is willing to accept the installation of the new system since the NPV of $9361 demonstrates a positive investment and will increase the overall value of the company. The cost-benefit analysis spreadsheet is attached to represent the results.

  • Legal Assessment

The legal considerations added by this project will be the user-rights of Oracle Database and APEX, as well as the use of the new operating systems for the two new computers we will be purchasing. Oracle Database, APEX, and the operating systems of both computers will provide a license with an end-user agreement that the development team will read over and follow when setting up the system. If we have any issues with the set-up and verification of our legal right to use the software, customer service and technical support for any of the software will be contacted.

  • Operational Assessment

This project will provide a dramatic increase to the ease of access and organization of records as well as decrease time taken to review and record crop data. This will allow analysis much more effectively in order to determine which crops grow where and with what best. This will also allow a much more quickly ascertained understanding of where and what is causing crops to not produce at all. This will facilitate a much more expedient adaptation and fine-tuning of the system, which benefits everyone.

It's expected that that implementation of the new system will provide moderate changes in how records are kept, reviewed, and analyzed. The Secretary will remain in charge of record-keeping, reviewing for accuracy and consistency, and generating reports. However, the secretary as well as all members and staff requiring access to the database must be trained on how to properly use the database. The secretary and development team can be trained during the data-migration phase. The secretary as well as the development team can train each new member and staff that needs access. The development team and secretary can train all current membership and staff that needs access. Training can be done during normal working hours on an as-needed basis.

  • Scheduling Assessment

The project will start Tuesday April 14, 2015 at 8 am. The estimated duration of project is two weeks. The working days are Monday through Friday with full time hours, from 8am to 5pm. There will be no days off during the duration of the project development. Since the project is in the beginning phase there is no recording of milestones and checkpoints.

Project Management Conventions and Standards

  • Team configuration

Software Associates’ development team consists of 3 people, each assigned half-time to this project for four weeks. The members are: John Noel, Priscila Gurrola and Adriana Luna. John Noelis the project leader and the contact person for the clients. Adriana and Priscila will share the responsibilities for creating models and creating the prototype. The project repository will be maintained by John. John Noel will oversee testing.

  • Communication Procedures

Only company email addresses will be used for project communication. During the work week responses to emails should be made within 24 hours. There will be a weekly meeting on Tuesdays and Thursdays for 30 minutes to report progress on tasks from the previous week and select tasks for the coming week.

  • Project Standards

Microsoft software will be used for reports, project timelines, cost-benefit spreadsheets and user documentation. Models will be done with Oracle SQL Developer & Data Modeler.

Project Deliverables

Database functionality

-Normalize data model into a relational data model.

-Build tables from the physical data model.

-Referential and entity integrity enforced.

Application:

APEX application

Inputs/Storage functions: (What/how input will be captured in the proposed system?)

-Data entry in a user friendly manner application

  • Make a form in APEX that will be user friendly

- Specific questions for selecting data

Inventory form

  • Capture planting date and type data
  • Capture harvest date and type data
  • Capture planting not harvested data

-Consistency of data storage after entered by end user

  • Make forms that automatically organize data
  • Capture new and repeated data and organize accordingly

-Automatic synchronization of repeated data

Make forms that prevent repetition of data

-Harvest Master Detail form

  • Capture data between harvesting and crop variety

-Harvest Master Detail form

  • Capture data between planting and crop variety

Processing functions:

-Retrieve greenhouse information based on filtering criteria

  • crop type
  • Display crop type in form
  • crop-variety
  • Display crop variety in form
  • amendments used
  • Display amendments used
  • date planted
  • Display date planted
  • harvest count
  • Display harvest count
  • Make a form for easy access of information

-Calculate totals for harvest counts and weights.

  • Make a form that would calculate totals after the input of data

Output: (What output will the proposed system provide?)

-Organized crop classification

  • Listing of all the crop classes

-Simplified results of harvest quantities

  • Listing of the harvest results

-Time evaluation of first and last crops

  • Interactive report based on crops table
  • Listing of the first crops
  • Listing of the last crops

-Specific assessment of crop variety harvested

  • Interactive report based on variety of crops
  • Listing of the variety of harvested crops

Control: (What controls will be in place?)

-Prevention of entering same data multiple times

  • Form for new data with error message display for the input of data already in database

-Generation of accurate reports

  • Prevention of data repetition
  • Date and time recording

-Time saving on development of reports

  • Easy forms to understand in the input of data
  • Relational form that relates data in different tables as needed