IS480 Team wiki: 2016T1 Stark Final Wiki
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of Product
- 4 Reflection
Project Progress Summary
Final Slides: [ Download Here]
MaiMai is deployed for production at
MaiMai is deployed for testing purpose at
Learn more about us at http://www.maitwo.com
Total Iterations: 16
Iteration Dates (Current):
Iteration Dates (Final):
Scope Changes The following changes has been made to our project scope and reflected in our schedule.
Schedule Highlights The following changes has been made to our project scope and reflected in our schedule.
- Shift iBanking from iteration 12 to iteration 13
|Iteration||Planned Duration (Days)||Actual Duration (Days)||Schedule Metric Score||Action Taken||Status|
|8||14||16||0.88||More time needed to fix bugs from UT1 and after the integration of Dispute Management.
Follow up action: Informed supervisor and mentor about the delay. More hours put in for debugging. No major delay to overall schedule.
|Iteration||Bug Score||Bug Summary||Action Taken|
|The spike in bug count is due to the integration of dispute management system together with previous completed features.||Resolve bugs immediately. No major delay was caused.|
|The spike in bug count is because of the integration of many new features together for UT1.||Resolve bugs immediately. Iteration 8 was scheduled for post UT1 debugging. PM scheduled the Lead Backend developer to focus on debugging while the rest of the developers focus on development.|
|The first critical bug was system crashed when a dispute for review is filed. The second critical bug was images is not updated when listing image name is being edited.||Resolve bugs immediately. No major delay was caused. Critical bug did not occur again. Similar action was performed but bug did not replicate.|
|Risk Description||Likelihood||Impact||Mitigation Strategy|
|Mismatch of product against market.||High||High
Developed product may not be what our target users or anyone in the market wants.
|1. Gather more feedbacks during testing to validate market needs against project idea. |
2. Transact with more real user and conduct interview with them to understand the problems and needs of the market.
|Quick rise of direct competition||Low||Low
Existing application like Caurosell can easily implement payment services that we are providing.
|We provide user with dispute management service which is something that is unique to us and we are investing our resources into defining a stringent and reliable process of micro management. As such we have the upper hand because that is our prime feature. However, it still remain as a risk. |
Quality of Product
|Project Requirements||Market Research||Market Research|
|Metrics|| Schedule Metrics|
|Change Management||Change Management|
|Testing||User Testing 1|| User Test 1|
User Test 2
User Test 3
|User Testing 1||1st August 2016 - 8th August 2016||Off-Site (At respective members' discretion)||22||User Testing 1|
|User Testing 2||12th September 2016 - 26th September 2016||SIS GSR 2-7 & Off-Site (At respective members' discretion)||38||User Testing 2|
|User Testing 3||User Testing 3|
Lee Chian Yee
Raji Hemanth Kumar
Phua Xue Yong
Darren Tay Kuang Yong