Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Midterm"
Line 591: | Line 591: | ||
|} | |} | ||
+ | |||
+ | Click here for a more detailed project schedule | ||
===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Bug Metric</font>=== | ===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Bug Metric</font>=== |
Revision as of 17:07, 24 February 2015
Home | Team T-Club | Project Overview | Project Management | Project Documentation |
Project Summary | Project Management | Quality of Products | Reflections |
|
Task/Functions | Satus | Confident Level(0-1) | Comment |
---|---|---|---|
Salesforce Administration Configuration | 100% | 1 | Completed configuration for customer portal and objects according to the business needs |
Customer Portal Configuration (To Manage external users) | 100% | 1 | Setting up customer portal to allow external customer login and registration for the web application |
Customer Account Management(CRUD) | 100% | 1 | Customer registration and update of their personal particular complete. |
Inventory Management (CRUD) | 90% | 0.9 | Keep track of inventory and update owners if the inventory is out of stocks |
Search Function | 60% | 1 | Function done but need to improvise further to improve user experience |
Upload Image | 90% | 0.9 | Change in scope and requirements. This function is not required from the new client |
Product Catalog | 80% | 1 | Arinah is still exploring how to further improve the user experiences(eg. Quick view for products) |
Cart Function | 90% | 0.9 | |
Product Catalog | 100% | 1 | Function completed |
Mailing list to existing customers | 80% | 1 | |
Integration of Paypal for payment | 90% | 1 | Gerald is in-charge of integration Paypal to Salesforce, retrieving grand total from shopping cart and deduct money from customer and transfer to merchant. Pending to set it to "live" mode. |
Product suggestions | 0% | 0.8 | Chloe is researching on how should she implement this function [Phase 2 implementation] |
Checkout as Customer | 0% | 0.8 | Hexing will be in charge of this function after mid-term presentation.[Phase 2 implementation] |
Membership Loyalty Program | 0% | 0.8 | Farah will be in charge of this function after mid-term presentation.[Phase 2 implementation] |
Discount and Promo Code for Shopping Cart | 0% | 0.8 | Gerald will be in charge of this function after mid-term presentation.[Phase 2 implementation] |
Project Schedule (Plan Vs Actual)
Iterations | Tasks | Planned | Actual | Comments |
---|---|---|---|---|
1 | Gathering of project requirements | 12th Sept 2014 - 19 Sept 2014 | 12th Sept 2014 - 19 Sept 2014 | |
1 | Drafting of proposal | 15 Sept 2014 - 19 Sept 2014 | 15 Sept 2014 - 19 Sept 2014 | First draft of proposal for sponsors to vet through |
2 | Salesforce Configuration Training for New Administrator | 29 Sept 2014 - 05 Sept 2014 | 29 Sept 2014 - 09 Sept 2014 | Online configuration trainings to allow T-club members to modify the objects based on the business needs |
2 | Salesforce Configuration Training for New Administrator | 29 Sept 2014 - 05 Sept 2014 | 29 Sept 2014 - 09 Sept 2014 | Online configuration trainings to allow T-club members to modify the objects based on the business needs |
1 | Create Technical Diagram (Class, User Case, Architecture Diagram) | 15 Sept 2014 - 19 Sept 2014 | 15 Sept 2014 - 19 Sept 2014 | Designing of technical diagram based on Trunk Club (Previous client) business model |
2 | 2nd Draft of Project Proposal | 8 Oct 2014 - 10 Oct 2014 | 8 Oct 2014 - 10 Oct 2014 | |
2 | Low-Fidelity prototype | 10 Oct 2014 - 12 Oct 2014 | 10 Oct 2014 - 12 Oct 2014 | [Documentation] Arinah & Chloe to work on the prototype of the web application |
2 | Design Schema on Salesforce Platform | 10 Oct 2014 | 10 Oct 2014 | [Documentation] Hexing and Farah to work hand in hand in coming out of the schema and the relationship between the different objects on Salesforce platform. |
3 | Salesforce trainings for Apex and Visualforce (Programming Language) | 13 Oct 2014 - 19 Oct 2014 | 13 Oct 2014 - 19 Oct 2014 | Basic tutorial trainings with step-by-step guide to teach T-club how to code in apex and visualforce |
3 | Create Customer Portal to enable user login and registrations | 17 Oct 2014 | 20 Oct 2014 | Delay in creating customer portal sue to the need to get access rights from Salesforce |
3 | Edit and update user profile | 24 Oct 2014 - 27 Oct 2014 | 24 Oct 2014 - 27 Oct 2014 | [User Management- customer] Allow editing of some information on customer account |
4 | Product Catalog view (Product simple filter, product grid view) | 20 Oct 2014 - 25 Oct 2014 | 20 Oct 2014 - 25 Oct 2014 | [User Interface] Arinah to come out with the user interface of the product catalog and product details page |
5 | Product browsing enhancement | 10 Nov 2014 - 12 Nov 2014 | 10 Nov 2014 - 12 Nov 2014 | [User Interface] Back to top and multiple products in product details page |
5 | Retrieve/View Cart Orders | 10 Dec 2014 - 12 Dec 2014 | 10 Dec 2014 - 12 Dec 2014 | [Customer Account Module] Hexing to retrieve customer cart orders history on user account page |
5 | Retrieve/View Ad-Hoc request Orders | 12 Dec 2014 - 16 Dec 2014 | 12 Dec 2014 - 16 Dec 2014 | [Customer Account Module] Hexing to retrieve customer ad-hoc request orders history on user account page |
5 | Stylist subscription for customers | 12 Dec 2014 - 16 Dec 2014 | 12 Dec 2014 - 16 Dec 2014 | [Customer Account Module] Enable stylist subscription in user account |
5 | Assignment of stylist to user | 16 Dec 2014 - 18 Dec 2014 | 16 Dec 2014 - 18 Dec 2014 | [Customer Account Module] Hexing to work on the assignment of stylist to users.Delay in task but managed to complete it within iteration 5. Assignment of stylist to customer algorithm done by hexing using the most available , gender, specialisation and age of customer |
5 | Add multiple products to cart | 11 Dec 2014 - 15 Dec 2014 | 11 Dec 2014 - 15 Dec 2014 | [Cart Management] Allow Multiple products to be added to cart |
5 | Tabulate total amount for all cart items | 16th Dec 2014 - 18 Dec 2014 | 16th Dec 2014 - 18 Dec 2014 | [Cart Management] Farah to allow Multiple products to add in to shopping cart |
6 | Tabulate total amount for all cart items | 16th Dec 2014 - 18 Dec 2014 | 16th Dec 2014 - 18 Dec 2014 | [Cart Management] Farah to Remove/Add cookie when user add to cart |
6 | Product Details Page | 24 Dec 2014 - 26 Dec 2014 | 24 Dec 2014 - 26 Dec 2014 | [Cart Management] |
6 | Update product quantity upon checkout | 9 Jan 2015 - 9 Dec 2014 | 24 Dec 2014 - 26 Dec 2014 | [Inventory Management] |
6 | Update product quantity for ad-hoc styling request | 9 Jan 2015 - 9 Dec 2014 | 24 Dec 2014 - 26 Dec 2014 | [Inventory Management] |
7 | Create Paypal stimulation merchant account | 24 Dec 2015 - 25 Dec 2014 | 24 Dec 2014 - 26 Dec 2014 | [Inventory Management] Remove/Add cookie when user add to cart |
7 | Create stylist profile on Salesforce | 4 Jan 2015 | 4 Jan 2015 | [User Management- Stylist] |
7 | Assigning users to stylist profile on salesforce | 5 Jan 2015 | 5 Jan 2015 | [User Management- Stylist] |
7 | Assigning users to stylist profile on salesforce | 4 Jan 2015 | 4 Jan 2015 | [User Management- Stylist] |
7 | Stylist to view the customers' orders, ad-hoc request and Trunk products | 8 Jan 2015 - 10 Jan 2015 | 8 Jan 2015 - 10 Jan 2015 | [User Management- Stylist] |
7 | Update object permission of stylist on Salesforce | 4 Jan 2015 | 4 Jan 2015 | [User Management- Stylist] |
7 | Update assigned stylist and database when user submit a ad-hoc request for styling service | 8 Jan 2015 - 10 Jan 2015 | 8 Jan 2015 - 10 Jan 2015 | [Inventory Management] |
7 | Update product status for ad-hoc request | 9 Jan 2015 - 12 Jan 2015 | 9 Jan 2015 - 12 Jan 2015 | [Inventory Management] Remove/Add cookie when user add to cart |
7 | Notification alert for stylist upon new ad-hoc request from customers | 9 Jan 2015- 12 Jan 2015 | 9 Jan 2015 - 12 Jan 2015 | [Orders Management- Request for Trunk (Ad-Hoc Request Styling)] Remove/Add cookie when user add to cart |
7 | Create email after user is subscripted to styling services | 9 Jan 2015 - 12 Jan 2015 | 9 Jan 2015 - 12 Jan 2015 | [Orders Management- Request for Trunk (Ad-Hoc Request Styling)]Assignment of users to stylist email to stylist |
8 | Retrieve total amount from checkout | 19 Jan 2015 - 20 Jan 2015 | 19 Jan 2015 - 20 Jan 2015 | [Payment Management] |
8 | Deduct Amount from checkout from customer to transfer to merchant account | 19 Jan 2015 - 20 Jan 2015 | 19 Jan 2015 - 20 Jan 2015 | [Payment Management] |
8 | Update customer paypal payment status on salesforce database | 19 Jan 2015 - 21 Jan 2015 | 19 Jan 2015 - 12 Feb 2015 | [Payment Management] Delay in retrieving IPN status to update inventories and customer orders. This task is shifted to next iteration. |
8 | Validate customer paypal or credit details | 19 Jan 2015 - 21 Jan 2015 | 19 Jan 2015 - 12 Feb 2015 | [Payment Management] Delay in retrieving IPN status to update inventories and customer orders. This task is shifted to next iteration. |
8 | Show the inventory available for stylist to pick the clothes on Salesforce | 21 Jan 2015 | 21 Jan 2015 | [Inventory Management-Select clothes for customers] Delay in retrieving IPN status to update inventories and customer orders. This task is shifted to next iteration. |
8 | Update item status upon picking the clothes for customer | 22 Jan 2015 - 23 Jan 2015 | 22 Jan 2015 | [Inventory Management-Select clothes for customers] Ended this task earlier than planned |
8 | Update inventory based on what customer took from the trunk box | 24 Jan 2015 | 24 Jan 2015 | [Inventory Management-Select clothes for customers] Ended this task earlier than planned |
9 | Change in client and scope of project | |||
9 | Modification of user interface based on new client's expectation | 7 Feb 2015- 10 Feb 2015 | 7 Feb 2015- 10 Feb 2015 | [Content Management] Delay in changing UI for kaleea due to the integration of front end and backend. Task managed to complete within the same iteration |
10 | Modification of Inventory Management to new client's requirements | 5 Feb 2015- 12 Feb 2015 | 5 Feb 2015- 12 Feb 2015 | [Inventory Management] Product association and inclusion of backorders (iteration 9 and 10)
Backorder inventories count in product objects |
10 | Changes from UAT 1 | 13 Feb 2015- 22 Feb 2015 | 13 Feb 2015- 22 Feb 2015 | Refer to User Testing for more information on changes for UAT |
10 | Search Capabilities | 21 Feb 2015 - 22 Feb 2015 | 21 Feb 2015 - 22 Feb 2015 | [User Interface] Hexing in charge of this function |
10 | Retrieve orders history with products bought in user account | 22 Feb | 22 Feb 2015 | [Order Manaagement] |
10 | Changes from UAT 2 | 23 Feb 2015 - 25 Feb 2015 | 23 Feb 2015 - 25 Feb 2015 |
Click here for a more detailed project schedule
Bug Metric
Observations:
Risk Management
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 |
Click here for a comprehensive risk assessment for every iterations
Change Management
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? |
---|---|---|---|---|---|---|---|---|---|---|
Shifting Ad-Hoc Styling Request Module Module from Phase 6 to Phase 7 | Technical | Team | High | Members have too much work on hand. PM decide to shift the task to the later iteration to lessen their workload | Farah | 16/1/2015 | 6 | Yes | No | No |
Shifting of Search funcion from Phase 8 to Phase 10 | Technical | Team | High | Members have too much work on hand. PM decide to shift the task to the later iteration to lessen their workload | Farah | 16/1/2015 | 6 | Yes | No | No |
Shift communication between stylist from phase 9 to phase 11 | Project Management | Chloe | Low | Ensure that the team has done up the core and secondary function before working on the additional features | Chloe | 8/12/2015 | 8 | Yes | No | No |
Allocate more time for paypal implementation | Technical | Team | High | IPN issues to retrieve payment status from paypal is not working at the very last moment. Allocated more time for this function | Gerald | 19/1/2015 | 8 | Yes | No | No |
Changed of requirements & Scope (All scope has changed from Phase 9 onwards) | ||||||||||
Remove Facebook Sign in | Technical | Team | Nil | Change of requirements & Scope. This function is no longer applicable for new client | Nil | 05/02/2015 | 11 | Yes | No | No |
Drop UAT 1 (FormAsiaLabel) as it is not applicable to the new client | Technical | Team | Nil | Drop UAT 1 (FormAsiaLabel) as it is not applicable to the new client | Nil | 05/02/2015 | 9 | Yes | Yes | No |
Remove Styling Module | Technical | Client & Sponsor | Nil | Change of requirements & Scope. This function is no longer applicable for new client. Remove Stylist selection of clothes function to subscriped customers | Nil | 05/02/2015 | 9 | Yes | Yes | Yes |
Remove Customer Wishlist function | Technical | Client & Sponsor | Nil | Change of requirements & Scope. This function is no longer applicable for new client | Nil | 05/02/2015 | 11 | Yes | Yes | Yes |
Remove Stylist account management | Technical | Client & Sponsor | Nil | Change of requirements & Scope. This function is no longer applicable for new client | Nil | 05/02/2015 | 7 | Yes | Yes | Yes |
Remove assignment of customer to stylist | Technical | Client & Sponsor | Nil | Suggest product based on customer preference and the product that they view. [Phase 2 mplementation] | Hexing | 05/02/2015 | 7 | Yes | Yes | Yes |
Add Product Checkout as Guest Function | Technical | Client & Sponsor | Medium | Allow customer to checkout without logging in or sign up an account. Customer account will automatically be created once user checkout as guest.Phase 2 requirements [Phase 2 mplementation] | Medium | 05/02/2015 | 11 | Yes | Yes | Yes |
Add Mailing List | Technical | Client & Sponsor | Medium | Mailing list for all registed customer | Hexing, Gerald | 05/02/2015 | 9 | Yes | Yes | Yes |
Add Backorders Function | Technical | Client & Sponsor | High | Build a simple BO function for Kaleea before Mid-term and their launch(1st March). Improvised automated BO function will be done at phase 2 | Farah | 05/02/2015 | 9 | Yes | Yes | Yes |
Add Membership Loyalty Program | Technical | Client & Sponsor | Medium | Team T-club is to discussed with Kaleea on what kinds of loyalty program Kaleea could adopt to improve their customer base. | Team | 05/02/2015 | 11 | Yes | Yes | Yes |
Product Suggestion | Technical | Client & Sponsor | Medium | Suggest products to customers based on their purchase history and preference style | Team | 05/02/2015 | 11 | Yes | Yes | Yes |
Change of Domain Name | Technical | Team | High | Porting of Domain from t-club.force.com to kaleea.com | Salesforce, SMU Team | 05/02/2015 | 10 | Yes | Yes | Yes |
Add Trend Analysis | Business | Client & Sponsor | High | Track the customer behavaiour track any drop out rate and traffic of the customer on a certain page. | Chloe, Gerald | 05/02/2015 | 12 | Yes | Yes | Yes |
Email to remind customer to checkout their products | Business | Client & Sponsor | Low | Have an email reminding customer to checkout their product if they leave it in the cart for some period of time without checking out | Chloe | 05/02/2015 | 13 | Yes | Yes | Yes |
Technical Complexity
Front End Complexity
Back End complexity
1) Initially we use cookie for our carts, however we find that it's difficult to manage cookie and delete the cookie
2) Integration with front end LIVE (visualforce) and apex controller, expectations are met or not
3) The functionality can be pretty straight forward but the technical abilities could be an obstacles - with help from Google and salesforce forums, we are able to overcome the obstacles
4) Converting business requirements to technical requirements
5) Integrating external vendor(Paypal) to Salesforce
6) Customising Objects in Salesforce based on Kaleea's Business needs
7) Using Apex and Visualforce to code the web application
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
User Test | Date of Test | Objectives of Test | Number of participants | Age range |
User Test 1 (Client & Sponsors) | 13-Feb-14 | It is to look at the general usability of
1. How easy is it for owner of Kaleea to learn how to use our web application? |
4 | |
User Test 2 (Users & Client) | 23-Feb-14 to 24-Feb-14 | It is to look at the general usability of
1. How easy is it for owner of Kaleea to learn how to use our web application? |
15 | 20 - 35 |
Summary of the user test.
- A total of 2 user tests were conducted before Mid-Term for both the administrator and the to-be users of Kaleea.
- The purpose of the user test is to ensure that the technical aspects align with the business needs to the owners of Kaleea
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
Chloe:
Arinah:
Farah:
Gerald:
Hexing: