HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
(Created page with "<!--Logo--> 150px|center<br> <!--/Logo--> <!--Header--> {|style="background-color:#A6CE39; color:#F5F5F5; padding: 10 0 10 0;" width="100%" cellspacin...")
 
Line 58: Line 58:
 
<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 18 Feb 2016, we have completed 67.9% of our development. <br>
+
* As of 8 April 2016, we have completed 100% of our development. <br>
* We have conducted 1 user testing before mid terms, which consist of 6 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, which consist of 10 customers of our client. <br>
 
* There was no major changes in requirements throughout this period. <br>
 
* There was no major changes in requirements throughout this period. <br>
* 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.<br>
+
* Some major changes in schedule involves the change of the scope of our project.<br>
* In addition, we decided to combine the planned iteration 5 and 6 together into one iteration in the midst of our development. <br>
+
* Changes in scope includes scraping away sub functions - tracking of website clicking, viewing outlet with google map<br>
* 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. <br>
+
* We decided to scrap away to focus on improving the quality our core functions. <br>
 
* 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>
+
* This decision is supported by both our Client and our Supervisor. <br>
 
<br>
 
<br>
 
* The team is confident of completing the project and delivering the application on time.
 
* The team is confident of completing the project and delivering the application on time.

Revision as of 10:37, 6 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

Project Highlights
  • Our project has 11 iteration.
  • As of 8 April 2016, we have completed 100% of our development.
  • 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.
  • Some major changes in schedule involves the change of the scope of our project.
  • Changes in scope includes scraping away sub functions - tracking of website clicking, viewing outlet with google map
  • We decided to scrap away to focus on improving the quality our core functions.
  • These changes include new sub-task (i.e. Auto printing shipping addresses for label and website clicks tracking).
  • This decision is supported by both our Client and our Supervisor.


  • The team is confident of completing the project and delivering the application on time.


Project Summary
Codex Home.png

 

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

Timeline codex v2.png



Actual Schedule

Timeline codex v3.png



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


Codex 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.


Codex Bug Metric.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.
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
  • Batch the group of shipping based on shipping date to print out
  • Extra interfaces to cater to this function
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.
  • Google Analytics
  • Removal of Product comparison function and concentrate on analytics
3 Accepted Not completed


Technical Complexity

Paypal Function Codex paypal.png

Coupon Function Codex Coupon.png

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