HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Final"

From IS480
Jump to navigation Jump to search
Line 189: Line 189:
 
===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Change Management</font>===
 
===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Change Management</font>===
  
<font color="red">** Changes as of after Mid-Term</font><br>
+
<font color="red">** Changes after Mid-Term</font><br>
 
Click [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_T-Club_Midterm#part9| here] to view the Mid-Term Change Metrics
 
Click [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_T-Club_Midterm#part9| here] to view the Mid-Term Change Metrics
  
Line 210: Line 210:
 
|-
 
|-
  
 +
|}
 +
 +
 +
{| class="wikitable" style="text-align: center; style="font-size:30%";
 +
|+
 +
|-
 +
! scope="col" width="500" style="background-color:black"| <font color="white">Change Task/Event</font>
 +
! scope="col" width="150" style="background-color:black"| <font color="white">Type</font>
 +
! scope="col" width="100" style="background-color:black"| <font color="white">Requestor</font>
 +
! scope="col" width="200" style="background-color:black"| <font color="white">Priority</font>
 +
! scope="col" width="500" style="background-color:black"| <font color="white">Description</font>
 +
! scope="col" width="200" style="background-color:black"| <font color="white">Member in charge</font>
 +
! scope="col" width="200" style="background-color:black"| <font color="white">Date Changed</font>
 +
! scope="col" width="100" style="background-color:black"| <font color="white">For Which Iteration</font>
 +
! scope="col" width="200" style="background-color:black"| <font color="white">Inform Team?</font>
 +
! scope="col" width="200" style="background-color:black"| <font color="white">Inform Supervisor?</font>
 +
! scope="col" width="200" style="background-color:black"| <font color="white">Inform Sponsor?</font>
 +
|-
 +
 +
! scope="row" style="background: #eeeeee"| Delay in Product Launch
 +
|style="text-align: left;"|Business
 +
|style="text-align: left;"|Team
 +
|style="text-align: left;"|High
 +
|style="text-align: left;"| Delay in the product launch due to problem deploying paypal live which resulted in the manual update of inventory
 +
|style="text-align: left;"|Gerald
 +
|style="text-align: left;"| 28/02/2015
 +
|style="text-align: left;"| 10
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| Yes
 +
|-
 +
 +
! scope="row" style="background: #eeeeee"| Adding additional UAT at iteration 12
 +
|style="text-align: left;"|Technical
 +
|style="text-align: left;"|Team
 +
|style="text-align: left;"|High
 +
|style="text-align: left;"|UAT 3 is mainly for Ui/UX testing. Hence team decided to have another user testing to test the phase 2 deliverables
 +
|style="text-align: left;"|Farah
 +
|style="text-align: left;"| 08/03/2015
 +
|style="text-align: left;"| 11
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| No
 +
|-
 +
 +
! scope="row" style="background: #eeeeee"| Shift Product Suggestion function from iteration 10 to 11
 +
|style="text-align: left;"|Technical
 +
|style="text-align: left;"|Team
 +
|style="text-align: left;"|High
 +
|style="text-align: left;"|Dropped this function due to some limitation in salesforce where all users share the same public cart when they are not logged in. Refer to project highlights for more info.
 +
|style="text-align: left;"|Hexing
 +
|style="text-align: left;"| 08/03/2015
 +
|style="text-align: left;"| 12
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| No
 +
|style="text-align: left;"| No
 +
|
 +
! scope="row" style="background: #eeeeee"| Drop Checkout as Guest Function
 +
|style="text-align: left;"|Technical
 +
|style="text-align: left;"|Team
 +
|style="text-align: left;"|High
 +
|style="text-align: left;"|Dropped this function due to some limitation in Salesforce where all users share the same public cart when they are not logged in. Refer to project highlights for more info.
 +
|style="text-align: left;"| SMU
 +
|style="text-align: left;"| 02/04/2015
 +
|style="text-align: left;"| 12
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| Yes
 +
|style="text-align: left;"| Yes
 +
|-
 +
 +
-
 
|}
 
|}
  

Revision as of 14:56, 5 April 2015

T-clublogo.png
Home Team T-Club Project Overview Project Management Project Documentation
Project Summary Project Management Quality of Products Reflections

Project Progress Summary

Project Progress Status

% Completion for the iteration: 80%
Download our slides File:Here
Preview our Deployed Site link, here

For Project Overview, please see visit our page to better understand our project & scope.


Completed Functions

  • Login & Registration
  • Reset Password
  • Search & Filter
  • Product Catelog Browsing
  • Cart Function (CRUD)
  • Paypal Payment
  • Product Suggestions
  • Promo Code
  • Mailing List Subscription
  • Email Automation (Registration, Forget password email, Subscription, Order Confirmation)
  • Reminder email to let customer cart their products
  • Inventory Management in Salesforce (CRUD)
  • Order Management in Salesforce (CRUD)

Project Highlights

  • Delay in launch fomr 1st March 2015 to 8th March 2015 due to the issues in automation in updating inventory upon payment
  • Live Deployment of web application on 8th March 2015
  • ____ Transactions
  • Embedded Google Analytics to track customer behaviour and profile
  • Dropped Checkout as Guest Function due to the Salesforce Guest Licensing restriction where every user who enters the site are treated as the same guest session, resulting in public cart. (where other users share the same cart as the one another)

Project Deliverables

Project Challenges

  • Problems in implementing Checkout As Guest Function due to the limitation in Salesforce guest license.
  • 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
  • Finding a common time to meet the different project stakeholders due to the heavy workload in the second half of the semester.

Project Achievements

Teamwork:

  • The project requires the coordination between the Front-End Developer and the Back-End Developer. Designing the programming model is required so that coding will be much easier. In any event if team members is facing any difficulty in coding or documentation,the rest will give advice in completing it if they are competent in the codes or documents.

Team Communication:

  • The arrangement of meeting every Tuesday and Friday, informal integration of members completed functions and development sessions among developers & progress updates. We also make use of whatsapp & email to foster closer teamwork and also optimized our working efficiency.

Project Management

Project Scope

Scope FAL.PNG Scope kaleea.PNG

Project Timeline

Planned Vs Actual

Project Status

  • 4 User Testing
  • 11 Completed Milestones

Project Schedule (Plan Vs Actual)

Tclub schedulemetrics.JPG

Observations:

Bug Metric

Tclub bugmetrics.JPG


Observations:

Risk Management

Tclub risk metric.png

Risk Activated

No. Risk Type Likelihood Impact Risk Level Risk Management Status
1 Change in requirements from Salesforce Business Medium High A Project manager is to compare and determine the difference in scope and how it will impact the project. Inform project supervisor and course coordinator immediately and seek advice on how the team should proceed. Pm is to review the project plan and identify new milestones and delegate work to the respective members. Activated
2 Insufficient technical knowledge to code out the function Technical Medium High A PProject manager is to review the plan and track the progress of the team members. Prioritise the tasks that needs to be done first and schedule a meeting to relay these to the team members. Work on the unfinished task once they are done with the critical task Activated
3 Unresolved backlog bugs Technical Medium Medium B Backlog bugs are bugs that but will not affect the entire system. Bugs should be log down in the bug metrics and pm is to assign members to resolved the bug asap when they have nothing on their plate or to resolve it during the debugging phase Activated

Future Risk

No. Risk Type Likelihood Impact Risk Level Risk Management Status
1 Kaleea Owners unfamiliar with how to use the salesforce system to add products and track orders upon handling over the system to them Technical Medium High B User manual with step by step guide to teach them how to use the system

|} Click here for a comprehensive risk assessment for every iterations

Change Management

** Changes after Mid-Term
Click here to view the Mid-Term Change Metrics

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.


-
Change Task/Event Type Requestor Priority Description Member in charge Date Changed For Which Iteration Inform Team? Inform Supervisor? Inform Sponsor?
Delay in Product Launch Business Team High Delay in the product launch due to problem deploying paypal live which resulted in the manual update of inventory Gerald 28/02/2015 10 Yes Yes Yes
Adding additional UAT at iteration 12 Technical Team High UAT 3 is mainly for Ui/UX testing. Hence team decided to have another user testing to test the phase 2 deliverables Farah 08/03/2015 11 Yes Yes No
Shift Product Suggestion function from iteration 10 to 11 Technical Team High Dropped this function due to some limitation in salesforce where all users share the same public cart when they are not logged in. Refer to project highlights for more info. Hexing 08/03/2015 12 Yes No No Drop Checkout as Guest Function Technical Team High Dropped this function due to some limitation in Salesforce where all users share the same public cart when they are not logged in. Refer to project highlights for more info. SMU 02/04/2015 12 Yes Yes Yes

Technical Complexity

Integrating Paypal to Salesforce

Back-End Complexity (Apex Classes)

  • Retrieving Paypal IPN status to Salesforce and update inventory
  • Picture rendering
  • User session

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

T-club system achi.jpg

Testing

Download a copy of our test plan here: UAT 1 | UAT 2


USERS & KALEEA UI/UX TESTING
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
1. Discover bugs and failure points
2. Evaluation

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
1. Discover bugs and failure points
2. Evaluation of Usability

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.

Individual Reflection