Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Midterm"
Line 121: | Line 121: | ||
===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Project Timeline</font>=== | ===<font style="font-family:Calibri;letter-spacing:-0.1em;font-weight:bold;text-transform:uppercase; font-size:22px">Project Timeline</font>=== | ||
− | Planned | + | Planned Timeline<br> |
[[File:Tclubtimeline(OLD).jpg|1350px]] | [[File:Tclubtimeline(OLD).jpg|1350px]] | ||
− | <br> | + | <br><br><br> |
+ | Actual Timeline | ||
[[File:Tclubtimeline.jpg|1350px]] | [[File:Tclubtimeline.jpg|1350px]] | ||
Revision as of 23:31, 22 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 | |
Checkout as Customer | 0% | 1 | Hexing will be in charge of this function after mid-term presentation.[Phase 2 implementation] |
Product Catalog | 100% | 1 | Function completed |
Mailing list to existing customers | 80% | 1 | |
Integration of Paypal for payment | 100% | 1 | Paypal integration to Salesforce |
Product suggestions | 0% | 0.5 | Phase 2 (finals)deliverables |
Project Schedule (Plan Vs Actual)
Iterations | Tasks | Planned | Actual | Comments |
---|---|---|---|---|
1 | Form Team and Select Project for FYP | |||
1 | Gathering of project requirements | 12th Sept 2014 - 19 Sept 2014 | 12th Sept 2014 - 19 Sept 2014 | |
1 | Drafting of proposal | 15th Sept 2014 - 19th Sept 2014 | 15th Sept 2014 - 19th Sept 2014 | First draft of proposal for sponsors to vet through |
2 | Salesforce Configuration Training for New Administrator | 29/9/14 - 05/09/14 | 29/9/14 - 09/9/14 | Online configuration trainings to allow T-club members to modify the objects based on the business needs |
2 | Create Technical Diagram (Class, User Case, Architecture Diagram) | |||
2 | 2nd Draft of Project Proposal | |||
2 | Low-Fidelity prototype | |||
2 | Design Schema on Salesforce Platform | |||
2 | Low-Fidelity prototype | 10 Oct 2014 - 12 Oct 2014 | 10 Oct 2014 - 12 Oct 2014 | |
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 | |||
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 | |
3 | Product Catalog view | |||
3 | Product uploads to Salesforce database |
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 (Refer to Change Metrics) |
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 (Refer to Change Metrics) |
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 (Refer to Change Metrics) |
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 Stylist Account 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 |
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
- Integrating external vendor(Paypal) to Salesfore
- Customising Objects in Salesforce based on Kaleea's Business needs
- Porting a new Domain to Salesforce
- 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 | ER Diagram |
|
Class Diagram | [] |
Deployement
Testing
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: