1 / 19

GAZCars Conversion Management System Project Overview and Risk Coordination

This document outlines the project for implementing a new system to enhance GAZCars' conversion management. The system is aimed at improving reliability and customer confidence as the business expands, addressing existing database issues. Key components include stakeholder engagement, defined scope, project scheduling, and risk management strategies to reduce project failure likelihood. Additionally, strong emphasis on quality assurance is highlighted, ensuring all deliverables meet client expectations. The project is currently overdue, necessitating immediate focus on mitigating risks and maintaining quality.

kort
Télécharger la présentation

GAZCars Conversion Management System Project Overview and Risk Coordination

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Briefing

  2. Agenda Managing Risks Controlling Changes Ensuring Quality Summary Questions • Business Case • Stakeholder Engagement • Scope • Schedule • Status

  3. 1. Business Case • New system for managing GAZCars conversions • Fully specified in 15 Weeks • Cost of inaction is much higher than action • Existing system is unreliable • Instil customer confidence (conversion choices) • Contact with existing customers simplified

  4. 2. Stakeholder Engagement • Stakeholders identified via GAZCars Industry Briefing Paper and liaising with client representatives • Online forums • Stakeholders documented in Project Management Plan • Stakeholder engagement outlined in Communications Plan

  5. 3a. Scope IN SCOPE • Database design • Decision support system OUT OF SCOPE • Online booking system

  6. 3b. Scope (deliverables) IN SCOPE • Complete project document suite • Project planning documentation • Requirements analysis documentation • Design documentation OUT OF SCOPE • Working prototype

  7. 4a. Schedule • Four phases • Project Planning • Requirements Analysis • Design • Project Closure

  8. 4b. Schedule(link)

  9. Complete In Progress 5. Status Overdue

  10. 6a. Managing Risks

  11. 6b. Key Project Risks • Team members with limited time and availability • Loss of team members • Unclear requirements • Uncertainty over responsibilities

  12. 6c. Risk Register

  13. 7a. Controlling changes

  14. 7b. Controlling changes Complete Promised Deliverables On-Time Risk Mitigation Measure Possible Project Failure Reduction in Project Scope Adapt to Lost Team Member

  15. 8. Ensuring Quality Quality Reviews Product Descriptions Deliverable Quality Assurance Checklists Agreed with client Product Descriptions Deliverable Quality Assurance Checklists Final team review Sign-off by client

  16. 9. Summary Problems: • Existing database is a mess • GAZCars Business is expanding • Require increased functionality and reliability • Customer Conversion Decision Support • Online Booking System Solution : PG Project Maniacs GAZCars EMS 2.0 17

  17. Citations: Stumpf, R and Teague, L 2005, Object-Oriented Systems Analysis and Design with UML, Pearson, New Jersey 18

  18. 10. Questions...

More Related