HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
 
(110 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<br>
+
<!--Navigation Bar start -->
[[Image:Teamphotowiki.jpg|centre|1150px ]]
+
[[Image:Boxus_Logo_PNG_Small.png|150px| centre | degree=90 ]]
 +
 
 +
{| style="background-color:#FFFFFF; color:#000000 padding: 0px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" align="center" border="0" font face="Calibri" |
  
 
<font face="Century Gothic" size="2">
 
<font face="Century Gothic" size="2">
  
{| style="background-color:#ffffff; color:#000000 padding:5px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |
+
| style="padding:0.6em;  font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; " width="10%"  | <font color="#632E00"><b>HOME</b><font>
| style="padding:2 em; font-size:90%;text-align:center; background-color:#B40404; " width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Home|<font color="#ffffff"><b>Home</b></font>]]
+
| style=" border-bottom:2px solid #632E00; background:none;" width="2%" | &nbsp;
 +
| style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; color:#000000" width="36%" |<font color="#632E00"><b>PROJECT OVERVIEW</b><font>
 +
| style="border-bottom:2px solid #632E00; background:none;" width="2%" | &nbsp;
 +
| style="border-bottom:2px solid #632E00; background:none;" width="2%" |&nbsp;
 +
| style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; color:#000000" width="36%" |<font color="#632E00"><b>PROJECT MANAGEMENT</b><font>
 +
| style="border-bottom:2px solid #632E00; background:none;" width="2%" | &nbsp;
 +
| style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00;  text-align:center; color:#000000" width="18%" |<font color="#632E00"><b>DOCUMENTATION</b><font>
 +
| style="border-bottom:2px solid #632E00; background:none;" width="2%" | &nbsp;
 +
 
 +
|}
  
| style="padding:2 em;  font-size:90%; text-align:center; background-color:#B40404; " width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Stakeholders|<font color="#ffffff"><b>Stakeholders</b></font>]]
+
{| style="background-color:#FFFFFF; color:#000000 padding: 2px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" align="center" border="0" font face="Calibri" |
  
| style="padding:2 em;  font-size:90%; text-align:center; background-color:#B40404; " width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Project_Overview|<font color="#ffffff"><b>Project Overview</b></font>]]
+
| style="padding:0 .6em;  font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; " width="10%" |  
 +
*[[IS480_Team_wiki:_2012T2_box.us | <font color="#385385" face="">'''Updates'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us | <font color="#385385" face="">'''Events''' </font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us | <font color="#385385" face="">'''Progress'''</font>]]
 +
| style="border-bottom:2px solid #806517;background:none;" width="2%" | &nbsp;
  
| style="padding:2 em; font-size:90%; text-align:center; background-color:#FFBF00;" width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Project_Management|<font color="#ffffff"><b>Project Management</b></font>]]
+
| style="padding:0.6em; font-size:100%; background-color:#ffffff;  border-bottom:2px solid #806517; text-align:left; color:#000000" width="18%" |
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Overview#Project_Description |<font color="#385385" face="">'''Project Description'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Process_Analysis |<font color="#385385" face="">'''Process Analysis'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Overview#System_Description |<font color="#385385" face="">'''System Description'''</font>]]
 +
| style="border-bottom:2px solid #806517; background:none;" width="2%" | &nbsp;
  
| style="padding:2 em; font-size:90%; text-align:center; background-color:#B40404; " width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Documentation|<font color="#ffffff"><b>Documentation</b></font>]]
+
| style="padding:0.6em; font-size:100%; background-color:#ffffff;  border-bottom:2px solid #806517;  text-align:left; color:#000000" width="18%" |
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Management#Team_Charter |<font color="#385385" face="">'''Team Charter '''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Overview#Project_Scope |<font color="#385385" face="">'''Project Scope'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Management#Schedule_.26_Milestones |<font color="#385385" face="">'''Schedule & Milestones'''</font>]]
 +
| style="border-bottom:2px solid #806517; background:none;" width="2%" |&nbsp;
  
| style="padding:2 em; font-size:90%; text-align:center; background-color:#B40404; " width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Learning_Outcomes|<font color="#ffffff"><b>Learning Outcomes</b></font>]]
+
| style="padding:0.6em; font-size:100%; background-color:#ffffff;  border-bottom:2px solid #806517; text-align:left; color:#000000" width="18%" |
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Management#Metrics |<font color="#385385" face="">'''Metrics'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Management#Risk_Management |<font color="#385385" face="">'''Risks'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Project_Management#Change_Management |<font color="#385385" face="">'''Change Management'''</font>]]
 +
| style="border-bottom:2px solid #806517; background:none;" width="2%" | &nbsp;
  
| style="padding:2 em; font-size:90%; text-align:center; background-color:#B40404; " width="10%" | [[IS480_Team_wiki:_2012T2_box.us_Useful Links|<font color="#ffffff"><b>Useful Links</b></font>]]
+
| style="padding:0.6em; font-size:100%; background-color:#ffffff;  border-bottom:2px solid #806517; text-align:left; color:#000000" width="12%" |
 +
*[[IS480_Team_wiki:_2012T2_box.us_Minutes |<font color="#385385" face="">'''Meeting Minutes'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Diagrams |<font color="#385385" face="">'''Diagrams'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_UI_&_Video |<font color="#385385" face="">'''UI & Videos'''</font>]]
 +
| style="border-bottom:2px solid #806517;background:none;" width="2%" | &nbsp;
 +
 
 +
| style="padding:0.6em; font-size:100%; background-color:#ffffff;  border-bottom:2px solid #806517; text-align:left; color:#000000" width="25%" |  
 +
*[[IS480_Team_wiki:_2012T2_box.us_Test_Plans |<font color="#385385" face="">'''Testing'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Useful_Links |<font color="#385385" face="">'''Resources'''</font>]]
 +
*[[IS480_Team_wiki:_2012T2_box.us_Learning_Outcomes |<font color="#385385" face="">'''Learning Outcomes'''</font>]]
 
|}
 
|}
 +
  
 
{| style="text-align: center; width: 100%;"
 
{| style="text-align: center; width: 100%;"
Line 24: Line 61:
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Team Charter''' </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"> '''Team Charter''' </span></div></p>=
  
 +
<div>
 +
[[Image:kevin.jpg|550px]]
 +
[[Image:sherrie.jpg|550px]]
 +
[[Image:Boonkheng.jpg|550px]]
 +
[[Image:Jenzus.jpg|550px]]
 +
[[Image:Waimun.jpg|550px]]
 +
[[Image:Jervenne.jpg|550px]]
 +
</div>
  
Team Box.us is a project team that consists of 6 individuals with varying (and complementing skillsets). The team set out with the following beliefs to achieve at the end of the project:
+
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Schedule & Milestones'''  </span></div></p>=
  
* Create value for organizations - Value could be business value and also social value to our sponsors.
 
* Sustainable implementations - Our team believes in having projects that would be sustainable and be able to bring value to the organizations in a long run
 
* Team Learning - Our team believes in learning during the entire development process so that the experience would be enriching for the organization, the team and the individuals invovled.
 
  
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Work Breakdown''' </span></div></p>=
+
'''Project Milestones'''  
'''CONCEPTUALIZATION (07/10/2012 - 27/10/2012)'''
+
* [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=24 Project Milestones List]
  
[[Image:Conceptualization.jpg‎]]
+
'''Project Gantt Chart(For Empact)'''
 +
* [https://wiki.smu.edu.sg/is480/Image:Boxus_Gantt_Chart_4.xlsx Project Gantt Chart V4.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Boxus_Gantt_Chart_3.xlsx Project Gantt Chart V3.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Gantt_Chart_2.xlsx Project Gantt Chart V2.0]
 +
* [https://wiki.smu.edu.sg/is480/Image:Boxus_Gantt_Chart_1.xlsx Project Gantt Chart V1.0]  
  
  
'''DEVELOPMENT (28/10/2012 - 17/02/2013)'''
+
'''Project Schedule'''
 +
* [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_Version3.xlsx Project Schedule Version 3]
 +
* [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]
  
[[Image:Development.jpg]]
 
  
 +
'''Iteration Reports'''
 +
<br/>The iteration reports covers the bug ratios and schedule ratios for each iteration.
 +
* Iteration 0 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=26 Iteration Report]
 +
* Iteration 1 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=30 Iteration Report]
 +
* Iteration 2 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=31 Iteration Report]
 +
* Iteration 3 Schedule Ratio(Acceptance): [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=32 Iteration Report @ Acceptance]
 +
* Iteration 4 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=34 Iteration Report]
 +
* Iteration 5 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=35 Iteration Report]
 +
* Iteration 6 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=36 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 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]
  
'''DEPLOYMENT (18/02/2013 - 31/03/2013)'''
+
=<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>=
  
[[Image:Deployment_Process_Boxus.jpg‎]]
+
===Overall Project Metrics:===
  
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Schedule & Milestones'''  </span></div></p>=
+
====<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
 +
|-
 +
|}
  
[[Image:Milestones_v2.png | thumb | center | 1000px | Our Project Milestone ]]
+
====Overall Schedule Metrics====
 +
* Schedule: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVRWVhPUGN5N0pwYmIwSndOWmIzQUE#gid=16 Schedule on Google Docs]
 +
[[Image:Boxus_Schedulemetricsfinals.png | 500px]]
  
'''Project Milestones''' - Detailed Project Milestones with their dates can be found at: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=24 Project Milestones List]
 
  
'''Project Schedule''' - [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=16 Project Schedule on Google Docs]
+
=='''SCHEDULE METRICS'''==
  
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Schedule Metrics'''  </span></div></p>=
 
  
 
'''OBJECTIVE'''
 
'''OBJECTIVE'''
Line 65: Line 164:
 
! scope="row"  width="800" style="align: middle; text-align: center; background: #FFF8C6"|CALCULATION:
 
! scope="row"  width="800" style="align: middle; text-align: center; background: #FFF8C6"|CALCULATION:
 
Schedule Ratio  
 
Schedule Ratio  
= Actual Time / Planned Time
+
= Actual Duration / Planned Duration
 
|}
 
|}
 
</center>
 
</center>
Line 77: Line 176:
 
|-
 
|-
  
! scope="row" style="background: #A8E16B" |'''> 0.8'''
+
! scope="row" style="background: #A8E16B" |'''< 0.8'''
 
|style="text-align: center;"|Team is ahead of schedule
 
|style="text-align: center;"|Team is ahead of schedule
 
|style="text-align: left;"|Proceed to embark on the next task if possible
 
|style="text-align: left;"|Proceed to embark on the next task if possible
Line 84: Line 183:
 
! scope="row" style="background: #FF9734"|'''0.8 - 1.2'''
 
! scope="row" style="background: #FF9734"|'''0.8 - 1.2'''
 
|style="text-align: center;"|Within healthy schedule range
 
|style="text-align: center;"|Within healthy schedule range
|style="text-align: left;"|No actions required for ratio above 1. <br>Keep close monitor on tasks that have a ratio of less than one.
+
|style="text-align: left;"|No actions required for ratio below 1. <br>Keep close monitor on tasks that have a ratio of more than one. <br> Project Manager to review schedule to see which tasks have gone over time. If necessary, review time estimations for tasks in the next iteration.
 
|-
 
|-
  
! scope="row" style="background: #EE5429"|'''< 1.2'''
+
! scope="row" style="background: #EE5429"|'''> 1.2'''
 
|style="text-align: center;"|Team is behind schedule
 
|style="text-align: center;"|Team is behind schedule
|style="text-align: left;"|Team is behind schedule. Project Manager identifies root cause and allocate more time to complete tasks in the next iteration.
+
|style="text-align: left;"|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.
 
|}
 
|}
 
<br>
 
<br>
 +
Schedule Metrics are captured within the Iteration Reports. Look above for the Iteration Reports.
  
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Bug Metric''' </span></div></p>=
+
=='''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 106: Line 205:
 
! scope="row"  width="600" style="text-align: center; background: #FFF8C6"|CALCULATION:
 
! scope="row"  width="600" style="text-align: center; background: #FFF8C6"|CALCULATION:
 
Bug Score
 
Bug Score
= (2 X Total No. of Low Severity) + (4 X Total No. of Medium Severity Bug) + (8 X Total No. of High Severity Bug)
+
= (1 X Total No. of Low Severity) + (2 X Total No. of Medium Severity Bug) + (10 X Total No. of High Severity Bug)
 
|}
 
|}
  
Line 118: Line 217:
 
|-
 
|-
  
! scope="row" |'''2'''
+
! scope="row" |'''1'''
 
|style="text-align: center;"|'''LOW'''
 
|style="text-align: center;"|'''LOW'''
|style="text-align: left;"|Errors that lies with user interface. Features can still work, but not as what is expected.
+
|style="text-align: left;"|System is able to function as per normal. Minor issues in expected output or user interface alignment
 
|-
 
|-
  
! scope="row" |'''4'''
+
! scope="row" |'''2'''
 
|style="text-align: center;"|'''MEDIUM'''
 
|style="text-align: center;"|'''MEDIUM'''
|style="text-align: left;"|Errors that prevent an entire feature from working
+
|style="text-align: left;"|System is able to function but with runtime errors. Some non-critical functionalities may not work as expected
 
|-
 
|-
  
 
! scope="row" |'''10'''
 
! scope="row" |'''10'''
 
|style="text-align: center;"|'''HIGH'''
 
|style="text-align: center;"|'''HIGH'''
|style="text-align: left;"|Errors that prevent more than 1 feature from working
+
|style="text-align: left;"|System has some compilation error and unable to run or unusable for a period of time. Core functionalities may be affected
 
|}
 
|}
  
Line 155: Line 254:
 
</center>
 
</center>
  
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Iteration Planning''' </span></div></p>=
+
'''Bug Log'''
 
+
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdFh6eXB3VmtpYmljVGN2Y19oajdtRWc#gid=0 Bug Log on Google Docs]
'''Sponsor Sourcing'''
 
 
 
Before everything, we have to find a sponsor. Learning from our past experiences, the team has developed a guideline for sourcing the sponsor. The guidelines are as such:
 
 
 
* The Motivation: What is the need?
 
* The Idea: In short, what is the idea about?
 
* The Solution: How would the idea help to solve the need
 
* The Scope: What is the focus of the project? The differentiating factor? The X-Factor of the project?
 
* The Implementation: Do we have the technical ability to deal with the project?
 
 
 
At the end of this iteration, the team would have a clear idea of what the scope of the project is about and the high-level steps of what needs to be done to get there.
 
 
 
 
 
'''Agile Development'''
 
  
It's all about agility. Our team aims to mimic as close as possible to real-world software engineering experiences. As such, our team has decided to adopt the Agile Development Process that is flexible and meaningful for the entire team. In our Development phase, we iterate between design, build, test and release for each iteration.
+
'''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 179: Line 265:
  
 
'''TYPES OF CHANGE'''
 
'''TYPES OF CHANGE'''
 +
  
 
'''Requirement Change'''
 
'''Requirement Change'''
Line 188: Line 275:
 
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.
 
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.
  
'''Team Process Change'''
+
'''Business Process Change'''
  
Team Process changes are modifications, additions, deletions to the existing team processes as stated in the latest versions of project management plan and software configuration management plan. In this case, supervisor. Supervisor would be informed.
+
Business Process changes are modifications, additions, deletions to the existing business processes as stated in the latest versions of process analysis documentation.  
  
  
Line 201: Line 288:
 
#Project Manager informs team supervisor and sponsor(only if necessary)
 
#Project Manager informs team supervisor and sponsor(only if necessary)
 
#If team meeting is needed, meeting is scheduled, else team would be informed of change once decision made
 
#If team meeting is needed, meeting is scheduled, else team would be informed of change once decision made
 +
#Change would be analyzed and decision reached by team to make it known.
 
#Change decision is being made known to supervisor
 
#Change decision is being made known to supervisor
 
#Change implemented and decision is made known to team, supervisor and sponsor(if necessary)
 
#Change implemented and decision is made known to team, supervisor and sponsor(if necessary)
  
  
'''DOCUMENTING CHANGE'''
+
== 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 or Business Analyst. Followup actions of changes made to project and team would be tracked by the Deputy Project Manager.
+
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:
 +
* [https://docs.google.com/spreadsheet/ccc?key=0AuLeuwqZi7r9dGtXSFdJVVhFbUx3TEpmSzlQRzZjdEE#gid=0 Change Log(Google Docs)]
 +
 
 +
<br/>
 +
 
 +
== 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:
 +
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdE5FSkFZTkVULWIyMm5pUnJWX0drUnc#gid=0 Issue Log (Google Docs)]
 +
 
 +
 
 +
<br/>
 +
 
 +
== Resources ==
 +
*[https://wiki.smu.edu.sg/is480/Image:Change_Management_Principles.pptx Change Management Briefing Slides]
 +
*[https://wiki.smu.edu.sg/is480/Image:Confirmation_Template.xlsx Change Management Confirmation Template]
 +
*[https://docs.google.com/spreadsheet/ccc?key=0AuLeuwqZi7r9dGtXSFdJVVhFbUx3TEpmSzlQRzZjdEE#gid=0 Change Management Form (Team Use Only)]
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Risk 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"> '''Risk Management'''  </span></div></p>=
Line 215: Line 325:
 
<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"
 
|+  
 
|+  
 
|-
 
|-
! scope="col"  width="10"| No
+
! scope="col"  width="10"| Priority
 
! scope="col" width="50" | Type
 
! scope="col" width="50" | Type
 
! scope="col" width="100" | Risk
 
! scope="col" width="100" | Risk
Line 231: 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;"|
*Lay down milestones, deadlines and tasks to do with team before the start of every iteration and review estimates together as a team
+
# Change Management process to help evaluate whether the change is necessary
*Project Maanger to actively manage the overrun of schedule through tracking of metrics
 
 
|-
 
|-
  
 
! 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>
  
! scope="row" style=" " |'''4'''
+
<br/>
|style="text-align: center;"|
+
 
Project
+
==Risk Management Plan Resources==
|style="text-align: center;"|
+
Check our our Risk Management Plans for more information:
Change in volunteer matching business process during the development of the system
+
* [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHVVRkhza3VvSEVsd2ZIMG51ekV3eUE#gid=0 Risk Management(Google Docs)]
|style="text-align: center;"|
+
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v1.xlsx Risk Management Plan v1.0]
Decrease in value of system brought to the business.
+
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v2.xlsx Risk Management Plan v2.0]
|style="text-align: center;"|
+
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v3.xlsx Risk Management Plan v3.0]
Possible
+
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v4.xlsx Risk Management Plan v4.0]
|style="text-align: center;"|
+
* [https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risks_v5.xlsx Risk Management Plan v5.0]
Major
+
*[https://wiki.smu.edu.sg/is480/Image:Empact_FYP_Risk_v6.xlsx Risk Management Plan v6.0]
|style="text-align: center;"|
+
 
High
+
=<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>=
|style="text-align: center;"|
+
 
*Analyse client's As-Is Process and verify with client about current As-Is Model
+
'''DESCRIPTION'''
*Consider longevity of the system during the design of system
+
 
|-
+
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
  
! scope="row" style=" " |'''5'''
 
|style="text-align: center;"|
 
Resources
 
|style="text-align: center;"|
 
Multiple users working on the same files resulting in conflicting versions of documentation
 
|style="text-align: center;"|
 
Loss of information or mismatch in understanding
 
|style="text-align: center;"|
 
Likely
 
|style="text-align: center;"|
 
Minor
 
|style="text-align: center;"|
 
Minor
 
|style="text-align: center;"|
 
*Segregating editing responsibilities - Business Team to edit business related documents while Technical Team to edit technical-related documents
 
*Use of Subversion during the committing of code. Lead Developer would be responsible for any code conflicts.
 
|-
 
  
! scope="row" style=" " |'''6'''
+
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:
|style="text-align: center;"|
 
Resources
 
|style="text-align: center;"|
 
Hardware and software failure during the development of the project.
 
|style="text-align: center;"|
 
*Failure of hardware would cause latest work that is being developed to be lost.
 
*Redundancy and repetition of work is necessary in order to keep up to the pace that is being set by the schedule in the event of a software and hardware failure.
 
|style="text-align: center;"|
 
Unlikely
 
|style="text-align: center;"|
 
Moderate
 
|style="text-align: center;"|
 
Moderate
 
|style="text-align: center;"|
 
* Save development codes onto Subversion
 
* Business Analyst to do a weekly backup of all documents and source code.
 
|-
 
  
! scope="row" style=" " |'''7'''
+
* Did not affect the current schedule much
|style="text-align: center;"|
+
* Had previously done research on the list of possible hosts for Empact
Team
+
* Gives the team greater control over the development environment
|style="text-align: center;"|
+
* Ensures Empact's business continuity
Different workloads and committment in team due to varying workloads and outside commitments
 
|style="text-align: center;"|
 
Inaccurate allocation and expectation of team and project manager upon each team member, obstructing accurate time estimation and affects schedule allocation.
 
Unhappiness in team due to unfair work allocations throughout the entire project
 
|style="text-align: center;"|
 
Likely
 
|style="text-align: center;"|
 
Major
 
|style="text-align: center;"|
 
High
 
|style="text-align: center;"|
 
* Set expectations instead of micro-managing how work would be done by individuals
 
* Schedule shorter iterations to ensure that targets are met and not piled up.
 
* Allocate common coding sessions to allow team to ensure accountability and transparency
 
|-
 
  
! scope="row" style=" " |'''8'''
 
|style="text-align: center;"|
 
Business
 
|style="text-align: center;"|
 
Misunderstanding of technical requirements between client and project team as clients are not technically-inclined
 
|style="text-align: center;"|
 
Re-doing of development work as a result of mismatched expectations between different parties, leading to time wastage
 
|style="text-align: center;"|
 
Likely
 
|style="text-align: center;"|
 
Severe
 
|style="text-align: center;"|
 
High
 
|style="text-align: center;"|
 
* Conduct requirements clarifications before the start of every iteration between team and client to clarify the requirements
 
* Using process flow diagrams and storyboards to communicate features with client and team.
 
* Discuss about feature design before each development session
 
* Recommend and propose technical requirements to client
 
|-
 
  
|}
+
'''Resources for Server Migration'''
</center>
+
* [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