Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Final"
Line 70: | Line 70: | ||
* Having to Google and post questions on Salesforce Stack Exchange (Forum) due to the lack of technical knowledge to implement the functions (eg. relations of carts and products, Paypal, Creating Customer Portal to manage Customers, picture rendering) | * Having to Google and post questions on Salesforce Stack Exchange (Forum) due to the lack of technical knowledge to implement the functions (eg. relations of carts and products, Paypal, Creating Customer Portal to manage Customers, picture rendering) | ||
* Insufficient rights from objects in Salesforce which resulted in the user interface to defer from the active sites and sites within Salesforce | * Insufficient rights from objects in Salesforce which resulted in the user interface to defer from the active sites and sites within Salesforce | ||
+ | * Finding a common time to meet the different project stakeholders due to the heavy workload in the second half of the semester. | ||
===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Project Achievements</font>=== | ===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Project Achievements</font>=== |
Revision as of 20:05, 3 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.