Research Paper About Odessa Mobile Technology Project (Research Paper Sample)

ODESSA MOBILE TECHNOLOGY PROJECT

Project PlanOdessa Mobile Technology Project
Author: Debbie Whitson Creation Date: 7/10/03Last Revised: 7/10/03Version: 1.0
 TABLE OF CONTENTSINTRODUCTION 2PURPOSE OF PLAN 2BACKGROUND INFORMATION/AVAILABLE ALTERNATIVES 2PROJECT APPROACH 3PHASE X: SECURE EQUIPMENT 3GOALS AND OBJECTIVES 4BUSINESS GOALS AND OBJECTIVES 4PROJECT GOALS AND OBJECTIVES 4SCOPE 5SCOPE DEFINITION 5ITEMS BEYOND SCOPE 6PROJECTED BUDGET 6RISK ASSESSMENT 7INITIAL PROJECT RISK ASSESSMENT 8MILESTONES 11ASSUMPTIONS 12PROJECT ASSUMPTIONS 12CONSTRAINTS 13PROJECT CONSTRAINTS 13RELATED PROJECTS 13CRITICAL PROJECT BARRIERS 13PROJECT MANAGEMENT APPROACH 14PROJECT TIMELINE 14PROJECT ROLES AND RESPONSIBILITIES 14ISSUE MANAGEMENT 16COMMUNICATIONS PLAN 17ATTACHMENTS/APPENDICES 19APPROVALS 20SIGN-OFF SHEET 20 
INTRODUCTION
Purpose of Plan
The Odessa Mobile Technology Project Plan will provide a definition of the project, including the project’s goals and objectives. Additionally, the Plan will serve as an agreement between the following parties: Project Sponsor, Steering Committee, Project Manager, Project Team, and other personnel associated with and/or affected by the project.
The Project Plan defines the following:
 Project purpose Business and project goals and objectives Scope and expectations Roles and responsibilities Assumptions and constraints Project management approach Ground rules for the project Project budget Project timeline The conceptual design of new technology Background Information/Available Alternatives Debbie: This section should describe the work you have done to date, the choices you had with regard to hardware/software, and an explanation of how you arrived at the decision to use L3 and Tiburon.
  Project Approach This section should outline the way you will roll out the technology, including the highest level milestones.   For example:  Phase I: Secure agreement with vendors (L3 and Tiburon)  Phase II: Order/Install Equipment Phase III: Install/Test Software Phase IV: Conduct Hardware/Software Testing Phase V: Conduct Training Phase VI: Implement ARS/AFR Phase X: Secure Equipment Define the phases in more detail.   GOALS AND OBJECTIVES Business Goals and Objectives The business goals and objectives for this project will focus on implementing mobile technology that:  Improves officer, firefighter and citizen safety. Facilitates coordination and information sharing both internal and external to the participating organizations. Enhances the ability and effectiveness of staff to perform their jobs. Facilitates coordinated crime prevention and reduction. Provides high levels of data security. Provides an open, flexible, reliable technology base for the future. Facilitates the electronic capture of data at its source. Is easy to use. Eliminate redundant data entry throughout the organization. Project Goals and Objectives Sample project goals and objectives:  Ensure that end users have input into the design process. Accomplish project business goals and objectives within defined budget and time parameters. Minimize impact to standard business operations within the affected units. Craft a favorable and secure agreement between the Department and the selected vendor.   SCOPE Scope Definition The Project will introduce new mobile technology; including the following:   35 mobile devices Digital CAD dispatch software Car to car messaging Internet access (?) Automated field reporting software GPS/AVL for automated dispatch Including the following interfaces:  CAD RMS AFR TLETS/NCIC/NLETS Desired Enhancements Any?   Items Beyond Scope The project does not include the following:  Devices in supervisor vehicles Desktop hardware upgrade or replacement Printers Projected Budget Define the project budget and insert it here:    Risk Assessment The initial Risk Assessment (following page) attempts to identify, characterize, prioritize and document a mitigation approach relative to those risks which can be identified prior to the start of the project.  The Risk Assessment will be continuously monitored and updated throughout the life of the project, with monthly assessments included in the status report (see Communications Plan) and open to amendment by the Project Manager.  Because mitigation approaches must be agreed upon by project leadership (based on the assessed impact of the risk, the project’s ability to accept the risk, and the feasibility of mitigating the risk), it is necessary to allocate time into each Steering Committee meeting, dedicated to identifying new risks and discussing mitigation strategies. The Project Manager will convey amendments and recommended contingencies to the Steering Committee monthly, or more frequently, as conditions may warrant.   Initial Project Risk Assessment Risk Risk Level L/M/H Likelihood of Event Mitigation Strategy Project Size   Person Hours H: Over 20,000 Certainty Assigned Project Manager, engaged consultant, comprehensive project management approach and communications plan  Estimated Project Schedule H: Over 12 months Certainty Created comprehensive project timeline with frequent baseline reviews Team Size at Peak H: Over 15 members Certainty Comprehensive communications plan, frequent meetings, tight project management oversight Number of Interfaces to Existing Systems Affected H: Over 3 Certainty Develop interface control document immediately Project Definition   Narrow Knowledge Level of Users M: Knowledgeable of user area only Likely Assigned Project Manager(s) to assess global implications  Available documentation clouds establishment of baseline M: More than 75% complete/current Likely Balance of information to be gathered by consultant Project Scope Creep L: Scope generally defined, subject to revision Unlikely Scope intially defined in project plan, reviewed monthly by three groups (Project Manager and Steering Committee) to prevent undetected scope creep  Consultant Project Deliverables unclear L: Well defined Unlikely Included in project plan, subject to amendment  Vendor Project Deliverables M: Estimated, not clearly defined Somewhat likely Included in project plan, subject to amendment  Cost Estimates Unrealistic L: Thoroughly predicted by industry experts using proven practices to 15% margin of error Unlikely Included in project plan, subject to amendment as new details regarding project scope are revealed  Timeline Estimates Unrealistic M: Timeline assumes no derailment Somewhat likely Timeline reviewed monthly by three groups (Project Manager and Steering Committee) to prevent undetected timeline departures  Number of Team Members Unknowledgeable of Business L: Team well versed i...