SlideShare a Scribd company logo
Implementation Plan – X Corporation
06 10, 2016
NETW-471
Professor Tinmaz
Team Members: Jared Bourne, Cesar Pena
Introduction
The WBS documented here will outline the steps required to fully implement the Field Aware
field service management solution from purchase to the point a fully functional system.
Work Breakdown Structure - Outline
FieldAware & Support App Implementation Project
1.1 Initiation
1.1.1Evaluation & Recommendations
1.1.2Develop Project Charter
1.1.3Deliverable: Submit Project Charter
1.1.4Project Sponsor Reviews Project Charter
1.1.5Project Charter Signed/Approved
1.2 Planning
1.2.1Create Preliminary Scope Statement
1.2.2Determine Project Team
1.2.3Project Team Kickoff Meeting
1.2.4Develop Project Plan
1.2.5Submit Project Plan
1.2.6Milestone: Project Plan Approval
1.3 Execution
1.3.1Project Kickoff Meeting
1.3.2Verify & Validate User Requirements
1.3.3Design System
1.3.4Procure Hardware/Software
1.3.5Install Development System
1.3.6Testing Phase
1.3.7Install Live System
1.3.8User Training
1.3.9Go Live
1.4 Control
1.4.1Project Management
1.4.2Project Status Meetings
1.4.3Risk Management
1.4.4Update Project Management Plan
1.5 Closeout
1.5.1Audit Procurement
1.5.2Document Lessons Learned
1.5.3Update Files/Records
1.5.4Gain Formal Acceptance
1.5.5Archive Files/Documents
Work Breakdown Structure – Tree View
FieldAware
Field Mgmt System
Initiation
1.1
Evaluation &
Recommendations
1.1.1
Develop Project Charter
1.1.2
Deliverable: Submit
Project Charter
1.1.3
Project Sponsor Reviews
Project Charter
1.1.4
Project Charter
Signed/Approved
1.1.5
Planning
1.2
Create Preliminary Scope
Statement
1.2.1
Determine Project Team
1.2.2
Project Team Kickoff
Meeting
1.2.3
Develop Project Plan
1.2.4
Submit Project Plan
1.2.5
Milestone: Project Plan
Approved
1.2.6
Execution
1.3
Project Kickoff Meeting
1.3.1
Verify & Validate User
Requirements
1.3.2
Design System
1.3.3
Procure
Hardware/Software
1.3.4
Install Development
System
1.3.5
Testing Phase
1.3.6
Install Live System
1.3.7
User Training
1.3.8
Go Live
1.3.9
Control
1.4
Project Management
1.4.1
Project Status Meetings
1.4.2
Risk Management
1.4.3
Update Project
Management Plan
1.4.4
Closeout
1.5
Audit Procurement
1.5.1
Document Lessons
Learned
1.5.2
Update Files/ Records
1.5.3
Gain Formal Acceptance
1.5.4
Archive Files/
Documents
1.5.5
Level WBS
Code
Element Name Definition
1 1 Field Aware Field Management
System
All work to implement a new field
management system.
2 1.1 Initiation The work to initiate the project.
3 1.1.1 Evaluation & Recommendations Working group to evaluate solution sets
and make recommendations.
3 1.1.2 Develop Project Charter Project Manager to develop the Project
Charter.
3 1.1.3 Deliverable: Submit Project
Charter
Project Charter is delivered to the
Project Sponsor.
3 1.1.4 Project Sponsor Reviews Project
Charter
Project sponsor reviews the Project
Charter.
3 1.1.5 Project Charter
Signed/Approved
The Project Sponsor signs the Project
Charter which authorizes the Project
Manager to move to the Planning
Process.
2 1.2
Planning
The work for the planning process for
the project.
3 1.2.1 Create Preliminary Scope
Statement
Project Manager creates a Preliminary
Scope Statement.
3 1.2.2
Determine Project Team
The Project Manager determines the
project team and requests the
resources.
3 1.2.3
Project Team Kickoff Meeting
The planning process is officially
started with a project kickoff meeting
which includes the Project Manager,
Project Team and Project Sponsor
(optional).
3 1.2.4
Develop Project Plan
Under the direction of the Project
Manager the team develops the
project plan.
3 1.2.5
Submit Project Plan
Project Manager submits the project
plan for approval.
3 1.2.6
Milestone: Project Plan
Approval
The project plan is approved and the
Project Manager has permission to
proceed to execute the project
according to the project plan.
2 1.3 Execution Work involved to execute the project.
3 1.3.1
Project Kickoff Meeting
Project Manager conducts a formal
kick off meeting with the project team,
project stakeholders and project
sponsor.
3 1.3.2
Verify & Validate User
Requirements
The original user requirements is
reviewed by the project manager and
team, then validated with the
users/stakeholders. This is where
additional clarification may be needed.
3 1.3.3
Design System
The technical resources design the
new widget management system.
3 1.3.4
Procure Hardware/Software
The procurement of all hardware,
software and facility needs for the
project.
3 1.3.5
Install Development System
Team installs a development system
for testing and customizations of user
interfaces.
3 1.3.6
Testing Phase
The systemis tested with a select set
of users.
3 1.3.7
Install Live System
The actual systemis installed and
configured.
3 1.3.8
User Training
All users are provided with a four
hours training class. Additionally,
managers are provided with an
additional two hours class to cover
advanced reporting.
3 1.3.9 Go Live System goes live with all users.
2 1.4
Control
The work involved for the control
process of the project.
3 1.4.1
Project Management
Overall project management for the
project.
3 1.4.2 Project Status Meetings Weekly team status meetings.
3 1.4.3
Risk Management
Risk management efforts as defined in
the Risk Management Plan.
3 1.4.4
Update Project Management
Plan
Project Manager updates the Project
Management Plan as the project
progresses.
2 1.5 Closeout The work to close-out the project.
3 1.5.1
Audit Procurement
An audit of all hardware and software
procured for the project, ensures that
all procured products are accounted
for and in the asset management
system.
3 1.5.2
Document Lessons Learned
Project Manager along with the project
team performs a lessons learned
meeting and documents the lessons
learned for the project.
3 1.5.3
Update Files/Records
All files and records are updated to
reflect the widget management
system.
3 1.5.4
Gain Formal Acceptance
The Project Sponsor formally accepts
the project by signing the acceptance
document included in the project plan.
3 1.5.5
Archive Files/Documents
All project related files and documents
are formally archived.
Summary
X Corp has long prided itself as being a leading provider of Data, Internet, Voice and Managed
services in the US. We have achieved this distinction by providing outstanding service to our
customer base of over 4M subscribers. We are currently the fifth largest cable provider in the
United States. With our growth, we have experienced major issues with our call center
performance. Long wait times to schedule an appointment, 4 hour windows for service calls, an
onerous cancellation policy and technician failures to report to the customers home at the
scheduled time have resulted in low customer satisfaction and higher than normal churn. These
issues have affected our stock price and threaten our standing in the industry if not addressed
immediately. Our extensive research has led us to the FieldAware system, the leading field
service management solution available. This solution will allow for easier, significantly faster
appointment scheduling, eliminating long wait times. With improved accuracy and the ability
to match the most qualified technicians for each unique call, service calls will take less time and
allow our call center personnel to provide exact appointment times instead of windows.
Implementation will be supported throughout by experienced FieldAware Engineers and the
software can be customized to X Corps specific needs. Time from start to a fully deployed,
functional system is 120 days. The result will be increased customer satisfaction and higher
retention rates, ultimately resulting in increased revenues and share prices.

More Related Content

Similar to Implementation-Plan_X_Corp

Work Breakdown Structure (WBS) TemplateThis Project WB.docx
Work Breakdown Structure (WBS) TemplateThis Project WB.docxWork Breakdown Structure (WBS) TemplateThis Project WB.docx
Work Breakdown Structure (WBS) TemplateThis Project WB.docx
ambersalomon88660
 
Work Breakdown Structure Template(1).docx
Work Breakdown Structure Template(1).docxWork Breakdown Structure Template(1).docx
Work Breakdown Structure Template(1).docx
Shahid Farooq, PMP
 
Work BreakDown Structure
Work BreakDown StructureWork BreakDown Structure
Work BreakDown Structure
Abdul Aslam
 
MSF Process model
MSF Process modelMSF Process model
MSF Process model
unruliness
 
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit  EMR Implementation Plannin.docxAOHC EMR Implementation Toolkit  EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
festockton
 
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit  EMR Implementation Plannin.docxAOHC EMR Implementation Toolkit  EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
RAHUL126667
 
Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)
Logitrain: New Zealand
 
ITP-1 – Project CharterGroup 3 - The Project Management Masters .docx
ITP-1 – Project CharterGroup 3 - The Project Management Masters .docxITP-1 – Project CharterGroup 3 - The Project Management Masters .docx
ITP-1 – Project CharterGroup 3 - The Project Management Masters .docx
priestmanmable
 
James dimas it infrastructure approach
James dimas it infrastructure approachJames dimas it infrastructure approach
James dimas it infrastructure approach
James (JD) Dimas
 
Agile lifecycle handbook by bhawani nandan prasad
Agile lifecycle handbook by bhawani nandan prasadAgile lifecycle handbook by bhawani nandan prasad
Agile lifecycle handbook by bhawani nandan prasad
Bhawani N Prasad
 
SNSasikumar-Present R&R
SNSasikumar-Present R&RSNSasikumar-Present R&R
SNSasikumar-Present R&R
SASIKUMAR SN
 
The Software Engineering Profession SWE311The Software Enginee.docx
The Software Engineering Profession SWE311The Software Enginee.docxThe Software Engineering Profession SWE311The Software Enginee.docx
The Software Engineering Profession SWE311The Software Enginee.docx
ssusera34210
 
Pmt 01
Pmt 01Pmt 01
Software Product Life Cycle
Software Product Life CycleSoftware Product Life Cycle
Software Product Life Cycle
Mahesh Panchal
 
Online cinematicketingdocx
Online cinematicketingdocxOnline cinematicketingdocx
Online cinematicketingdocx
Donna Mae Laurente
 
Project charter and plan document for millennium upgrade
Project charter and plan document for millennium upgradeProject charter and plan document for millennium upgrade
Project charter and plan document for millennium upgrade
Theodore Van Patten, Jr.
 
Presentation by saurabh chandra
Presentation by saurabh chandraPresentation by saurabh chandra
Presentation by saurabh chandra
PMI_IREP_TP
 
RUNNING HEAD Customer Care Website Implementation1Customer .docx
RUNNING HEAD Customer Care Website Implementation1Customer .docxRUNNING HEAD Customer Care Website Implementation1Customer .docx
RUNNING HEAD Customer Care Website Implementation1Customer .docx
joellemurphey
 
Some of the Material in this paper has been repurposed from C.docx
Some of the Material in this paper has been repurposed from C.docxSome of the Material in this paper has been repurposed from C.docx
Some of the Material in this paper has been repurposed from C.docx
whitneyleman54422
 
Agile concepts
Agile conceptsAgile concepts
Agile concepts
Joaquim Ferreira
 

Similar to Implementation-Plan_X_Corp (20)

Work Breakdown Structure (WBS) TemplateThis Project WB.docx
Work Breakdown Structure (WBS) TemplateThis Project WB.docxWork Breakdown Structure (WBS) TemplateThis Project WB.docx
Work Breakdown Structure (WBS) TemplateThis Project WB.docx
 
Work Breakdown Structure Template(1).docx
Work Breakdown Structure Template(1).docxWork Breakdown Structure Template(1).docx
Work Breakdown Structure Template(1).docx
 
Work BreakDown Structure
Work BreakDown StructureWork BreakDown Structure
Work BreakDown Structure
 
MSF Process model
MSF Process modelMSF Process model
MSF Process model
 
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit  EMR Implementation Plannin.docxAOHC EMR Implementation Toolkit  EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
 
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit  EMR Implementation Plannin.docxAOHC EMR Implementation Toolkit  EMR Implementation Plannin.docx
AOHC EMR Implementation Toolkit EMR Implementation Plannin.docx
 
Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)Project Management for IT-related Projects (Logitrain)
Project Management for IT-related Projects (Logitrain)
 
ITP-1 – Project CharterGroup 3 - The Project Management Masters .docx
ITP-1 – Project CharterGroup 3 - The Project Management Masters .docxITP-1 – Project CharterGroup 3 - The Project Management Masters .docx
ITP-1 – Project CharterGroup 3 - The Project Management Masters .docx
 
James dimas it infrastructure approach
James dimas it infrastructure approachJames dimas it infrastructure approach
James dimas it infrastructure approach
 
Agile lifecycle handbook by bhawani nandan prasad
Agile lifecycle handbook by bhawani nandan prasadAgile lifecycle handbook by bhawani nandan prasad
Agile lifecycle handbook by bhawani nandan prasad
 
SNSasikumar-Present R&R
SNSasikumar-Present R&RSNSasikumar-Present R&R
SNSasikumar-Present R&R
 
The Software Engineering Profession SWE311The Software Enginee.docx
The Software Engineering Profession SWE311The Software Enginee.docxThe Software Engineering Profession SWE311The Software Enginee.docx
The Software Engineering Profession SWE311The Software Enginee.docx
 
Pmt 01
Pmt 01Pmt 01
Pmt 01
 
Software Product Life Cycle
Software Product Life CycleSoftware Product Life Cycle
Software Product Life Cycle
 
Online cinematicketingdocx
Online cinematicketingdocxOnline cinematicketingdocx
Online cinematicketingdocx
 
Project charter and plan document for millennium upgrade
Project charter and plan document for millennium upgradeProject charter and plan document for millennium upgrade
Project charter and plan document for millennium upgrade
 
Presentation by saurabh chandra
Presentation by saurabh chandraPresentation by saurabh chandra
Presentation by saurabh chandra
 
RUNNING HEAD Customer Care Website Implementation1Customer .docx
RUNNING HEAD Customer Care Website Implementation1Customer .docxRUNNING HEAD Customer Care Website Implementation1Customer .docx
RUNNING HEAD Customer Care Website Implementation1Customer .docx
 
Some of the Material in this paper has been repurposed from C.docx
Some of the Material in this paper has been repurposed from C.docxSome of the Material in this paper has been repurposed from C.docx
Some of the Material in this paper has been repurposed from C.docx
 
Agile concepts
Agile conceptsAgile concepts
Agile concepts
 

Implementation-Plan_X_Corp

  • 1. Implementation Plan – X Corporation 06 10, 2016 NETW-471 Professor Tinmaz Team Members: Jared Bourne, Cesar Pena
  • 2. Introduction The WBS documented here will outline the steps required to fully implement the Field Aware field service management solution from purchase to the point a fully functional system. Work Breakdown Structure - Outline FieldAware & Support App Implementation Project 1.1 Initiation 1.1.1Evaluation & Recommendations 1.1.2Develop Project Charter 1.1.3Deliverable: Submit Project Charter 1.1.4Project Sponsor Reviews Project Charter 1.1.5Project Charter Signed/Approved 1.2 Planning 1.2.1Create Preliminary Scope Statement 1.2.2Determine Project Team 1.2.3Project Team Kickoff Meeting 1.2.4Develop Project Plan 1.2.5Submit Project Plan 1.2.6Milestone: Project Plan Approval 1.3 Execution 1.3.1Project Kickoff Meeting 1.3.2Verify & Validate User Requirements 1.3.3Design System 1.3.4Procure Hardware/Software 1.3.5Install Development System 1.3.6Testing Phase 1.3.7Install Live System 1.3.8User Training 1.3.9Go Live 1.4 Control 1.4.1Project Management 1.4.2Project Status Meetings 1.4.3Risk Management 1.4.4Update Project Management Plan 1.5 Closeout 1.5.1Audit Procurement 1.5.2Document Lessons Learned 1.5.3Update Files/Records 1.5.4Gain Formal Acceptance 1.5.5Archive Files/Documents
  • 3. Work Breakdown Structure – Tree View FieldAware Field Mgmt System Initiation 1.1 Evaluation & Recommendations 1.1.1 Develop Project Charter 1.1.2 Deliverable: Submit Project Charter 1.1.3 Project Sponsor Reviews Project Charter 1.1.4 Project Charter Signed/Approved 1.1.5 Planning 1.2 Create Preliminary Scope Statement 1.2.1 Determine Project Team 1.2.2 Project Team Kickoff Meeting 1.2.3 Develop Project Plan 1.2.4 Submit Project Plan 1.2.5 Milestone: Project Plan Approved 1.2.6 Execution 1.3 Project Kickoff Meeting 1.3.1 Verify & Validate User Requirements 1.3.2 Design System 1.3.3 Procure Hardware/Software 1.3.4 Install Development System 1.3.5 Testing Phase 1.3.6 Install Live System 1.3.7 User Training 1.3.8 Go Live 1.3.9 Control 1.4 Project Management 1.4.1 Project Status Meetings 1.4.2 Risk Management 1.4.3 Update Project Management Plan 1.4.4 Closeout 1.5 Audit Procurement 1.5.1 Document Lessons Learned 1.5.2 Update Files/ Records 1.5.3 Gain Formal Acceptance 1.5.4 Archive Files/ Documents 1.5.5
  • 4. Level WBS Code Element Name Definition 1 1 Field Aware Field Management System All work to implement a new field management system. 2 1.1 Initiation The work to initiate the project. 3 1.1.1 Evaluation & Recommendations Working group to evaluate solution sets and make recommendations. 3 1.1.2 Develop Project Charter Project Manager to develop the Project Charter. 3 1.1.3 Deliverable: Submit Project Charter Project Charter is delivered to the Project Sponsor. 3 1.1.4 Project Sponsor Reviews Project Charter Project sponsor reviews the Project Charter. 3 1.1.5 Project Charter Signed/Approved The Project Sponsor signs the Project Charter which authorizes the Project Manager to move to the Planning Process. 2 1.2 Planning The work for the planning process for the project. 3 1.2.1 Create Preliminary Scope Statement Project Manager creates a Preliminary Scope Statement. 3 1.2.2 Determine Project Team The Project Manager determines the project team and requests the resources. 3 1.2.3 Project Team Kickoff Meeting The planning process is officially started with a project kickoff meeting which includes the Project Manager, Project Team and Project Sponsor (optional). 3 1.2.4 Develop Project Plan Under the direction of the Project Manager the team develops the project plan. 3 1.2.5 Submit Project Plan Project Manager submits the project plan for approval.
  • 5. 3 1.2.6 Milestone: Project Plan Approval The project plan is approved and the Project Manager has permission to proceed to execute the project according to the project plan. 2 1.3 Execution Work involved to execute the project. 3 1.3.1 Project Kickoff Meeting Project Manager conducts a formal kick off meeting with the project team, project stakeholders and project sponsor. 3 1.3.2 Verify & Validate User Requirements The original user requirements is reviewed by the project manager and team, then validated with the users/stakeholders. This is where additional clarification may be needed. 3 1.3.3 Design System The technical resources design the new widget management system. 3 1.3.4 Procure Hardware/Software The procurement of all hardware, software and facility needs for the project. 3 1.3.5 Install Development System Team installs a development system for testing and customizations of user interfaces. 3 1.3.6 Testing Phase The systemis tested with a select set of users. 3 1.3.7 Install Live System The actual systemis installed and configured. 3 1.3.8 User Training All users are provided with a four hours training class. Additionally, managers are provided with an additional two hours class to cover advanced reporting. 3 1.3.9 Go Live System goes live with all users. 2 1.4 Control The work involved for the control process of the project.
  • 6. 3 1.4.1 Project Management Overall project management for the project. 3 1.4.2 Project Status Meetings Weekly team status meetings. 3 1.4.3 Risk Management Risk management efforts as defined in the Risk Management Plan. 3 1.4.4 Update Project Management Plan Project Manager updates the Project Management Plan as the project progresses. 2 1.5 Closeout The work to close-out the project. 3 1.5.1 Audit Procurement An audit of all hardware and software procured for the project, ensures that all procured products are accounted for and in the asset management system. 3 1.5.2 Document Lessons Learned Project Manager along with the project team performs a lessons learned meeting and documents the lessons learned for the project. 3 1.5.3 Update Files/Records All files and records are updated to reflect the widget management system. 3 1.5.4 Gain Formal Acceptance The Project Sponsor formally accepts the project by signing the acceptance document included in the project plan. 3 1.5.5 Archive Files/Documents All project related files and documents are formally archived.
  • 7. Summary X Corp has long prided itself as being a leading provider of Data, Internet, Voice and Managed services in the US. We have achieved this distinction by providing outstanding service to our customer base of over 4M subscribers. We are currently the fifth largest cable provider in the United States. With our growth, we have experienced major issues with our call center performance. Long wait times to schedule an appointment, 4 hour windows for service calls, an onerous cancellation policy and technician failures to report to the customers home at the scheduled time have resulted in low customer satisfaction and higher than normal churn. These issues have affected our stock price and threaten our standing in the industry if not addressed immediately. Our extensive research has led us to the FieldAware system, the leading field service management solution available. This solution will allow for easier, significantly faster appointment scheduling, eliminating long wait times. With improved accuracy and the ability to match the most qualified technicians for each unique call, service calls will take less time and allow our call center personnel to provide exact appointment times instead of windows.
  • 8. Implementation will be supported throughout by experienced FieldAware Engineers and the software can be customized to X Corps specific needs. Time from start to a fully deployed, functional system is 120 days. The result will be increased customer satisfaction and higher retention rates, ultimately resulting in increased revenues and share prices.