Mis 4596 Project Charter Got Your Back



Download 60.51 Kb.
Date conversion08.07.2018
Size60.51 Kb.
MIS 4596

Project Charter
Got Your Back


Project Title

GotYourBack

Product/Process Impacted

Police Force

Start Date

2/1/16

Organization/Department

MIS

Target Completion Date

4/19/16

Champion

Messina

Version

3

Revision Date

4/18/2016





Description





1. Project Description




New technology is constantly emerging, and with information systems playing a huge role in today’s society, people are utilizing technology new ways every day. Our system, known as “Got Your Back,” utilizes Google Glass to solve one of the biggest dilemmas of today’s society: creating transparency between law enforcement and society while providing a new level of safety for police officers. During our research and interviews, we found that many police officers have gripes with body cameras. They understand the reasoning for them, but the cameras provide no protection in their opinion. Jim Buerrmann, President of the police foundation in Washington stated: “Within the next five years or so, body-worn cameras will be as ubiquitous in the world of policing as handcuffs, the police radio, and the gun. We believe that our idea can benefit both sides greatly by providing safety for both citizens and law enforcement by not only recording video but also live-streaming the video back to the dispatcher. This system allows the dispatcher to act as a second pair of eyes and make split-second decisions that can further benefit the officer. It is paramount to our group that we provide not just citizens with the added protection of video recording, but that we increase the level of safety provided to law enforcement.








2. Project Scope




We will focus on the software aspect of the body camera, and not necessarily the hardware as much. Our system will be compatible with different types of glasses, but created specifically for Google Glass. Our top interest is marketing our software that creates a two way communication between officers and dispatchers.









  1. Project Goal and Deliverables

We must deliver software that readily meets the needs of the police officers and dispatchers. That means a successful two-way communication between the officers’ glasses and the dispatcher. Our main deliverable is the software for the body cameras that provides our service.










Metrics


Baseline


Current


Goal















Cost Reduction.

Reduce costs for Police Departments



3 Years

0

$9,232,000

(over 3 years)


















Crime Reduction.

Reduce crime in local towns and cities by



6 Weeks

0

10%
















Use of Force Reduction. Reduce force by officers

6 Weeks

0

60%
















Customer Satisfaction.

Reduce complaints



6 Months

70%

85%







4. Business Results Expected






Benefits to our organization when this project is complete are profitability and serving the greater good with IT and IS. Partnerships with Police Departments and the Government.




5. Team members




Team Members: Ashley Lombardo, Stephen Scanlon, Jack Portnoy, Peter Hwang

Champion: Anthony Messina


Ashley Lombardo - Project Manager

Stephen Scanlon – Prototype Lead

Jack Portnoy – Document Manager

Peter Hwang - Business Analyst


The team can turn to our champion, key stakeholders, and mentors if we run into any issues or need expert guidance.




6. Support Required and risks




Additional resources needed: Google Glass, JustInMind

Support: Police Department and Government support for implementation

Risks: lack of resources, privacy issues, data ownership, and the connection between the system and the process of the Google Glass with our new technology.






7. Customer Benefits




The people using the claims dispute process will get faster results and resolution of their claim. This should result in better customer satisfaction levels with the process as well as improved productivity of service operators through fewer status inquiries.





8. Technology Architecture




Google Glass: 0 experience

Justinmind: Steve – proficient

Ashley – limited

Peter – limited



Jack – limited

Collaborative Tools: Google Drive, GroupMe, MIS Community Site








9. Overall schedule/Work Breakdown Structure (Key milestones & dates)


Responsible

individual

Output (notes, diagrams, interviews, screen prints)

Date started if in progress

Or Expected completion date

Date completed or date completion is expected




Planning



ALL

Interview with Temple Police, notes on how cameras work at other police departments

2/1/16

2/7/16




Analysis



ALL

User Needs Analysis

2/8/16

2/20/16




Design



ALL

Diagram of the capabilities of the Google Glass, Flow Chart of the process of GotYourBack technology

2/22/16

3/1/16




Implementation: Construction



Steve

JustInMind Prototype basic development

3/8/16

Expected:

4/10/16





Implementation: Testing



ALL

Functional screens of prototype

4/1/16

Expected:

4/15/16





Installation



ALL

Working Prototype

4/18/16

Expected:

4/20/16





Charter Development Guidelines: Examples are in italics. You can expand the form to meet your requirements as you enter text.
Project Title: Enter the name for your project – the name should convey a sense of purpose. Should contain an action word; such as – improve, develop, implement, reduce, etc.

Reduce Cycle Time for Resolving Disability Disputes
Product/Process Impacted: What you are working on.

Disability Claim Process
Champion: The sponsor of the project.

Department Head
Organization: Where you work.

Corporate HQ – Shared Services
Start Date: This is the first day on the project.
Target Completion Date: This is depending on the negotiated time line and scope with the sponsor.


  1. Project Description: Several sentences addressing: why you are undertaking this project, the magnitude of the problem, general approach to be taken and expected benefits.

The Shared Services Benefits Group receives on average 30 claim appeals per month. Many of these are resolved by providing information clarifying the process and others should have been handled locally or by directly working with the service provider. This project will improve the process currently in use so that calls/claims are resolved quicker. This will allow members of this organization to focus on more strategic issues and will improve client satisfaction and eliminate re-work.




  1. Project Scope: What the boundaries are of the process that you are going to be working on.

This "Process" begins with opening of a claim dispute and ends when the disputed claim case being closed.




  1. Project Goal: Describe the target(s) that you are planning to achieve. Reduce cycle time by 50%, reduce cost per computer installation by 50% etc. If you don’t have a quantifiable target then you cannot claim that you have reached your goal.

Include the historical baseline information. The current value for the process will be updated as the project progresses toward your goal.


For cycle time: Baseline- 2 days, Current- 2 days, Goal- 1 day (the goal reflects the 50% reduction from baseline)

For cost: Baseline- $1000, Current- $800, Goal- $500 (the goal reflects the 50% reduction from baseline)
You may have other metrics that you are working to impact; if so, substitute them for any that don’t apply. You may have only one metric and will rarely have more than three.


  1. Business Results: What the benefits are to your organization when this project is complete. How will this project impact your organizations “Dashboard” metrics? What will be the impact to the financial bottom line?




  1. Team Members: List the dedicated team members and also any other regular contributors to the success of the project.




  1. Support Required: Identify other resources that may be required, such as outside consultants etc.




  1. Customer Benefits: What the benefits are to the customers of this project if the process/product is improved.

The people using the claims dispute process will get faster results and resolution of their claim. This should result in better customer satisfaction levels with the process as well as improved productivity of service operators through fewer status inquiries.


  1. Technology Architecture: What are the tools you will be using (development tools, data base, etc)? How will you obtain the tools? What is the level of experience of specific team members with these tools?




  1. Schedule: Enter the anticipated dates that you will complete each phase of the project; work with your champion to determine these dates.


The database is protected by copyright ©dentisty.org 2016
send message

    Main page