Difference between revisions of "IS480 Team wiki: 2012T1 STEEP PROJECT MANAGEMENT"
Jump to navigation
Jump to search
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 49: | Line 48: | ||
[[Media:STEEPTest_plan.xlsx| Test Plan File ]] | [[Media:STEEPTest_plan.xlsx| Test Plan File ]] | ||
− | |||
==== Schedule Metric ==== | ==== Schedule Metric ==== |
Revision as of 05:20, 5 December 2012
Home | The Team | Project Overview | Project Scope | User Testing | Project Management | LOMS & Reflections |
Contents
Schedule
Schedule
Schedule Summary
Metrics
Metrics
Bug Metric
Objective : To ensure an error-free application
Our bug metric is calculated at the end of every iteration.
Test Plan
This is the test plan that we would be using to test for bugs during every iteration.
Schedule Metric
Objective : To improve schedule estimation accuracy
Our Schedule Metric is calculated at the end of every iteration.
Risks
Risks
Risk Assessment
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 |
|
2 | Resource Risk | Insufficient users with android phones during user testing | High | High | A |
|
3 | Technical Risk | Software updating its version causing functions to stop working | High | Low | B |
|
Tools
Tools
Development Tools
- Microsoft Visual Studio |
Deployment Tools
- Google Play |
Collaboration Tools
- Dropbox
|
Project Management Tools
- Microsoft Project |
Minutes
Minutes