Student Name
Capella University
PM-FPX4060 Risk Management in Project Management
Prof. Name:
Date
This project charter outlines the necessary components for upgrading Webster Insurance’s current customer service platform to the GCSP (Guided Customer Service Program).
Project Title: Guided Customer Service Program
Project Start Date: June 1, 2021
Project Finish Date: May 31, 2023
Budget: The project has a total budget of $2,000,000. This amount is allocated as follows:
The project will consist of various deliverables, all fitting within the $2 million budget limit. A cost overrun exceeding 4% will render the project unsuccessful.
Project Manager: Angela Guthrie
The primary goal of this project is to implement the GCSP, replacing the existing customer service database with minimal operational disruptions. Webster Insurance’s current system can no longer support its growing membership base, resulting in frequent delays and system crashes that negatively impact customer service (Ganesh, 2020). The new platform must:
The deliverables for Project GCSP will be organized according to different phases of the project. Each phase’s requirements may evolve, and any changes must be updated and approved.
The objectives will be met by utilizing data from the current platform and incorporating it into the new GCSP system with enhancements for better usability. The project will focus on:
RBS ID | Question | Answer | Mitigation | Assigned Preliminary Action |
---|---|---|---|---|
1.1 | Scope of the project clearly defined? | Yes | Validate scope through customer meetings | Confirm scope of work matches supply. |
1.2 | Project deliverables clearly identified? | Yes | Send preliminary data for approval | Ensure all systems can integrate with the new platform. |
1.3 | Estimates, assumptions vetted? | TBD | Vet suppliers and regulatory bodies | Verify estimates and assumptions. |
1.4 | Support facilities sufficient? | Yes | Purchase Salesforce license | Confirm compatibility with new platform requirements. |
1.5 | IT systems support integration? | Yes | Verify legacy system compatibility | Ensure API feeds are compatible. |
1.6 | Dependencies on other projects? | No | N/A | No action needed. |
1.7 | Design aligned with requirements? | Yes | Final program to meet CMS compliance | Ensure design is user-friendly and functional for fast service. |
1.8 | Will deliverables meet performance needs? | Yes | Ensure CMS compliance is met | Test functionality and operability. |
1.9 | Stability and maintainability confirmed? | TBD | Verify functionality and operability | Regular testing to confirm maintainability. |
1.10 | Is the solution safe? | No | N/A | N/A |
1.11 | Will the system be secure? | Yes | Ensure HIPAA compliance | Security checks throughout project phases. |
Name | Role | Phase | Responsibility |
---|---|---|---|
Steve Smith | Project Sponsor | All Phases | Approval of scope and budget increases |
Angela Guthrie | Project Manager | All Phases | Manage all project aspects |
Ingrid Sing | Product Manager | Phase 3.0 Design & Engineering | Ensure program meets project criteria |
Tracy Weave | HR Manager | All Phases | Manage HR tasks |
Gina Willis | Procurement Manager | All Phases | Oversee procurement and financial activities |
Deb Keplin | Project Administrator | All Phases | Track change orders, meeting notes, liaise |
Danny Senn | Integration Manager | Phase 4.0 Integration | Ensure program integrates with legacy systems |
Joyce Miller | Usability Manager | Phase 4.0 Integration | Test usability during integration |
Beatrice Jones | Customer Representative | All Phases | Ensure customer interests are represented |
Team Member Signatures: The following individuals have signed below as a confirmation of their role and responsibility in the project:
Team Member Signatures:
Project Manager: Angela Guthrie
Project Sponsor: Steve Smith
Product Manager: Ingrid Sing
Human Resources Manager: Tracy Weave
Procurement Manager: Gina Willis
Project Administrator: Deb Keplin
Integration Manager: Danny Senn
Usability Manager: Joyce Miller
Customer Representative: Beatrice Jones
Project Scope: The primary goal of this project is to replace the current customer service platform while adhering to CMS compliance and HIPAA regulations. The program aims to offer an improved, user-friendly experience for call center staff, enhancing member interactions and overall customer satisfaction.
Project Overview: Project GCSP (Guided Customer Service Program) is Webster Insurance’s new initiative aimed at enhancing their customer service platform. This change is necessitated by the existing platform’s inability to scale with the company’s expanding business, leading to frequent system crashes and customer dissatisfaction. Webster Insurance has allocated a budget of $2 million to develop the new platform, with expectations of reducing average handle time and realizing cost savings. The company anticipates a return on investment (ROI) within 18 months post-deployment. Upon approval, the project will commence on June 1, 2021, with a planned completion date of May 31, 2023.
Work Breakdown Structure (WBS): The Work Breakdown Structure (WBS) provides a detailed outline of the project’s key phases and tasks:
1.0 Project Initiation
1.1 Verify Customer’s Needs/Project
1.2 Create Project Schedule/Milestones
1.3 Confirm Salesforce as Software
1.4 Determine Stakeholders
2.0 Bid Phase
2.1 Develop Bid/RFP
2.2 Release Bid/RFP Document
2.3 Post Bid with Potential Suppliers
2.4 Secure Supplier
3.0 Develop, Design, Integrate
3.1 Design Responsibility Matrix
3.2 Design of New System
3.3 Design Approval
3.4 Final Release of Program
4.0 Monitor and Control
4.1 Begin Usability Testing
4.2 Finalize Deployment
4.3 Install and Confirm Access for Users
5.0 Close
5.1 Perform Compliance Testing
5.2 Customer Training
5.3 Customer Sign-off/Lessons Learned
WBS # | Task Description | Date Required | Budget |
---|---|---|---|
0.0 | Customer Service Platform | Â | $2,000,000.00 |
1.0 | Project Initiation | Â | Â |
1.1 | Verify Customer’s Needs/Project | 6/1/21 |  |
1.2 | Create Project Schedule/Milestones | 7/1/21 | Â |
1.3 | Confirm Salesforce as Software | 6/15/21 | Â |
1.4 | Determine Stakeholders and Responsibilities | 7/1/21 |
Risk Breakdown Structure (RBS): The Risk Breakdown Structure identifies the risks involved in this project. According to Hillson (2002), the upper levels of the RBS provide a comprehensive view of potential risks, ensuring coverage during the identification phase.
Budget: The project’s budget is set at $2 million based on estimated costs for software and vendor services. This budget is fixed with no additional funds available.
Communications Matrix: The Communications Matrix details the responsibilities for different communication elements, ensuring clarity regarding information dissemination among team members.
Information Provider | Recipient(s) | Frequency | Medium | Location |
---|---|---|---|---|
PM | Sponsor | Weekly | Microsoft Teams Channel | |
PM | Sponsor | As Needed | Microsoft Teams Channel | |
PM | Sponsor | As Arise | Phone | Microsoft Teams Channel |
Stakeholder Communications Analysis: The analysis defines the communication needs of each stakeholder, including document type, format, and due dates, ensuring that essential information reaches the appropriate individuals.
Stakeholder | Document Name | Document Format | Contact Person | Due Date |
---|---|---|---|---|
Executive Sponsor | Monthly Status Report | Hard Copy | Deb Keplin | Last Friday of Each Month |
RACI Matrix: The RACI Matrix outlines who is Responsible, Accountable, Consulted, and Informed for each project task.
Risk Matrix: The Risk Matrix serves as a core tool for identifying and mitigating potential risks that could impact the project’s scope, cost, and quality.
ID | Rank | Risk | Probability | Severity | Mitigation Approach | Status | Category | Watch List? |
---|---|---|---|---|---|---|---|---|
1 | 10 | Team Skill Sets | Medium | High | Train team on new technology | Ongoing | Personnel | Low |
Risk Stakeholder Roles and Responsibilities: The project manager is primarily responsible for overseeing the risk management plan, reporting to sponsors, and updating risk statuses.
Risk Management Process and Activities: The risk management process includes the identification of risks at the project’s onset and throughout its life cycle. Regular updates to the risk watch list ensure that priorities are managed effectively.
Hillson, D. (2002). Use a risk breakdown structure (RBS) to understand your risks. Paper presented at Project Management Institute Annual Seminars & Symposium, San Antonio, TX. Newtown Square, PA: Project Management Institute.
Hillson, D., & Simon, P. (2012). Practical project risk management: The ATOM methodology (2nd ed.). Vienna, VA: Management Concepts.
Project Management Institute. (2017). Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Sixth Edition and Agile Practice Guide.
Pcubed. (2004). Risk identification questionnaire [Microsoft Word template]. Retrieved from http://office.microsoft.com/en-us/templates/risk-identification-questionnaireTC001142331.aspx
Post Categories
Tags