Difference between revisions of "IS480 Team wiki: 2015T1 Codex Midterm Wiki"
Jump to navigation
Jump to search
Currently At: Iteration 7
(6 intermediate revisions by the same user not shown) | |||
Line 54: | Line 54: | ||
<br> | <br> | ||
Deployed link : http://crystalnatural.com.sg/ <br> | Deployed link : http://crystalnatural.com.sg/ <br> | ||
+ | [[Media:Codex_Acceptance.pdf|Acceptance Slides]]<br> | ||
+ | |||
<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Highlights</font></div> | <div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Highlights</font></div> | ||
* Our project has 11 iteration. <br> | * Our project has 11 iteration. <br> | ||
Line 179: | Line 181: | ||
[[Image: Codex_Bug_Metric.png|700px|center]]<br> | [[Image: Codex_Bug_Metric.png|700px|center]]<br> | ||
+ | |||
+ | {| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; background-color:#FFFFFF;" | ||
+ | |- | ||
+ | ! style="color:white; background-color:#45812B; width:50px" | Iteration | ||
+ | ! style="color:white; background-color:#45812B; width:80px" | Bug Score | ||
+ | ! style="color:white; background-color:#45812B; width:200px" | Summary of Bugs | ||
+ | ! style="color:white; background-color:#45812B; width:200px" | Action Taken | ||
+ | |- | ||
+ | | <center>1</center> | ||
+ | | <center>0</center> | ||
+ | | There is no planned and actual testing done. We decided to focus on Acceptance development. | ||
+ | | <center>No action taken.</center> | ||
+ | |- | ||
+ | | <center>2</center> | ||
+ | | <center>0</center> | ||
+ | | There is no planned and actual testing done. We decided to focus on Acceptance development. | ||
+ | | <center>No action taken.</center> | ||
+ | |- | ||
+ | | <center>3</center> | ||
+ | | <center>37</center> | ||
+ | | 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. | ||
+ | | <center>Coders stopped all current development and resolve the bugs.</center> | ||
+ | |- | ||
+ | | <center>4</center> | ||
+ | | <center>10</center> | ||
+ | | 2 high impact bugs due to unable to process adding and editing of product should an unacceptable input be keyed in. | ||
+ | | <center>Coders stopped all current development and resolve the bugs.</center> | ||
+ | |- | ||
+ | | <center>5</center> | ||
+ | | <center>6</center> | ||
+ | | 1 high impact bugs and 1 low impact bug found in Order and Inventory Management Module, mainly from View Order History Page. | ||
+ | | <center> Developers to use planned debugging time in the iteration to solve the bug.</center> | ||
+ | |- | ||
+ | | <center>6</center> | ||
+ | | <center>0</center> | ||
+ | | There is no planned and actual testing done in this iteration. | ||
+ | | <center>No action taken.</center> | ||
+ | |- | ||
+ | | <center>7</center> | ||
+ | | <center>13</center> | ||
+ | | 2 High Impact Bugs from session and redirecting problems. 3 low impact errors discovered during our UAT. | ||
+ | | <center>Coders stopped all current development and resolve the bugs.</center> | ||
+ | |- | ||
+ | |} | ||
<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Risk</font></div> | <div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Risk</font></div> | ||
Line 191: | Line 237: | ||
! style="font-weight: bold;background: #45812B;color:#fff;" | Category | ! style="font-weight: bold;background: #45812B;color:#fff;" | Category | ||
! style="font-weight: bold;background: #45812B;color:#fff;" | Mitigation | ! style="font-weight: bold;background: #45812B;color:#fff;" | Mitigation | ||
+ | |||
|- | |- | ||
| 1 | | 1 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| Client Management | | Client Management | ||
| Client is unable to give us the relevant data for us, causing a delay in our project schedule. | | Client is unable to give us the relevant data for us, causing a delay in our project schedule. | ||
Line 216: | Line 247: | ||
| 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. | | 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 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. | | 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. | ||
Line 222: | Line 253: | ||
| Medium | | Medium | ||
| B | | B | ||
− | | | + | | Regularly update our client on our current progress and ask for incremental feedbacks. |
|- | |- | ||
− | | | + | | 3 |
| Client Management Risk | | 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. | | 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. | ||
Line 232: | Line 263: | ||
| We try to maintain simplicity in our design but we might compile a user guide for her future reference. | | We try to maintain simplicity in our design but we might compile a user guide for her future reference. | ||
|- | |- | ||
− | | | + | | 4 |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| 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. | ||
Line 296: | Line 319: | ||
*Batch the group of shipping based on shipping date to print out | *Batch the group of shipping based on shipping date to print out | ||
* Extra interfaces to cater to this function | * Extra interfaces to cater to this function | ||
− | |||
|3 | |3 | ||
|Accepted | |Accepted | ||
Line 306: | Line 328: | ||
|It is a useful feature for our client to carry out future campaigns. | |It is a useful feature for our client to carry out future campaigns. | ||
| | | | ||
− | * Google | + | * Google Analytics |
* Removal of Product comparison function and concentrate on analytics | * Removal of Product comparison function and concentrate on analytics | ||
|3 | |3 | ||
Line 318: | Line 340: | ||
<b> Paypal Function </b> | <b> Paypal Function </b> | ||
− | [[File:Codex_paypal.png| | + | [[File:Codex_paypal.png|500px]] |
+ | |||
+ | <b> Coupon Function </b> | ||
+ | [[File:Codex_Coupon.png|500px]] | ||
<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Quality of Product</font></div> | <div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Quality of Product</font></div> |
Latest revision as of 15:05, 19 February 2016
Deployed link : http://crystalnatural.com.sg/
Acceptance Slides
Project Highlights
- Our project has 11 iteration.
- As of 18 Feb 2016, we have completed 67.9% of our development.
- We have conducted 1 user testing before mid terms, which consist of 6 customers of our client.
- There was no major changes in requirements throughout this period.
- 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.
- The team is confident of completing the project and delivering 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% except for "Print label address for shipping" | 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 | 0.9 | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Cross Marketing Management Module | Not Completed | N.A | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Sales Performance Management Module | Not Completed | N.A | Yu Jie(Front End), Wu Di & Xiao Xin (Back End) |
Project Schedule
Planned Schedule
Actual Schedule
Notes:
- 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.
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. |
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. | Low | Medium | C | 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