HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 STEEP PROJECT MANAGEMENT"

From IS480
Jump to navigation Jump to search
 
(16 intermediate revisions by the same user not shown)
Line 26: Line 26:
 
==<div style="border-left: #5ee5ec solid 10px; padding: 0px;"><div style="background: #FAF8CC; font-family:Tahoma; line-height: 0.4em; border-left: #000000 solid 10px;"><div style="border-left: White solid 10px; padding: 10px; text-indent: 20px;"><font color= #000000><b>Schedule</b></font></div></div></div>==
 
==<div style="border-left: #5ee5ec solid 10px; padding: 0px;"><div style="background: #FAF8CC; font-family:Tahoma; line-height: 0.4em; border-left: #000000 solid 10px;"><div style="border-left: White solid 10px; padding: 10px; text-indent: 20px;"><font color= #000000><b>Schedule</b></font></div></div></div>==
  
[[Media:STEEPSchedule_v5.pdf‎ ‎‎|View our planned Schedule]]<br/>
+
[[Media:STEEPSchedule_v5.pdf‎ ‎‎|View our Schedule]]<br/>
  
 
'''Schedule Summary'''
 
'''Schedule Summary'''
Line 42: Line 42:
  
 
[[Media:STEEP_-_Bug_Metric_v1.xls‎| Bug Metric File ]]
 
[[Media:STEEP_-_Bug_Metric_v1.xls‎| Bug Metric File ]]
 +
  
 
'''Test Plan'''
 
'''Test Plan'''
Line 47: Line 48:
 
This is the test plan that we would be using to test for bugs during every iteration.
 
This is the test plan that we would be using to test for bugs during every iteration.
  
[[Media:STEEPTest_plan.xlsx| Test Plan ]]
+
[[Media:STEEPTest_plan.xlsx| Test Plan File ]]
  
 
==== Schedule Metric ====
 
==== Schedule Metric ====
Line 79: Line 80:
 
|rowspan="1"| 1
 
|rowspan="1"| 1
 
|| Resource Risk
 
|| Resource Risk
|| Insufficient android mobile phones during development and User Testing
+
|| Insufficient android phones during development and testing
|| High
+
|align="center"| High
|| <s>Low</s> High
+
|align="center"| High
|| A
+
|align="center"| A
 
||  
 
||  
*Plan UAT early and inform sponsors the number of mobile phones required
+
*Plan user testing early and inform sponsors
*Sponsors would be providing the mobile phones
+
*Borrow from friends for user testing
*Borrow from friends
+
*Purchase phones by team
 
|-
 
|-
  
 
|rowspan="1"| 2
 
|rowspan="1"| 2
|| Technical Risk  
+
|| Resource Risk
|| Working with new technology and tools
+
|| Insufficient users with android phones during user testing
|| Medium
+
|align="center"| High
|| High
+
|align="center"| High
|| A
+
|align="center"| A
 
||  
 
||  
*Arrange group sharing/learning sessions to improve knowledge
+
*Provide testers with android mobile phones
*Allocate sufficient time to familiarize with new technology and tools
+
*Group them in teams with 1 user having android phone
 +
*Enquire on testers’ phones prior to user testing to prepare
 
|-
 
|-
  
 
|rowspan="1"| 3
 
|rowspan="1"| 3
|| Resource Risk
+
|| Technical Risk  
|| Insufficient time for User Testing with SMU students
+
|| Software updating its version causing functions to stop working
|| Medium
+
|align="center"| High
|| Medium
+
|align="center"| Low
|| B
+
|align="center"| B
 
||  
 
||  
* Plan to complete all functionalities early to prepare for User Testing
+
* Halt development to tackle issue
 +
* Team members to research and help out
  
 
|-
 
|-
Line 174: Line 177:
 
[[Media:TM_14_-_1_OCT_2012.doc‎|Team Meeting 14 (01/10/2012)]]<br/>
 
[[Media:TM_14_-_1_OCT_2012.doc‎|Team Meeting 14 (01/10/2012)]]<br/>
 
[[Media:TM_15__-_3_OCT_2012.doc|Team Meeting 15 (03/10/2012)]]<br/>
 
[[Media:TM_15__-_3_OCT_2012.doc|Team Meeting 15 (03/10/2012)]]<br/>
 +
[[Media:TM_16__-_8_OCT_2012.doc|Team Meeting 16 (08/10/2012)]]<br/>
 +
[[Media:TM_17__-_9_OCT_2012.doc|Team Meeting 17 (09/10/2012)]]<br/>
 +
[[Media:TM_18__-_15_OCT_2012.doc|Team Meeting 18 (15/10/2012)]]<br/>
 +
[[Media:TM_19__-_22_OCT_2012.doc|Team Meeting 19 (22/10/2012)]]<br/>
 +
[[Media:TM_20__-_29_OCT_2012.doc|Team Meeting 20 (29/10/2012)]]<br/>
 +
[[Media:TM_21-_5_NOV_2012.doc|Team Meeting 21 (05/11/2012)]]<br/>
 +
[[Media:TM_22_-_12_NOV_2012.doc‎ |Team Meeting 22 (12/11/2012)]]<br/>
 +
[[Media:TM_23_-_16_NOV_2012.doc‎ |Team Meeting 23 (16/11/2012)]]<br/>
 +
[[Media:TM_24__-_23_NOV_2012.doc|Team Meeting 24 (23/11/2012)]]<br/>
 +
[[Media:TM_25__-_3_DEC_2012.doc|Team Meeting 25 (03/12/2012)]]<br/>
 +
[[Media:TM_26__-_4_DEC_2012.doc|Team Meeting 26 (04/12/2012)]]<br/>
 
</div>
 
</div>
  
Line 188: Line 202:
 
[[Media:SPM_8_-_26_SEP_2012.doc‎|Sponsor Meeting 8 (26/09/2012)]]<br/>
 
[[Media:SPM_8_-_26_SEP_2012.doc‎|Sponsor Meeting 8 (26/09/2012)]]<br/>
 
[[Media:SPM_9_-_6_OCT_2012.doc‎|Sponsor Meeting 9 (06/10/2012)]]<br/>
 
[[Media:SPM_9_-_6_OCT_2012.doc‎|Sponsor Meeting 9 (06/10/2012)]]<br/>
 +
[[Media:SPM_10_-_17_OCT_2012.doc‎|Sponsor Meeting 10 (17/10/2012)]]<br/>
 +
[[Media:SPM_11_-_27_NOV_2012.doc|Sponsor Meeting 11 (27/11/2012)]]<br/>
 
</div>
 
</div>
  
Line 197: Line 213:
 
[[Media:SVM_3_-_14_SEP_2012.doc|Supervisor Meeting 3 (14/09/2012)]]<br/>
 
[[Media:SVM_3_-_14_SEP_2012.doc|Supervisor Meeting 3 (14/09/2012)]]<br/>
 
[[Media:SVM_4_-_5_OCT_2012.doc‎|Supervisor Meeting 4 (05/10/2012)]]<br/>
 
[[Media:SVM_4_-_5_OCT_2012.doc‎|Supervisor Meeting 4 (05/10/2012)]]<br/>
 +
[[Media:SVM_5_-_15_NOV_2012.doc‎‎|Supervisor Meeting 5 (15/11/2012)]]<br/>
 +
[[Media:SVM_6_-_30_NOV_2012.doc‎|Supervisor Meeting 6 (30/11/2012)]]<br/>
 
</div>
 
</div>
 
|-
 
|-
 
|}
 
|}

Latest revision as of 06:29, 5 December 2012

Home The Team Project Overview Project Scope User Testing Project Management LOMS & Reflections

Schedule

View our Schedule

Schedule Summary

STEEPFunctionsFinal.png

Metrics

Bug Metric

Objective : To ensure an error-free application

Our bug metric is calculated at the end of every iteration.

Bug Metric File


Test Plan

This is the test plan that we would be using to test for bugs during every iteration.

Test Plan File

Schedule Metric

Objective : To improve schedule estimation accuracy

Our Schedule Metric is calculated at the end of every iteration.

Schedule Metric File

Risks

Risk Assessment

STEEPRiskAssessment.png

Risks & Mitigation Strategy

S/No Type of Risk Risk Statement Impact Level Likelihood Risk Assessment Mitigation Strategy
1 Resource Risk Insufficient android phones during development and testing High High A
  • Plan user testing early and inform sponsors
  • Borrow from friends for user testing
  • Purchase phones by team
2 Resource Risk Insufficient users with android phones during user testing High High A
  • Provide testers with android mobile phones
  • Group them in teams with 1 user having android phone
  • Enquire on testers’ phones prior to user testing to prepare
3 Technical Risk Software updating its version causing functions to stop working High Low B
  • Halt development to tackle issue
  • Team members to research and help out

Tools

- Microsoft Visual Studio
- Microsoft SQL Server
- Android SDK
- Eclipse Helios
- Adobe Photoshop

- Google Play
- Microsoft Azure

- Dropbox
- Google Docs
- IS480 Wikipedia
- Email


- Microsoft Project
- Microsoft Visio

Minutes