HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T1 Codex Final Wiki""

From IS480
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 56: Line 56:
 
[[Media:Codex_Acceptance.pdf|Acceptance Slides]]<br>
 
[[Media:Codex_Acceptance.pdf|Acceptance Slides]]<br>
 
[[Media:Codex_Midterms.pdf| Mid Terms Presentation]]<br>
 
[[Media:Codex_Midterms.pdf| Mid Terms Presentation]]<br>
 +
[[Media:FYP_Codex_Final_Presentation.pdf| Final Presentation]]<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>
* As of 8 April 2016, we have completed 100% of our development, a revenue generating platform for our Client, Crystal Natural Products. <br>
+
* As of 14 April 2016, we have completed 100% of our development, a revenue generating platform for our Client, Crystal Natural Products. <br>
* As of 8 April, our project generated more than $200 SGD, with more than 20 transactions.
+
* As of 14 April, our project generated more than $793.40 SGD, with 32 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. <br>
+
* We have conducted 1 user testing before mid terms, which consist of 6 customers of our client. 2 user testing before finals.
 +
* UAT 2 comprises of 5 friends and 15 real users. <br>
 +
* UAT 3 comprises of 10 real users.<br>
 
* There was no major changes in requirements throughout this period. <br>
 
* There was no major changes in requirements throughout this period. <br>
 
*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.<br>
 
*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.<br>
Line 124: Line 127:
 
<center>[[File:Codex_timeline.png|700px]]</center><br>
 
<center>[[File:Codex_timeline.png|700px]]</center><br>
 
<br>
 
<br>
 
Notes: <br>
 
<b>General changes in schedule after mid terms </b>
 
* User Test 2 was rescheduled from iteration 7 to 8 because we decided to focus on debugging the functions after the Mid Term review.
 
* Cross Marketing Module has been renamed to as a sub task inside Customer Relationship Management Module, and rescheduled from iteration 8 to Iteration 9 as we decided to focus on debugging.
 
  
 
<br>
 
<br>
Line 146: Line 144:
 
* These changes include new sub-task (i.e. Auto printing shipping addresses for label and website clicks tracking). <br>
 
* These changes include new sub-task (i.e. Auto printing shipping addresses for label and website clicks tracking). <br>
 
* Because of these new changes, we decided to drop sub task Product Comparison and seeked our Client agreement. <br>
 
* Because of these new changes, we decided to drop sub task Product Comparison and seeked our Client agreement. <br>
 +
* User Test 2 was rescheduled from iteration 7 to 8 because we decided to focus on debugging the functions after the Mid Term review.<br>
 +
* Cross Marketing Module has been renamed to as a sub task inside Customer Relationship Management Module, and rescheduled from iteration 8 to Iteration 9 as we decided to focus on debugging.<br>
 
<br>
 
<br>
 
<b>Changes schedule & scope after mid terms</b>
 
<b>Changes schedule & scope after mid terms</b>
Line 420: Line 420:
 
<b> Paypal Function </b>
 
<b> Paypal Function </b>
 
[[File:Codex_paypal.png|500px]]
 
[[File:Codex_paypal.png|500px]]
 
<b> Coupon Function </b>
 
[[File:Codex_Coupon.png|500px]]
 
  
 
<b> Compatibility with Server </b>
 
<b> Compatibility with Server </b>
 
Some function can work fine on localhost, but not on server due to web server having different setting from localhost wamp server.
 
Some function can work fine on localhost, but not on server due to web server having different setting from localhost wamp server.
 +
 +
<b> Usage of CSS, JavaScript, jQuery </b>
 +
Totally new, had to adapt to the template.
  
 
<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>
Line 466: Line 466:
 
<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>Reflections</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>Reflections</font></div>
 
<br>
 
<br>
“I learnt that we must always have contingency plans, for not everything will be as smooth as planned”. - Shuwen <br>
+
“If you fail to plan, you plan to fail. As a Project Manager, I learnt to manage Client requirements, schedule, and the team. In planning schedule and client management, <br>
 
+
I learnt that we should always have a contingency plan to  prepare for any delays or unforeseen circumstances.”. - Shuwen <br>
“I learnt that IS480 helped me go out and discover things that I dont know that i didnt know” – Xiao Xin<br>
+
<br>
 
+
“Sometimes designer and user might have different mental Module. Hence, it is important to understand what users really want <br>
“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 <br>
+
because users are ultimately the one using our system.” – Xiao Xin<br>
 
+
<br>
“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 <br>
+
“The best way to measure the success of the application is to add value to the Client’s business, and we did it!” Wu Di <br>

Latest revision as of 15:30, 14 April 2016

Codex logo.png


Codex logo.png   HOME

 

Codex aboutus.png   ABOUT US

 

Codex projectoverview.png   PROJECT OVERVIEW

 

Codex projmgt.png   PROJECT MANAGEMENT

 

Codex doc.png   DOCUMENTATION


 


Deployed link : http://crystalnatural.com.sg/
Acceptance Slides
Mid Terms Presentation
Final Presentation

Project Highlights
  • Our project has 11 iteration.
  • As of 14 April 2016, we have completed 100% of our development, a revenue generating platform for our Client, Crystal Natural Products.
  • As of 14 April, our project generated more than $793.40 SGD, with 32 transactions.
  • We have conducted 1 user testing before mid terms, which consist of 6 customers of our client. 2 user testing before finals.
  • UAT 2 comprises of 5 friends and 15 real users.
  • UAT 3 comprises of 10 real users.
  • 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
Codex Home.png

 

Project Management
Currently At: Iteration 11
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 and Scope

Planned Schedule

Timeline codex v2.png



Actual Schedule [Mid Terms]

Timeline codex v3.png



Actual Schedule [Finals]

Codex timeline.png





Planned Scope

Codex scope.png

 


Actual Scope

Codex scope v2.png

 


Planned vs Actual:
Changes in schedule & scope 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.
  • User Test 2 was rescheduled from iteration 7 to 8 because we decided to focus on debugging the functions after the Mid Term review.
  • Cross Marketing Module has been renamed to as a sub task inside Customer Relationship Management Module, and rescheduled from iteration 8 to Iteration 9 as we decided to focus on debugging.


Changes schedule & scope 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


Codex Final Task Metrics.png


Iteration Period Task Metric Score Actions
1
4 October 2015 - 13 Oct 2015
100%
As planned.
2
13 Oct 2015 - 26 Oct 2015
100%
As planned.
3
26 Oct 2015 - 12 Nov 2015
92.30%
A part of Order Management - Payment Process - Paypal function was delayed and moved to Iteration 7 because our coder used the time to do bugs squashing for User Management until it was at an acceptable bug score instead.
4
12 Nov 2015 - 4 Dec 2015
100%
As planned.
5
4 Dec 2015 - 20 Jan 2016
93.75%
Human risk happened. Team member has to go back to china earlier than planned, hence, we decided to move the Inventory Management - Low Stock Warning to Iteration 7
6
20 Jan 2016 - 10 Feb 2016
100%
As planned.
7
10 Feb 2016 - 28 Feb 2016
100%
As planned.
8
29 Feb 2016 - 9 Mar 2016
87.50%
UAT2 was delayed and pushed to Iteration 9, as Client delayed giving us the real product photos for the actual UAT2.
9
10 Mar 2016 - 24 Mar 2016
100%
As planned.
10
25 Mar 2016 - 8 April 2016
100%
As planned.
11
8 April 2016 - 14 April 2016
100%
As planned.


Codex Final Bug Metrics.png


Iteration Bug Score Summary of Bugs Action Taken
1
0
There is no planned and actual testing done. We decided to focus on Acceptance development.
No action taken.
2
0
There is no planned and actual testing done. We decided to focus on Acceptance development.
No action taken.
3
37
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.
Coders stopped all current development and resolve the bugs.
4
10
2 high impact bugs due to unable to process adding and editing of product should an unacceptable input be keyed in.
Coders stopped all current development and resolve the bugs.
5
6
1 high impact bugs and 1 low impact bug found in Order and Inventory Management Module, mainly from View Order History Page.
Developers to use planned debugging time in the iteration to solve the bug.
6
0
There is no planned and actual testing done in this iteration.
No action taken.
7
13
2 High Impact Bugs from session and redirecting problems. 3 low impact errors discovered during our UAT.
Coders stopped all current development and resolve the bugs.
8
17
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.
Coders stopped all current development and resolve the bugs.
9
0
There is no planned and actual testing done in this iteration.
No action taken.
10
22
2 High Impact Bugs and 12 Low Impact Bugs found from testing of new Functions as well as regression testing.
Coders stopped all current development and resolve the bugs.
11
0
End of project.
No action taken.
Project Risk
# Risk Type Risk Event Likelihood Impact Category Mitigation
1 Technical Risk Web Server incompatible with localhost wamp server may cause ocassional problems that cause our web application to run properly on localhost but not on the server Medium Medium B Contact the server for technical support. Else change the code and switch to another algorithm.
2 Client Management Risk Client is unable to give us the relevant data for us, causing a delay in our project schedule. Medium Medium B Use pseudo data and update immediately once client give us the data.
3 Client Management Risk Client is unable to help us get real users for UAT Medium Medium B We will go to approach other Shop Owners.
4 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.
5 Human Risk Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. Medium Medium B Regular 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
  • Batch the group of shipping based on shipping date to print out
  • Extra interfaces to cater to this function
3 Accepted Completed
5 15 January 2015 Tracking coupons popularity It is a useful feature for our client to carry out future campaigns.
  • Google Analytics
  • Removal of Product comparison function and concentrate on analytics
3 Accepted Completed
7 25 February 2015 Drop Sales Performance Module, and renamed it to Coupon Analytics Module, keeping only the coupon related sub-functions. We decided to focus on improving the quality of our basic functions and hence discussed with the Client to drop these functions.
  • Approved by supervisor and client
3 Accepted Completed


Technical Complexity

Paypal Function Codex paypal.png

Compatibility with Server Some function can work fine on localhost, but not on server due to web server having different setting from localhost wamp server.

Usage of CSS, JavaScript, jQuery Totally new, had to adapt to the template.

Quality of Product
Stage Specification Link
Project Management Minutes Meeting Minutes
Project Management Metrics Task & Bug Metrics
Project Overview Schedule Project Schedule
Testing User Test User Testing
Diagram Diagrams Use Case and System Architecture
Reflections


“If you fail to plan, you plan to fail. As a Project Manager, I learnt to manage Client requirements, schedule, and the team. In planning schedule and client management,
I learnt that we should always have a contingency plan to prepare for any delays or unforeseen circumstances.”. - Shuwen

“Sometimes designer and user might have different mental Module. Hence, it is important to understand what users really want
because users are ultimately the one using our system.” – Xiao Xin

“The best way to measure the success of the application is to add value to the Client’s business, and we did it!” – Wu Di