IS480 Team wiki: 2012T1 6-bit Project Management UT3
by offering a place for exchanging ideas and information on its public domain.
|Home||Technical Overview||Project Deliverables||Project Management||Learning Outcomes|
- 1 Schedule
- 2 Testing
- 3 Milestones
- 4 Schedule Metric
- 5 Bug Metric
- 6 Risk & Mitigation
Team Meeting Minutes
Supervisor Meeting Minutes
|User Testing 1||User Testing 2||User Testing 3||User Testing 4|
User Testing 3
The objective of User Test 3 is on functionality and usability testing of the system. The coverage of the test is focused on the key features of the system which is Private Message, Escrow, Gift Sharing and Mass Order.
The purpose of the test is to test that the system is functioning according to design, and/or to spot any bugs or anomalies not detected by the team. The test also seeks to collect inputs on possible enhancements or improvements preferred by the sampled group of testers.
There are a total of 30 testers who attended the User Test, of which 70% (21) are male and 30% (9) are female, representing various schools in SMU with SIS students being the majority. It is also observed that most testers are users of Chrome and Firefox web browser.
There is no significant difference between testers’ background in User Test 1, 2 and 3.
There are 2 test groups employed in this test.
Group A consists of 15 testers who are guided by an instruction sheet on a series of tasks to be tested. The purpose of this group is to test the system by a set of test case based on the design of the system.
Group B consists of 15 testers who are unguided, and encouraged to explore the full system seeking for any uncommon encounters in their experience. The purpose of this group is to test the system in the role of a random user who may explore use-cases or sequence of activities not intended by design but possible by usage.
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!.
Only testers from Group A are provided with the instruction sheet. Thereafter, both groups of testers will fill in details in an open-ended form, should they encounter any bugs or suggestions for improvements.
There are also 19 reported bugs, and 32 recommendations for improvements received. The following are the top 10 bugs reported.
Most of the recommendations are repeated from User Test 1 and 2, and hence will not be published.
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%
Bug Log: |Click Here
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:
- Index number
- Bug description
- Found by
- Found date
- Expected solve-by date
- Bug severity
- Owner of the function
- Fixed date
- Closed by (Tester)
- Close date
- Additional comments
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.
Total Points for Each Iteration = Σ Points of the Bugs in each iteration
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric: