HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 16: Line 16:
 
| style="border-bottom:5px solid #000000; border-top:5px solid #000000; background:none;" width="3%" |  
 
| style="border-bottom:5px solid #000000; border-top:5px solid #000000; background:none;" width="3%" |  
  
| style="padding:0 .4em; background-color:#FF3366; font-family:Tahoma; border-bottom:5px solid #000000; border-top:5px solid #000000; text-align:center; color:#000000" width="12%" |[[IS480_Team_wiki:_2012T1_STEEP_PROJECT_MANAGEMENT |<font color="White">Project Management</font>]]
+
| style="padding:0 .4em; background-color:#5ee5ec; font-family:Tahoma; border-bottom:5px solid #000000; border-top:5px solid #000000; text-align:center; color:#000000" width="12%" |[[IS480_Team_wiki:_2012T1_STEEP_PROJECT_MANAGEMENT |<font color="White">Project Management</font>]]
 
| style="border-bottom:5px solid #000000; border-top:5px solid #000000; background:none;" width="3%" |  
 
| style="border-bottom:5px solid #000000; border-top:5px solid #000000; background:none;" width="3%" |  
  

Revision as of 10:41, 30 November 2012

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

Schedule

View our actual Schedule

Schedule Summary

STEEPScheduleSummary.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


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

Test Plan

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 mobile phones during development and User Testing High Low High A
  • Plan UAT early and inform sponsors the number of mobile phones required
  • Sponsors would be providing the mobile phones
  • Borrow from friends
2 Technical Risk Working with new technology and tools Medium High A
  • Arrange group sharing/learning sessions to improve knowledge
  • Allocate sufficient time to familiarize with new technology and tools
3 Resource Risk Insufficient time for User Testing with SMU students Medium Medium B
  • Plan to complete all functionalities early to prepare for User Testing

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