Ryan Reeves

1
Group 3

• Ryan Reeves
• Monica Stallworth
• Juan Rodriguez
• Aziz Sori
• Sherri Penick

2
Milestone 1

• Scope Definition

3
Scope Definition

• Stage of the project where we Identify the
  coverage of the project and the perceived
  problems, opportunities, and orders that
  triggered the project.

4
Request for System Services
5
Request for System Services
6
Problem Statement Matrix
7
Feasibility Criteria

• Operational Feasibility
• Functionality. Monitoring business processes to
  maximize efficiency, Technicians may need a
  mobile device, such as a PDA or other wireless
  device (like a GPRS/EDGE laptop card) to
  communicate with the system from remote location.
  The system should be deployed on existing
  hardware.
• Political. The solution is made to facilitate
  business process as well as solving time
  consuming process. Technicians will benefit from
  this solution by using their time better.

• Technical Feasibility
• Technology. Employee training should be required,
  the bookkeeper, management and technicians will
  need training for the new system.
• Expertise. In-house design, development and
  deployment can be easily achieved due to the
  business characteristics of Coastline Systems
  Consulting.

8
Feasibility Criteria

• Schedule Feasibility
• The Project may last 6 months. Management
  should set a time where they can meet with
  clients to interact with the systems and show
  their progress. Since there is not set a real
  deadline the Project may not finish on time
  because of customer related problems where the
  technicians time will be taken up in customer
  service. Therefore in order to allow time to deal
  with customer issues this deadline may need to be
  modified.

• Economic Feasibility
• Cost to develop 64,000
• Payback period (discounted)
• 3 years
• Net present value 25,000
• Detailed Calculations
• (see problem statement matrix)

9
Statement of Work

• PERIOD OF PERFORMANCE 8/31/04-12/10/04
• CUSTOMER Coastline Systems Consulting
• PROJECT NAME Services Request and Reporting
• Purpose To design a system capable of system
  service request entry and tracking by customers
  and generating various reports and statistics for
  management use.
• Background
• Problem, Opportunity, or Directive Statement
• IT technicians are drowning in a sea or work and
  work for clients is not being done in an optimum
  manner
• History Leading to the Project Request
• IT consultants have been receiving direct service
  requests from clients and the receptionist
• Project Goal and Objectives
• To design a system that is more responsive to
  clients and helpful to consultants
• Product Description
• Computer system that keeps track of service
  requests in a database
• Scope
• Stakeholders
• Owners, clients, and consultants
• Data
• Service request data, hours spent on service
• Processes

10
Statement of Work

• Budget Constraints
• Project cannot exceed 50,000 without owners
  consent
• Technology Constraints
• Software must be compatible with Windows2000 and
  written in Java
• Rough Order of Magnitude (ROM) (or Ballpark)
  Estimates)
• Schedule
• 4 months
• Budget
• 45,000 - 55,000
• Conditions of Satisfaction
• Success Criteria
• The system will be successful if technicians can
  efficiently enter and update service request,
  clients can easily enter them, and management can
  produce useful reports and statistics
• Assumptions
• We assume that the project will be finished on
  time and within budget constraints
• Risks
• Running over budget
• Authorization to proceed
• Note
• The signatures below certify that each agrees to
  the provisions of this SOW and attests to the
  completeness, feasibility, consistency and
  testability of the requirements.

11
Statement of Work

• Project Approach
• Route (or Lifecycle)
• Project assignment w/ negotiated scope
• Deliverables
• Work Breakdown Structure
• Managerial Approach
• Team-building Considerations
• The project team should consist of a consultant,
  programmers, web designer and administrator, and
  the president and bookeeper
• Manager and Experience
• The project manager must be familiar with all
  aspects of the proposed system
• Training Requirements
• The project manager must be trained in MIS with a
  certification in project management
• Meeting Schedules
• The meeting setting will be JAD, and members will
  meet twice a week
• Reporting Methods and Frequency
• The project will be reported between project
  members daily via email
• Conflict Management Approach
• Conflicts will be resolved
• Scope Management Approach

12
Gantt Chart