Technology Project Plan

Read Complete Research Material

Technology Project Plan

Technology Project Plan

Technology Project Plan

The Charter Communication Technology Project Plan will supply a delineation of the task, encompassing the project's goals and objectives. Additionally, the Plan will assist as an affirmation between the next parties: Project Sponsor, Steering Committee, Project Manager, Project Team, and other staff affiliated with and/or influenced by the project.The Project Plan characterises the following:

Project principle

Business and project aims and goals

Possibility and expectations

Tasks and responsibilities

Suppositions and limitations

Project management thinking

Ground rules for the project

Project financial plan

Project timeline

The conceptual design of new technology

Background Information/Available Alternatives

Debbie: This section should explain the work you have done to date, the options you had with regard to hardware/software, and an description of how you arrived at the conclusion to use L3 and Tiburon.(Bent,2005)

Project Approach

This section should outline the way you will roll out the technology, including the highest level milestones.

For example:

Phase I: Safe concord with vendors (L3 and Tiburon)

Phase II:              Order/Install Equipment

Phase III:              Install/Test Software

Phase IV:              Perform Hardware/Software Testing

Phase V:              Carry out Training

Phase VI:              Execute ARS/AFR.

Business Goals and Objectives

The business aims and purposes 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.

Risk Assessment

The primary Risk Assessment (following page) endeavours to recognise, distinuish, prioritize and article a mitigation set about relation to those dangers which can be recognised former to the start of the project.The Risk Assessment will be relentlessly supervised and revised all through the life of the task, with monthly evaluations encompassed in the rank report (see Communications Plan) and open to amendment by the Project Manager. (Bent,2005)

Because mitigation advances should be acquiesced upon by task authority (based on the considered influence of the risk, the project's proficiency to accept the risk, and the feasibility of mitigating the risk), it is essential to assign time into each Steering Committee gathering, dedicated to recognising new dangers and considering mitigation strategies. Skamris,2002)

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: ...
Related Ads