Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Midterm"
Line 378: | Line 378: | ||
===<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>=== | ||
− | {| class="wikitable" style="text-align: center; style="font-size: | + | {| class="wikitable" style="text-align: center; style="font-size:80%"; |
|+ | |+ | ||
|- | |- |
Revision as of 20:55, 20 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 | |||
Customer Portal Configuration (To Manage external users) | |||
Customer Account Management(CRUD) | |||
Inventory Management (CRUD) | |||
Search Function | 60% | ||
Upload Image | |||
Product Catalog | 80% | Arinah is still exploring how to further improve the user experiences(eg. Quick view for products) | |
Cart Function | |||
Checkout as Customer | |||
Checkout as Customer | |||
Mailing list to existing customers | |||
Integration of Paypal for payment | |||
Checkout as Guest |
Project Schedule (Plan Vs Actual)
Iterations | Tasks | Planned | Actual | Comments |
---|---|---|---|---|
1 | Form Team and Select Project for FYP | |||
1 | Gathering of project requirements | 12/09/14 - 19/09/14 | 12/09/14 - 19/09/14 | |
1 | Drafting of proposal | 15/09/14 - 19/09/14 | 15/09/14 - 19/09/14 | 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/10/14 - 12/10/14 | 10/10/14 - 12/10/14 | |
3 | Salesforce trainings for Apex and Visualforce (Programming Language) | 13/10/14 - 19/10/14 | 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/10/14 | 20/10/14 | Delay in creating customer portal sue to the need to get access rights from Salesforce |
3 | Edit and update user profile | 24/10/14 - 27/10/14 | ||
3 | Product Catalog view | |||
3 | Product uploads to Salesforce database |
Bug Metric
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 | Type | Requestor | Priority | Description | Member in charge | Date Changed | 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 |
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 (Internal Testing) | 5 | 17 - 24 | ||
User Test 2 (User & Owner) | 12-Feb-14 to 14-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.