HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
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'''

Revision as of 04:15, 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