HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 box.us Project Management"

From IS480
Jump to navigation Jump to search
 
(41 intermediate revisions by 3 users not shown)
Line 62: Line 62:
  
 
<div>
 
<div>
[[Image:Stakeholders1.jpg|550px]]
+
[[Image:kevin.jpg|550px]]
[[Image:LDQAV3.jpg|500px]]
+
[[Image:sherrie.jpg|550px]]
[[Image:BA.jpg|450px]]
+
[[Image:Boonkheng.jpg|550px]]
[[Image:UA.jpg|500px]]
+
[[Image:Jenzus.jpg|550px]]
 +
[[Image:Waimun.jpg|550px]]
 +
[[Image:Jervenne.jpg|550px]]
 
</div>
 
</div>
  
Line 82: Line 84:
  
 
'''Project Schedule'''  
 
'''Project Schedule'''  
* [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=16 Project Schedule on Google Docs]
+
* [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=16 Project Schedule on Google Docs]
 +
* [https://wiki.smu.edu.sg/is480/Image:Schedule_%28Box.us%29_%40_Mid_Terms_v5.xlsx Project Schedule Version 4.0]
 
* [https://wiki.smu.edu.sg/is480/Image:Box.Us_Schedule_v31.xlsx Project Schedule Version 3.1]
 
* [https://wiki.smu.edu.sg/is480/Image:Box.Us_Schedule_v31.xlsx Project Schedule Version 3.1]
 
* [https://wiki.smu.edu.sg/is480/Image:Box.Us_Schedule_Version3.xlsx Project Schedule Version 3]
 
* [https://wiki.smu.edu.sg/is480/Image:Box.Us_Schedule_Version3.xlsx Project Schedule Version 3]
* [https://wiki.smu.edu.sg/is480/Image:Project_Schedule_v2.xlsx Project Schedule Version 2]
+
* [https://wiki.smu.edu.sg/is480/Image:Schedule_%28Box.us%29_%281%29.xlsx Project Schedule Version 2 @ Acceptance]
 
* [https://wiki.smu.edu.sg/is480/Image:Boxus_Schedule_v1.xlsx Project Schedule Version 1]
 
* [https://wiki.smu.edu.sg/is480/Image:Boxus_Schedule_v1.xlsx Project Schedule Version 1]
  
Line 100: Line 103:
 
* Iteration 7 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=37 Iteration Report]
 
* Iteration 7 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=37 Iteration Report]
 
* Iteration 8 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=38 Iteration Report]
 
* Iteration 8 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=38 Iteration Report]
 +
* Iteration 9 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=51 Iteration Report]
 +
* Iteration 10 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=53 Iteration Report]
 +
* Iteration 11 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=54 Iteration Report]
 +
* Iteration 12 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=55 Iteration Report]
 +
* Iteration 13 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=56 Iteration Report]
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Metrics'''  </span></div></p>=
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Metrics'''  </span></div></p>=
  
'''SCHEDULE METRICS'''
+
===Overall Project Metrics:===
 +
 
 +
====<b>Overall Bug Metrics</b><br/>====
 +
[[Image:Boxus_BugMetricsFinals.png | 500px ]]
 +
{| class="wikitable" style="width:800;text-align:left"
 +
|+
 +
|-
 +
! scope="col"  width="10" style="background:#810541;color:#ffffff"| Iteration
 +
! scope="col"  width="20" style="background:#810541;color:#ffffff"| Bug Score
 +
! scope="col" width="300" style="background:#810541;color:#ffffff"| Any Actions Taken
 +
|-
 +
! scope="row" style="text-align:center;" | 11
 +
! scope="row" style="text-align:center;" | 28
 +
! scope="row" style="background-color:white" |
 +
Increase in Bug Score due to bugs that were recorded from User Testing 2
 +
* 2 days allocated to fix bugs from User Testing 2
 +
|-
 +
! scope="row" style="text-align:center;" | 12
 +
! scope="row" style="text-align:center;" | 11
 +
! scope="row" style="background-color:white" |
 +
New features of the system(Statistics, Dashboard and Notifications) were being released
 +
* Allow Empact to have a full picture of the entire system for testing
 +
* Resulted in an overall increase in bugs being reported
 +
* Scheduled additional time during bug fixing to fix up bugs within the system
 +
* All bugs were fixed by the end of the iteration
 +
|-
 +
! scope="row" style="text-align:center;" | 13
 +
! scope="row" style="text-align:center;" | 32
 +
! scope="row" style="background-color:white" |
 +
More thorough testing was being performed for the UAT
 +
* Resulted in an overall increase in bugs being reported
 +
* Scheduled additional time during bug fixing to fix up bugs within the system
 +
* All bugs were fixed by the end of the iteration
 +
|-
 +
|}
 +
 
 +
====Overall Schedule Metrics====
 +
* Schedule: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=16 Schedule on Google Docs]
 +
[[Image:Boxus_Schedulemetricsfinals.png | 500px]]
 +
 
 +
 
 +
=='''SCHEDULE METRICS'''==
  
  
Line 142: Line 191:
 
|}
 
|}
 
<br>
 
<br>
 +
Schedule Metrics are captured within the Iteration Reports. Look above for the Iteration Reports.
  
 
+
=='''BUG METRICS'''==
 
 
'''BUG METRICS'''
 
 
<p>'''OBJECTIVE'''
 
<p>'''OBJECTIVE'''
 
* To minimize the number of bugs that surface during the duration of a sprint and thus ensuring the quality of the application.
 
* To minimize the number of bugs that surface during the duration of a sprint and thus ensuring the quality of the application.
Line 205: Line 253:
 
|}
 
|}
 
</center>
 
</center>
 +
 +
'''Bug Log'''
 +
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdFh6eXB3VmtpYmljVGN2Y19oajdtRWc#gid=0 Bug Log on Google Docs]
 +
 +
'''Resources for Bug Metrics'''
 +
*[http://en.wikipedia.org/wiki/Software_bug Types of Software Bugs]
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Change Management'''  </span></div></p>=
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Change Management'''  </span></div></p>=
Line 211: Line 265:
  
 
'''TYPES OF CHANGE'''
 
'''TYPES OF CHANGE'''
 +
  
 
'''Requirement Change'''
 
'''Requirement Change'''
Line 244: Line 299:
  
 
Check out our Change Log:
 
Check out our Change Log:
* [https://wiki.smu.edu.sg/is480/Image:Change_Log_v1.0.xlsx Change Log v1.0]
+
* [https://docs.google.com/spreadsheet/ccc?key=0AuLeuwqZi7r9dGtXSFdJVVhFbUx3TEpmSzlQRzZjdEE#gid=0 Change Log(Google Docs)]
 
 
Check out how the Change Log was used:
 
* [https://wiki.smu.edu.sg/is480/Image:Change003.xlsx Change ID 003]
 
* [https://wiki.smu.edu.sg/is480/Image:Change005.xlsx Change ID 005]
 
  
 +
<br/>
  
 
== Issues ==
 
== Issues ==
Line 258: Line 310:
 
Check out our Issue Log:  
 
Check out our Issue Log:  
 
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdE5FSkFZTkVULWIyMm5pUnJWX0drUnc#gid=0 Issue Log (Google Docs)]
 
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdE5FSkFZTkVULWIyMm5pUnJWX0drUnc#gid=0 Issue Log (Google Docs)]
*[https://docs.google.com/spreadsheet/ccc?key=0AuLeuwqZi7r9dE9ZSHhzLVZEWXRfbm1kMnVLUXFyaVE#gid=0 Development Issue Log (Google Docs)]
 
  
 +
 +
<br/>
  
 
== Resources ==
 
== Resources ==
Line 269: Line 322:
  
 
Our team's risk management approach is in constant monitoring and reviewing risk at the start and end of each milestone.
 
Our team's risk management approach is in constant monitoring and reviewing risk at the start and end of each milestone.
Check our our Risk Management Plans for more information:
 
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v1.xlsx Risk Management Plan v1.0]
 
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v2.xlsx Risk Management Plan v2.0]
 
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v3.xlsx Risk Management Plan v3.0]
 
  
 
<center>[[Image:risk_matrix.gif]]</center>
 
<center>[[Image:risk_matrix.gif]]</center>
  
 +
== Our Top 3 Risks==
 
<center>
 
<center>
 
{| class="wikitable sortable" style="text-align: center; width:500"
 
{| class="wikitable sortable" style="text-align: center; width:500"
Line 292: Line 342:
 
! scope="row" style=" " |'''1'''
 
! scope="row" style=" " |'''1'''
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Business
+
Team
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Unfamiliarity with mobile development frameworks required for the project
+
Underestimation of time taken to complete a module
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
* Inability to make decision about best framework to use
+
# Delay in project schedule
* Slow project progress because of unfamiliarity
 
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
 
Likely
 
Likely
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Major
+
Moderate
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
 
High
 
High
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
* Conduct research on possible mobile development technologies and consult peers and supervisors for advice on which framework to use, in view of mobile app's scope
+
# Buffer at the end of every iteration
* Development of mobile application in parallel with web application to highlight any possible loopholes and to buffer for any major changes needed early.
+
# More buffer towards the end to act as contingency buffer in between iterations
 
|-
 
|-
  
 
! scope="row" style=" " |'''2'''
 
! scope="row" style=" " |'''2'''
 
|style="text-align: center;"|
 
|style="text-align: center;"|
Team
+
Project
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Group members making assumptions of technical scope required within the project
+
Higher than expected number of issues raised during testing(s)
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Inaccurate estimates of time required to complete tasks that leads to unreliable project deadlines and milestones
+
# Delay in project schedule
 +
# Changes may affect the system or scope"
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
 
Possible
 
Possible
 
|style="text-align: center;"|
 
|style="text-align: center;"|
Moderate  
+
Moderate
 
|style="text-align: center;"|
 
|style="text-align: center;"|
High
+
Medium
 
|style="text-align: center;"|
 
|style="text-align: center;"|
*Review Project Scope at the start of every iteration by the team
+
# Change Management process to help evaluate whether the change is necessary
*Paper Prototype is being done to ensure common understanding
 
*Encourage Members to Check their understanding of the scope.
 
 
|-
 
|-
  
 
! scope="row" style=" " |'''3'''
 
! scope="row" style=" " |'''3'''
 
|style="text-align: center;"|
 
|style="text-align: center;"|
Business
+
Project
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Difference in understanding of terminologies and terms used in describing the business process (e.g. task, questions, assignments)
+
Business process of client is not clearly defined, leading to constant changes in the business process and design of the system
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
Confusion over terms that may lead to the wrong picture being conveyed between client and team
+
# Re-doing of system design that leads to unnecessary work
 +
#Delay in Schedule
 
|style="text-align: center;"|
 
|style="text-align: center;"|
Possible
+
Likely
 
|style="text-align: center;"|
 
|style="text-align: center;"|
Minor
+
Major
 
|style="text-align: center;"|
 
|style="text-align: center;"|
Medium
+
Extreme
 
|style="text-align: center;"|  
 
|style="text-align: center;"|  
* Implement a project dictionary where common terms of use are being recorded down
+
# Client meeting at the start of iteration to be adopted and it would be able to include the review for the next iteration
* Proactive logging down of common terms of use in the project dictionary
+
# Require client to do up the business process diagram in order to allow client to think through the entire process.
 +
# Prototyping process to let the client have a better idea of the end-product and what are the fields that would be necessary to capture within the system
 +
|-
 
|}
 
|}
 
</center>
 
</center>
 +
 +
<br/>
 +
 +
==Risk Management Plan Resources==
 +
Check our our Risk Management Plans for more information:
 +
* [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHVVRkhza3VvSEVsd2ZIMG51ekV3eUE#gid=0 Risk Management(Google Docs)]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v1.xlsx Risk Management Plan v1.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v2.xlsx Risk Management Plan v2.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v3.xlsx Risk Management Plan v3.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v4.xlsx Risk Management Plan v4.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v5.xlsx Risk Management Plan v5.0]
 +
*[https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risk_v6.xlsx Risk Management Plan v6.0]
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Deployment'''  </span></div></p>=
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Deployment'''  </span></div></p>=
Line 352: Line 415:
  
 
Team Box.us would be responsible for the deployment of the system onto the client's servers and to ensure that the application is able to function smoothly and integrate into their current workflow processes.
 
Team Box.us would be responsible for the deployment of the system onto the client's servers and to ensure that the application is able to function smoothly and integrate into their current workflow processes.
 +
 +
<p>
 +
[[Image:Deployment_Plan_Slide1_Boxus.jpg | 500px]]
 +
</p>
 +
 +
 +
 +
 +
== Server Migration ==
 +
Date: 08/02/2012
 +
 +
 +
Box.us was tasked to do an urgent migration for Empact because their servers were going to expire. After considering our scope, we decided that it would be possible to continue on with doing the migration for Empact. Our team decided to move forward with the server migration for the following reasons:
 +
 +
* Did not affect the current schedule much
 +
* Had previously done research on the list of possible hosts for Empact
 +
* Gives the team greater control over the development environment
 +
* Ensures Empact's business continuity
 +
 +
 +
'''Resources for Server Migration'''
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_Migration_Static_Page_Schedule_Final.xlsx Scheduled Dates for Server Migration]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_Documentation_FTP.docx Instructions for using FTP in EATJ Server]
 +
* [https://wiki.smu.edu.sg/is480/Image:Empact_DNS_configuration.docx Technical Specifications for Empact Website]
 +
* [https://wiki.smu.edu.sg/is480/Image:Signup_Instructions.docx Signup Instructions for Empact]

Latest revision as of 13:55, 22 April 2013

degree=90
HOME   PROJECT OVERVIEW     PROJECT MANAGEMENT   DOCUMENTATION  
         


Kevin.jpg Sherrie.jpg Boonkheng.jpg Jenzus.jpg Waimun.jpg Jervenne.jpg

Project Milestones

Project Gantt Chart(For Empact)


Project Schedule


Iteration Reports
The iteration reports covers the bug ratios and schedule ratios for each iteration.

Overall Project Metrics:

Overall Bug Metrics

Boxus BugMetricsFinals.png

Iteration Bug Score Any Actions Taken
11 28

Increase in Bug Score due to bugs that were recorded from User Testing 2

  • 2 days allocated to fix bugs from User Testing 2
12 11

New features of the system(Statistics, Dashboard and Notifications) were being released

  • Allow Empact to have a full picture of the entire system for testing
  • Resulted in an overall increase in bugs being reported
  • Scheduled additional time during bug fixing to fix up bugs within the system
  • All bugs were fixed by the end of the iteration
13 32

More thorough testing was being performed for the UAT

  • Resulted in an overall increase in bugs being reported
  • Scheduled additional time during bug fixing to fix up bugs within the system
  • All bugs were fixed by the end of the iteration

Overall Schedule Metrics

Boxus Schedulemetricsfinals.png


SCHEDULE METRICS

OBJECTIVE

  • To ensure that all project tasks are completed on time and milestones are met.
CALCULATION:

Schedule Ratio = Actual Duration / Planned Duration

Schedule Ratio Description Response
< 0.8 Team is ahead of schedule Proceed to embark on the next task if possible
0.8 - 1.2 Within healthy schedule range No actions required for ratio below 1.
Keep close monitor on tasks that have a ratio of more than one.
Project Manager to review schedule to see which tasks have gone over time. If necessary, review time estimations for tasks in the next iteration.
> 1.2 Team is behind schedule Team is behind schedule. Project Manager identifies root cause of the delay. Project Manager would increase the velocity of the team in the upcoming iteration to complete the tasks on time.


Schedule Metrics are captured within the Iteration Reports. Look above for the Iteration Reports.

BUG METRICS

OBJECTIVE

  • To minimize the number of bugs that surface during the duration of a sprint and thus ensuring the quality of the application.
  • A bug is defined as errors in code that causes system to behave differently from expected.


CALCULATION:

Bug Score = (1 X Total No. of Low Severity) + (2 X Total No. of Medium Severity Bug) + (10 X Total No. of High Severity Bug)


Severity Score Severity Level Description
1 LOW System is able to function as per normal. Minor issues in expected output or user interface alignment
2 MEDIUM System is able to function but with runtime errors. Some non-critical functionalities may not work as expected
10 HIGH System has some compilation error and unable to run or unusable for a period of time. Core functionalities may be affected
Bug Score Action Plan
6 and below Developers resolve issues within the iteration
7 - 9 Schedule debugging in the buffer of the iteration.
10 and above Priority goes to resolving bug. Project Manager reallocates task for debugging team to focus on debugging.

Bug Log

Resources for Bug Metrics

There are few sources of change for the project itself. Depending on the initiator of the project change, change control processes would have to be taken into consideration.

TYPES OF CHANGE


Requirement Change

Requirement changes are modifications, additions, deletions of requirements stated in the latest version of requirements documentation. In this case, sponsor and supervisor would be noted. Response from supervisor and sponsor would be sought before decision is sealed.

System Design Change

System changes are modification, additions, deletions to the system architecture and detail system design as stated in the latest versions of system architectural documentations and technical infrastructure documentations. Depending on severity, response from supervisor might be sought before decision is sealed.

Business Process Change

Business Process changes are modifications, additions, deletions to the existing business processes as stated in the latest versions of process analysis documentation.


CHANGE PROCESS

Following the feedback given by our supervisor, we have come up with the revised change process:

  1. Change initiated by external party
  2. Project Manager informed of change
  3. Project Manager makes decision of change and decides if team meeting is needed
  4. Project Manager informs team supervisor and sponsor(only if necessary)
  5. If team meeting is needed, meeting is scheduled, else team would be informed of change once decision made
  6. Change would be analyzed and decision reached by team to make it known.
  7. Change decision is being made known to supervisor
  8. Change implemented and decision is made known to team, supervisor and sponsor(if necessary)


Major Changes

DOCUMENTING BIG CHANGES

Changes that are formalized and agreed upon by team, and stakeholders if necessary, would be recorded in the respective documentation by Project Manager/Deputy Project Manager. Followup actions of changes made to project and team would be tracked by the Deputy Project Manager.

Check out our Change Log:


Issues

DOCUMENTING ISSUES RAISED

Issues consists of items that are small changes that do not significantly impact the project schedule or project scope. Our team adopts an issue list in order to keep track of outstanding issues.

Check out our Issue Log:



Resources

Our team's risk management approach is in constant monitoring and reviewing risk at the start and end of each milestone.

Risk matrix.gif

Our Top 3 Risks

Priority Type Risk Consequence Likelihood Impact Level Risk Assessment Level Mitigation Strategy
1

Team

Underestimation of time taken to complete a module

  1. Delay in project schedule

Likely

Moderate

High

  1. Buffer at the end of every iteration
  2. More buffer towards the end to act as contingency buffer in between iterations
2

Project

Higher than expected number of issues raised during testing(s)

  1. Delay in project schedule
  2. Changes may affect the system or scope"

Possible

Moderate

Medium

  1. Change Management process to help evaluate whether the change is necessary
3

Project

Business process of client is not clearly defined, leading to constant changes in the business process and design of the system

  1. Re-doing of system design that leads to unnecessary work
  2. Delay in Schedule

Likely

Major

Extreme

  1. Client meeting at the start of iteration to be adopted and it would be able to include the review for the next iteration
  2. Require client to do up the business process diagram in order to allow client to think through the entire process.
  3. Prototyping process to let the client have a better idea of the end-product and what are the fields that would be necessary to capture within the system


Risk Management Plan Resources

Check our our Risk Management Plans for more information:

DESCRIPTION

Team Box.us would be responsible for the deployment of the system onto the client's servers and to ensure that the application is able to function smoothly and integrate into their current workflow processes.

Deployment Plan Slide1 Boxus.jpg



Server Migration

Date: 08/02/2012


Box.us was tasked to do an urgent migration for Empact because their servers were going to expire. After considering our scope, we decided that it would be possible to continue on with doing the migration for Empact. Our team decided to move forward with the server migration for the following reasons:

  • Did not affect the current schedule much
  • Had previously done research on the list of possible hosts for Empact
  • Gives the team greater control over the development environment
  • Ensures Empact's business continuity


Resources for Server Migration