Difference between revisions of "IS480 Team wiki: 2015T1 Codex Final Wiki""
Jump to navigation
Jump to search
Currently At: Iteration 11
Line 309: | Line 309: | ||
| Human Risk | | Human Risk | ||
| Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. | | Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. | ||
− | |||
| Medium | | Medium | ||
− | | | + | | Medium |
+ | | B | ||
| If time permits and it is a small task, shift the subtask to another iteration. Else, code sharing session and another coder will take over. | | If time permits and it is a small task, shift the subtask to another iteration. Else, code sharing session and another coder will take over. | ||
|- | |- |
Revision as of 22:01, 8 April 2016
Deployed link : http://crystalnatural.com.sg/
Acceptance Slides
Project Highlights
- Our project has 11 iteration.
- As of 8 April 2016, we have completed 100% of our development, a revenue generating platform for our Client, Crystal Natural Products.
- As of 8 April, our project generated more than $200 SGD, with more than 20 transactions.
- We have conducted 1 user testing before mid terms, which consist of 6 customers of our client. 2 user testing before finals, which consist of 10 customers of our client.
- There was no major changes in requirements throughout this period.
- There was a re-scope of our project after Mid Term as our team decided to focus on the quality of basic functions instead of developing additional functions.
- These changes include removing Sales Performance Module from our project and replacing it with Coupon Analysis Module which is specifically for the coupon analysis sub task.
- View outlet with Google Map was also removed with Client's approval.
- The modules we decided to focus at the expense of other functions, are the functions which are revenue generating and would add value to our Client.
- The team has completed the project and delivered the application on time.
Project Summary
Project Management
Module | Status | Confidence level (0-1) | Comment |
---|---|---|---|
User Management Module | Fully Deployed and Tested 100% | 1 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Product Management Module | Fully Deployed and Tested 100% | 1 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Order Management Module | Fully Deployed and Tested 100% | 1 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Inventory Management Module | Fully Deployed and Tested 100% | 1 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Customer Relationship Management Module | Fully Deployed and Tested 100% | 1 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Coupon Analysis Module | Fully Deployed and Tested 100% | 1 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Project Schedule
Planned Schedule
Actual Schedule
Notes:
Changes before mid terms
- Some major changes in schedule throughout this period involves delaying our User Test 1 to iteration 7(actual) instead of Iteration 4(planned). This change was due to our team wanting to test the system together with our paypal function to give users a complete experience, but paypal function was delayed to Iteration 6.
- In addition, we decided to combine the planned iteration 5 and 6 together into one iteration in the midst of our development.
- There are also slight re-scoping of our project after meeting with the Supervisor and we have liase with our Client and got her agreement.
- These changes include new sub-task (i.e. Auto printing shipping addresses for label and website clicks tracking).
- Because of these new changes, we decided to drop sub task Product Comparison and seeked our Client agreement.
Changes after mid terms
- UAT2 was delayed from Iteration 8 to 9. This delay was due to Client's delaying to give us real product pictures to do the UAT2.
- There was also a re-scope of our project after Mid Term as our team decided to focus on the quality of basic functions instead of developing additional functions.
- These changes include removing Sales Performance Module from our project and replacing it with Coupon Analysis Module which is specifically for the coupon analysis sub task.
- View outlet with Google Map was also removed with Client's approval.
- The modules we decided to focus at the expense of other functions, are the functions which are revenue generating and would add value to our Client.
Project Metrics
Iteration | Period | Task Metric Score | Actions |
---|---|---|---|
Iteration | Bug Score | Summary of Bugs | Action Taken |
---|---|---|---|
There is no planned and actual testing done. We decided to focus on Acceptance development. | |||
There is no planned and actual testing done. We decided to focus on Acceptance development. | |||
The first testing is done and is for a major part of our development, the User Management Module, hence the surge in bugs. We discovered 4 high impact bugs and 17 low impact bugs. Low impact bugs were from the UI Error Messages. | |||
2 high impact bugs due to unable to process adding and editing of product should an unacceptable input be keyed in. | |||
1 high impact bugs and 1 low impact bug found in Order and Inventory Management Module, mainly from View Order History Page. | |||
There is no planned and actual testing done in this iteration. | |||
2 High Impact Bugs from session and redirecting problems. 3 low impact errors discovered during our UAT. | |||
2 Low impact bugs and 3 High Impact Bugs found. Low impact bugs arises from UI, high impact Bugs comprises of our input validation issues. | |||
There is no planned and actual testing done in this iteration. | |||
2 High Impact Bugs and 12 Low Impact Bugs found from testing of new Functions as well as regression testing. | |||
End of project. |
Project Risk
# | Risk Type | Risk Event | Likelihood | Impact | Category | Mitigation |
---|---|---|---|---|---|---|
1 | Client Management | Client is unable to give us the relevant data for us, causing a delay in our project schedule. | Medium | Medium | B | We will try to make do with sample data first, so that as soon as we get the relevant data from our client, we can integrate into our system straightaway. |
2 | Client Management Risk | Client has not fully decided upon the range of functions in her application as she is new to a e-commerce web application; may eventually lead to big scope changes. | Medium | Medium | B | Regularly update our client on our current progress and ask for incremental feedbacks. |
3 | Client Management Risk | Client has not host an e-commerce or a website before and is not IT savy, she may experience some difficulty with using our system. | Medium | Medium | B | We try to maintain simplicity in our design but we might compile a user guide for her future reference. |
4 | Human Risk | Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. | Medium | Medium | B | If time permits and it is a small task, shift the subtask to another iteration. Else, code sharing session and another coder will take over. |
Change Management
Importance | Decision | Action |
---|---|---|
0 | Reject | Reject the change, inform client |
1 | Low | Functions can be added should we have extra buffer time |
2 | Medium | May need to rescope the project and remove some planned functions, inform client |
3 | High | Reschedule tasks to include new function in next Iteration. |
Iteration | Requested On | Change Description | Reason of Change | Change Feasibility | Priority Level | Accepted/Rejected | Status |
---|---|---|---|---|---|---|---|
5 | 15 January 2015 | Add auto print shipping addresses label into the scope | To reduce manual work by client to print one-by-one |
|
3 | Accepted | Not completed |
5 | 15 January 2015 | Tracking coupons click and popularity | It is a useful feature for our client to carry out future campaigns. |
|
3 | Accepted | Not completed |
Technical Complexity
Quality of Product
Stage | Specification | Date |
---|---|---|
Project Management | Minutes | Meeting Minutes |
Project Management | Metrics | Task & Bug Metrics |
Project Overview | Schedule | Project Schedule |
Testing | User Test | User Testing |
Reflections
“I learnt that we must always have contingency plans, for not everything will be as smooth as planned”. - Shuwen
“I learnt that IS480 helped me go out and discover things I don’t know I don’t know” – Xiao Xin
“I learnt to control the things we cannot don’t know, by knowing to work on the hard-part (i.e. what if client don’t response)” – Wu Di
“I learnt that sometimes Client may not know what they really want, and hence, we have to take initiative to talk to the end-users” – Yu Jie