Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Final"
Line 244: | Line 244: | ||
| align="center" width = "5%"| 25-30 | | align="center" width = "5%"| 25-30 | ||
|- | |- | ||
+ | |||
+ | | align="center"| User Test 2 (Users & Client) | ||
+ | | align="center"| 23-Feb-14 to 24-Feb-14 | ||
+ | || | ||
+ | <b><u>User TESTING</u></b><br> | ||
+ | 1. Discover bugs and failure points<br> | ||
+ | 2. Evaluation | ||
+ | |||
+ | For more information, please click[[IS480 Team wiki|<b> here </b>]] | ||
+ | | align="center"| 10 | ||
+ | | align="center" width = "5%"| 21 - 35 | ||
+ | |- | ||
+ | |||
| align="center"| User Test 2 (Users & Client) | | align="center"| User Test 2 (Users & Client) | ||
Line 256: | Line 269: | ||
| align="center" width = "5%"| 21 - 35 | | align="center" width = "5%"| 21 - 35 | ||
|- | |- | ||
+ | |||
+ | <b><u>USERS & KALEEA UI/UX TESTING</u></b><br> | ||
+ | 1. Discover bugs and failure points<br> | ||
+ | 2. Evaluation of Usability | ||
+ | |||
+ | For more information, please click[[IS480 Team wiki|<b> here </b>]] | ||
+ | | align="center"| 10 | ||
+ | | align="center" width = "5%"| 21 - 35 | ||
+ | |- | ||
+ | |||
+ | |||
Revision as of 12:41, 2 April 2015
Home | Team T-Club | Project Overview | Project Management | Project Documentation |
Project Summary | Project Management | Quality of Products | Reflections |
|
Change Task/Event | Mitigation Plan |
---|---|
Low | Functions can be added to tertiary/good-to-have functions. Team will implement this function only if the core and secondary functions are done. |
Medium | Team is to only work on these function if the core functions are fulfilled. PM is to reschedule the task based on the level of priorities. |
High | Tasks is to be included in project schedule immediately. PM to reschedule tasks. Inform project supervisor if necessary to seek advice on how the team is going to proceed. |
Technical Complexity
Front-End Complexity
Back-End Complexity
- Retrieving Paypal IPN status to Salesforce and update inventory
Quality of Products
Intemediate Deliverables
Stage | Specification | Links |
---|---|---|
Project Management | Metrics |
|
Minutes | ||
Requirements | Prototype Mockups | |
Analysis | Use Cases Workflow | |
System Architecture Diagram | ||
Architecture Diagram | ||
Workflow | ||
Design | Technical Diagram | |
Class Diagram |
Deployement
Testing
Download a copy of our test plan here: UAT 1 | UAT 2
1. Discover bugs and failure points
2. Evaluation of Usability For more information, please click here
User Test | Date of Test | Objectives of Test | Number of participants | Age range |
User Test 1 (Client & Sponsors) | 13-Feb-14 | RE-ALIGN BUSINESS REQUIREMENTS
For more information, please click here |
4 | 25-30 |
User Test 2 (Users & Client) | 23-Feb-14 to 24-Feb-14 |
User TESTING For more information, please click here |
10 | 21 - 35 |
User Test 2 (Users & Client) | 23-Feb-14 to 24-Feb-14 |
USERS & KALEEA UI/UX TESTING For more information, please click here |
10 | 21 - 35 |
10 | 21 - 35 |
Reflection
Team Reflection
Our team has learnt the importance of effective communications and teamwork to achieve a common goal. The regular meetings that we have allow us to ensure that all members are on the same page and none are neglected before we move on to our specific tasks. Also, we support and learnt from one another by lending a helping hand if anyone has difficulties in completing the tasks and move forward as a team. In any event there is any doubts, we also learnt to express our opinions via the meetings, whatsapp or email.