HeaderSIS.jpg

IS480 Team wiki: 2012T1 6-bit Project Management UT3

From IS480
Jump to navigation Jump to search
6-bit logo.png
6-bit's Chapalang! is a social utility that connects people with friends and new friends
by offering a place for exchanging ideas and information on its public domain.
http://www.chapalang.com

Final Wikipage
Home Technical Overview Project Deliverables Project Management Learning Outcomes


Schedule

Planned Schedule

6-bit ScheduleDiagramOverview.png

































Meeting Minutes

Team Meeting Minutes

[|Meeting Minute 1] [|Meeting Minute 11] [|Meeting Minute 21]
[|Meeting Minute 2] [|Meeting Minute 12] [|Meeting Minute 22]
[|Meeting Minute 3] [|Meeting Minute 13] [|Meeting Minute 23]
[|Meeting Minute 4] [|Meeting Minute 14] [|Meeting Minute 24]
[|Meeting Minute 5] [|Meeting Minute 15] [|Meeting Minute 25]
[|Meeting Minute 6] [|Meeting Minute 16]
[|Meeting Minute 7] [|Meeting Minute 17]
[|Meeting Minute 8] [|Meeting Minute 18]
[|Meeting Minute 9] [|Meeting Minute 19]
[|Meeting Minute 10] [|Meeting Minute 20]

Supervisor Meeting Minutes

|Meeting Minute 1
|Meeting Minute 2
|Meeting Minute 3
|Meeting Minute 4
|Meeting Minute 5
|Meeting Minute 6
|Meeting Minute 7
|Meeting Minute 8
|Meeting Minute 9
|Meeting Minute 10
|Meeting Minute 11

Testing

Test Cases

|Test Cases

Test Plans

Test Plan 1 on 17 September 2012
Test Plan 2 on 28 September 2012
Test Plan 3 on 19 October 2012
Test Plan 4 on 4 November 2012

User Testing

User Testing 1 User Testing 2 User Testing 3 User Testing 4

User Testing 3

6bituser-testing3.png

Test Description

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.

Testers Background

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.

6bituser-testing3results.png

Test Groups

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.

Test Procedures

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.

Test Instruction

Click Here to Download User Testing 3 Instruction

Test Results

There are also 19 reported bugs, and 32 recommendations for improvements received. The following are the top 10 bugs reported.
6bituser-testing3bug.png
Most of the recommendations are repeated from User Test 1 and 2, and hence will not be published.

Milestones

6-bit schedule.png

Schedule Metric

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%

6-bit schedulemetric.png

Bug Metric

Log

6-bit BugMetric.png 6-bit BugLog.png

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
  • Status
  • Owner of the function
  • Fixed date
  • Closed by (Tester)
  • Close date
  • Additional comments

Metric

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

6-bit BugMetricFormula.png


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:

6-bit BugMetricFormula2.png

Risk & Mitigation


6-bit RiskDiagram.png