DOC

Sample Project Plan

By Christina Alexander,2014-04-11 12:08
11 views 0
The Project Plan defines the following: Project purpose; Business and project goals and objectives; Scope and expectations; Roles and responsibilities

    ODESSA MOBILE TECHNOLOGY PROJECT

Project Plan

    Odessa Mobile Technology Project

    Author: Debbie Whitson Creation Date: 7/10/03 Last Revised: 7/10/03 Version: 1.0

    ODESSA MOBILE TECHNOLOGY PROJECT

    TABLE OF CONTENTS

    INTRODUCTION ............................................................................................................................................................... 2 PURPOSE OF PLAN ............................................................................................................................................................... 2 BACKGROUND INFORMATION/AVAILABLE ALTERNATIVES ...................................................................................................... 2 PROJECT APPROACH ........................................................................................................................................................... 3 PHASE X: SECURE EQUIPMENT ............................................................................................................................................ 3 GOALS AND OBJECTIVES ............................................................................................................................................ 4 BUSINESS GOALS AND OBJECTIVES ..................................................................................................................................... 4 PROJECT GOALS AND OBJECTIVES ...................................................................................................................................... 4 SCOPE ............................................................................................................................................................................... 5 SCOPE DEFINITION ............................................................................................................................................................... 5 ITEMS BEYOND SCOPE ......................................................................................................................................................... 6 PROJECTED BUDGET ........................................................................................................................................................... 6 RISK ASSESSMENT ............................................................................................................................................................... 7 INITIAL PROJECT RISK ASSESSMENT .................................................................................................................................... 8 MILESTONES ...................................................................................................................................................................... 11 ASSUMPTIONS .............................................................................................................................................................. 12 PROJECT ASSUMPTIONS .................................................................................................................................................... 12 CONSTRAINTS ............................................................................................................................................................... 13 PROJECT CONSTRAINTS .................................................................................................................................................... 13 RELATED PROJECTS .......................................................................................................................................................... 13 CRITICAL PROJECT BARRIERS ............................................................................................................................................ 13 PROJECT MANAGEMENT APPROACH ..................................................................................................................... 14 PROJECT TIMELINE ............................................................................................................................................................ 14 PROJECT ROLES AND RESPONSIBILITIES ............................................................................................................................ 14 ISSUE MANAGEMENT .......................................................................................................................................................... 16 COMMUNICATIONS PLAN .................................................................................................................................................... 17 ATTACHMENTS/APPENDICES ................................................................................................................................... 19 APPROVALS ................................................................................................................................................................... 20 SIGN-OFF SHEET ................................................................................................................................................................ 20

     1

    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.

     2

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.

    3

    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.

    4

    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?

    5

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:

    6

    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.

    7

Initial Project Risk Assessment

    Risk Risk Level Likelihood Mitigation Strategy

    L/M/Hof Event

     Project Size

     CertaintyPerson Hours H: Over 20,000 Assigned Project Manager,

    engaged consultant,

    comprehensive project

    management approach and

    communications plan

    CertaintyEstimated Project Schedule H: Over 12 months Created comprehensive project

    timeline with frequent baseline

    reviews

    Certainty Team Size at Peak H: Over 15 members Comprehensive communications

    plan, frequent meetings, tight

    project management oversight

    Certainty Number of Interfaces to H: Over 3 Develop interface control

    Existing Systems Affected document immediately

     Project Definition

    Likely Narrow Knowledge Level M: Knowledgeable of Assigned Project Manager(s) to

    of Users user area only assess global implications

    Likely Available documentation M: More than 75% Balance of information to be clouds establishment of complete/current gathered by consultant baseline

    Unlikely Project Scope Creep L: Scope generally Scope intially defined in project

    defined, subject to plan, reviewed monthly by three

    revision groups (Project Manager and

    Steering Committee) to prevent

    undetected scope creep

    UnlikelyConsultant Project L: Well defined Included in project plan, subject

    Deliverables unclear to amendment

    Somewhat Vendor Project M: Estimated, not Included in project plan, subject

    likely Deliverables clearly defined to amendment

    Unlikely Cost Estimates Unrealistic L: Thoroughly Included in project plan, subject

    predicted by industry to amendment as new details

    experts using proven regarding project scope are

    practices to 15% revealed

    margin of error

    Somewhat Timeline Estimates M: Timeline assumes Timeline reviewed monthly by

    likely Unrealistic no derailment three groups (Project Manager

    and Steering Committee) to

    prevent undetected timeline

    departures

    UnlikelyNumber of Team Members L: Team well versed in Project Manager and consultant to

    Unknowledgeable of business operations identify knowledge gaps and

    Business impacted by technology provide training, as necessary

     Project Leadership

    Unlikely Steering Committee L: Identified and Frequently seek feedback to existence enthusiastic ensure continued support

    8

     Risk Risk Level Likelihood Mitigation Strategy

    L/M/Hof Event

     Unlikely Absence of Commitment L: Understands value & Frequently seek feedback to Level/Attitude of supports project ensure continued support Management

    Unlikely Absence of Commitment L: Understands value & Frequently seek feedback to Level/Attitude of Users supports project ensure continued support

    Unlikely Absence of Mid-L: Most understand Frequently seek feedback to Management Commitment value & support project ensure continued support

     Project Staffing

    Somewhat Project Team Availability M: Distributed team Continuous review of project

    likely makes availability momentum by all levels.

    questionable Consultant to identify any impacts

    caused by unavailability. If

    necessary, increase

    committmment by participants to

    full time status

    LikelyPhysical Location of Team M: Team is dispersed Use of Intranet project website, prevents effective among several sites comprehensive Communications management Plan

    Somewhat Project Team’s Shared M: Some have worked Comprehensive Communications

    likely Work Experience creates together before Plan poor working relationship

    Unlikely Weak User Participation on L: Users are part-time User Group Participants

    Project Team team members coordinated by full time employee

     Project Management

    Unlikely Procurement L: Procurement N/A Methodology Used foreign Methodology familiar to

    to team team

    Unlikely Change Management L: Well-defined N/A Procedures undefined

    Unlikely Quality Management L: Well-defined and N/A Procedures unclear accepted

     Software Vendor

    Certainty Number of Times Team H: Never A comprehensive vendor

    Has Done Prior Work with evaluation and selection process Vendor Creates Foreign (incorporated into Project Plan) Relationship will be employed to predict and

    define the relationship between

    the department and the vendor

    Somewhat Team’s Lack of Knowledge M: Conceptual Comprehensive vendor evaluation

    likely of Package understanding and selection process incorporated

    into Project Plan will assist the

    team in better understanding the

    package offering(s)

    9

Report this document

For any questions or suggestions please email
cust-service@docsford.com