MS, Information Technology Management Capstone - C498 1
Radeon Homes Microsoft Office 365 Migration Post-Implementation Report
Western Governors University
, 2
Abstract
Radeon Homes experienced decreased customer satisfaction, productivity, and efficiency and
increased response times. After careful analysis, it was determined that these issues were due to
how the teams collaborated internally and externally. Radeon was using email as a primary
source of communication for employees. This led to overwhelming emails, and the teams could
not keep up with demand, which affected Radeon’s customers. As IT Manager for Radeon
Homes, I proposed migrating to Microsoft Office 365 (O365) as the replacement solution. Office
365 is a cloud-based solution billed per license, flexible enough to grow as the company grows.
This license structure can be added to include voice solutions and can be further tailored to
Radeon’s needs. An agile methodology was used during the deployment, breaking the project
into four phases: Planning, Execution, Monitoring, and Project Closure. The project was
communicated to key stakeholders via the project dashboard and ongoing communication with
KPI status updates. At the end of the project, the success was measured by employee surveys and
questionnaires along with ongoing customer feedback requests. The project was successfully
completed. All milestones were met, all costs were accounted for, and there was no need to dip
into the risk reserves. The project is complete, including all training the Microsoft consulting
team provides. All legacy infrastructure has been turned down, and all current collaboration is
maintained through the Microsoft Office 365 cloud management portal.
Keywords: Microsoft Office 365, O365, collaboration
, 3
Table of Contents
Abstract............................................................................................................................................2
Quality Assurance............................................................................................................................7
Formative Evaluation and QA Metrics............................................................................8
Testing Methodology.......................................................................................................9
Test Cases......................................................................................................................10
Acceptance Criteria........................................................................................................10
Project Review...............................................................................................................................11
Assumptions...................................................................................................................11
Project Phases................................................................................................................12
Timeline Deviations.......................................................................................................14
Project Dependencies.....................................................................................................15
Resource Requirements.................................................................................................16
Implementation Project Milestones...............................................................................18
Project Deliverables.......................................................................................................20
Documentation Deliverables..........................................................................................21
Formative Evaluation Results and Revisions................................................................................28
Summative Evaluation Plan and Results.......................................................................................28
Stakeholder Communication Plan and Reports.............................................................................29
Ongoing Support and Maintenance...............................................................................................30
, 4
Resources for Post-Implementation Support.................................................................31
Short and Long-Term Maintenance Plan.......................................................................31
Post-Implementation Project Summary.........................................................................................32
Documentation Deliverables..........................................................................................33
Success Criteria for Each Project Outcome...................................................................35
Justification of Proposed versus Actual Project Outcomes...........................................36
Lessons Learned.............................................................................................................36
The completion of this project learned two lessons. The first lesson is the importance
of building in extra time for unforeseen circumstances. While the Radeon team did much
preparatory work to ensure all areas of the project that could be controlled were accounted for,
Microsoft had a network outage that pushed the project by three days. Thankfully, the Radeon
and Microsoft consulting teams were able to make up the time elsewhere, but that may not
always be the case for future projects........................................................................................36
The second lesson learned was the benefit of having a contingency plan for not only
migratory purposes but also the risk reserve. Had the outage been extended, the team may
have had to revert to the legacy infrastructure, and depending on labor costs, they may have
had to dip into the risk reserve fund. Risk planning is critical for all future projects for the
company. There is only so much the team can control. All risks must be evaluated, and a
quantitative and qualitative risk analysis should be done to evaluate how it can affect the
progression of the project and ROI for the business..................................................................36
References......................................................................................................................................38
Tables.............................................................................................................................................41
Radeon Homes Microsoft Office 365 Migration Post-Implementation Report
Western Governors University
, 2
Abstract
Radeon Homes experienced decreased customer satisfaction, productivity, and efficiency and
increased response times. After careful analysis, it was determined that these issues were due to
how the teams collaborated internally and externally. Radeon was using email as a primary
source of communication for employees. This led to overwhelming emails, and the teams could
not keep up with demand, which affected Radeon’s customers. As IT Manager for Radeon
Homes, I proposed migrating to Microsoft Office 365 (O365) as the replacement solution. Office
365 is a cloud-based solution billed per license, flexible enough to grow as the company grows.
This license structure can be added to include voice solutions and can be further tailored to
Radeon’s needs. An agile methodology was used during the deployment, breaking the project
into four phases: Planning, Execution, Monitoring, and Project Closure. The project was
communicated to key stakeholders via the project dashboard and ongoing communication with
KPI status updates. At the end of the project, the success was measured by employee surveys and
questionnaires along with ongoing customer feedback requests. The project was successfully
completed. All milestones were met, all costs were accounted for, and there was no need to dip
into the risk reserves. The project is complete, including all training the Microsoft consulting
team provides. All legacy infrastructure has been turned down, and all current collaboration is
maintained through the Microsoft Office 365 cloud management portal.
Keywords: Microsoft Office 365, O365, collaboration
, 3
Table of Contents
Abstract............................................................................................................................................2
Quality Assurance............................................................................................................................7
Formative Evaluation and QA Metrics............................................................................8
Testing Methodology.......................................................................................................9
Test Cases......................................................................................................................10
Acceptance Criteria........................................................................................................10
Project Review...............................................................................................................................11
Assumptions...................................................................................................................11
Project Phases................................................................................................................12
Timeline Deviations.......................................................................................................14
Project Dependencies.....................................................................................................15
Resource Requirements.................................................................................................16
Implementation Project Milestones...............................................................................18
Project Deliverables.......................................................................................................20
Documentation Deliverables..........................................................................................21
Formative Evaluation Results and Revisions................................................................................28
Summative Evaluation Plan and Results.......................................................................................28
Stakeholder Communication Plan and Reports.............................................................................29
Ongoing Support and Maintenance...............................................................................................30
, 4
Resources for Post-Implementation Support.................................................................31
Short and Long-Term Maintenance Plan.......................................................................31
Post-Implementation Project Summary.........................................................................................32
Documentation Deliverables..........................................................................................33
Success Criteria for Each Project Outcome...................................................................35
Justification of Proposed versus Actual Project Outcomes...........................................36
Lessons Learned.............................................................................................................36
The completion of this project learned two lessons. The first lesson is the importance
of building in extra time for unforeseen circumstances. While the Radeon team did much
preparatory work to ensure all areas of the project that could be controlled were accounted for,
Microsoft had a network outage that pushed the project by three days. Thankfully, the Radeon
and Microsoft consulting teams were able to make up the time elsewhere, but that may not
always be the case for future projects........................................................................................36
The second lesson learned was the benefit of having a contingency plan for not only
migratory purposes but also the risk reserve. Had the outage been extended, the team may
have had to revert to the legacy infrastructure, and depending on labor costs, they may have
had to dip into the risk reserve fund. Risk planning is critical for all future projects for the
company. There is only so much the team can control. All risks must be evaluated, and a
quantitative and qualitative risk analysis should be done to evaluate how it can affect the
progression of the project and ROI for the business..................................................................36
References......................................................................................................................................38
Tables.............................................................................................................................................41
