Difference between revisions of "IS480 Team wiki: 2012T2 Team Chm MidTerm Wiki"
(80 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
+ | __NOTOC__ | ||
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
|scope="row" width="1200" style="text-align: center; background: #000000"| | |scope="row" width="1200" style="text-align: center; background: #000000"| | ||
Line 4: | Line 5: | ||
|} | |} | ||
− | <big><p style="text-align: left; font-size: 150%;">[[IS480_Team_wiki:_2012T2_Team_Chm| <font color=#000000" | + | <big><p style="text-align: left; font-size: 150%;"><center> |
+ | [[IS480_Team_wiki:_2012T2_Team_Chm|<font color="#000000" face=""><ins>''' MAIN WIKI'''</ins></font>]] | ||
+ | | ||
+ | [[IS480_Team_wiki:_2012T2_Team_Chm_Final_Wiki|<font color="#000000" face=""><ins>''' FINAL WIKI'''</ins></font>]] | ||
+ | </center></p></big><br> | ||
[[Image:CHM1.png|580px|right]] | [[Image:CHM1.png|580px|right]] | ||
== Project Progress Summary == | == Project Progress Summary == | ||
− | Presentation Slides | + | '''[https://www.dropbox.com/s/3oo5fypw91m5b6l/TeamChmMidtermPresentation.pdf Presentation Slides]'''<br> |
+ | '''[http://mobisupermarket.com/bonx Mobisupermarket Frontend Deployment Environment]''' | ||
=== Overview === | === Overview === | ||
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
Line 20: | Line 26: | ||
*Manage Insights - Based on Transaction Data | *Manage Insights - Based on Transaction Data | ||
*Completed 2 usability test and are currently implementing solutions to given feedback | *Completed 2 usability test and are currently implementing solutions to given feedback | ||
− | + | <br> | |
Team Chm is confident of completing the project within the stipulated schedule as shown below: | Team Chm is confident of completing the project within the stipulated schedule as shown below: | ||
|} | |} | ||
− | [[Image: | + | <center>[[Image:ChmSchedule6.png|1000px]]</center> |
=== Project Highlights === | === Project Highlights === | ||
Line 33: | Line 39: | ||
! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">HIGHLIGHT / ISSUE</font> | ! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">HIGHLIGHT / ISSUE</font> | ||
|- | |- | ||
− | ! scope="row" style="background: #C0C0C0"| '''Sprint 2''' | + | ! scope="row" style="background: #C0C0C0"| '''Sprint 2 <br/>20 Nov 2012 <br/>-<br/> 04 Dec 2012''' |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | ''' | + | '''Incorrect commits to the repository altered files that were meant to be machine-specific ''' <br /><br /> |
+ | It was not only impractical to commit the entire working folder to our repository because it amounted to 109 megabytes, but also because certain files that resided in the working folder were machine-specific. Minimal documentation by Magento exacerbated the problem and hence the eventual solution only came about with advice from various tech sites (stackoverflow, roseindia, tech blogs) after 2 weeks of trial and error. | ||
+ | |||
Due to the integration with Magento and its database, the team had some problems committing and updating the project repository. Hence, the project wasn't able to continue and development had to be put on hold so as to address the project repository issue. The issue was then solved, and only certain major files were committed. The new risk and the risk mitigation plan was then recorded so as to prevent such problems from happening again.<br /> | Due to the integration with Magento and its database, the team had some problems committing and updating the project repository. Hence, the project wasn't able to continue and development had to be put on hold so as to address the project repository issue. The issue was then solved, and only certain major files were committed. The new risk and the risk mitigation plan was then recorded so as to prevent such problems from happening again.<br /> | ||
|- | |- | ||
Line 41: | Line 49: | ||
! scope="row" style="background: #C0C0C0"| '''Sprint 5''' | ! scope="row" style="background: #C0C0C0"| '''Sprint 5''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | ''' No transactional data for | + | ''' No transactional data for Insights ''' <br /><br /> |
− | + | In the course of developing our BI tool during Sprint 5, the team was advised by our supervisor that we do not have any meaningful transactional data in our project. Hence, upon discussion with our sponsor, the team and the sponsor decided to to have a data gathering cum user testing session. Over 30 friends were invited so shop online using Magento E-commerce website, and they were each given $1000 virtual money to spend. | |
|- | |- | ||
! scope="row" style="background: #C0C0C0"| '''Sprint 7''' | ! scope="row" style="background: #C0C0C0"| '''Sprint 7''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | '''No | + | '''No realistic data in our project'''<br /><br /> |
− | + | As the project progressed, the team was advised by our supervisor to try to make the spending behaviour slightly more genuine by means of incorporating real products that existed into the platform's catalog of products, which would in turn be more realistic during our User Tests. This rang true amongst the team because the products in the default catalog provided by Magento was either outdated or fictitious. Thus, both the sponsor and the team has been on the search for the products and their products' description to be input into our catalog. The team found the [http://helloyellowmushmellow.tumblr.com Yellow Mushmellow] online blogshop, and the owner was willing to allow her products to be input into our catalog. | |
|} | |} | ||
=== Technical Complexity === | === Technical Complexity === | ||
− | The technical | + | The technical complexities of our tools employed are in the following descending order: <br /> |
{| class="wikitable" style="text-align: center; height:100px" | {| class="wikitable" style="text-align: center; height:100px" | ||
Line 61: | Line 69: | ||
! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">DESCRIPTION</font> | ! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">DESCRIPTION</font> | ||
|- | |- | ||
− | ! scope="row" style="background: #C0C0C0"| '''Magento | + | ! scope="row" style="background: #C0C0C0"| '''Magento Community Edition''' |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | *'''What | + | *'''What is it?''' |
− | :*Open source | + | :*Open source e-commerce framework |
*'''What was complex?''' | *'''What was complex?''' | ||
− | :*Complex | + | :*Complex directory Structure |
+ | :*Based on the Zend Framework | ||
:*Complex database structure - EAV | :*Complex database structure - EAV | ||
::* Click [https://wiki.smu.edu.sg/w/is480/images/9/90/Magentodatabase2.png here] for Magento ER diagram | ::* Click [https://wiki.smu.edu.sg/w/is480/images/9/90/Magentodatabase2.png here] for Magento ER diagram | ||
− | *''' | + | *'''Why did we use it?''' |
+ | :*Client requirement — "Magento is very powerful because it gives very granular control of its features, thus making it extensible and scalable for future development." | ||
:*From our data generation sessions, feedback was given that it was easy to use and navigate | :*From our data generation sessions, feedback was given that it was easy to use and navigate | ||
− | |||
|- | |- | ||
− | ! scope="row" style="background: #C0C0C0"| '''D3.js <br> | + | ! scope="row" style="background: #C0C0C0"| '''D3.js <br> Data Manipulation Framework''' |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | *'''What | + | *'''What is it?''' |
:*D3.js is a JavaScript library for manipulating documents based on data | :*D3.js is a JavaScript library for manipulating documents based on data | ||
*'''What was complex?''' | *'''What was complex?''' | ||
:*Challenging process of making use of the D3.js API to manipulate data generated from Magento E-commerce website | :*Challenging process of making use of the D3.js API to manipulate data generated from Magento E-commerce website | ||
− | *''' | + | *'''Why did we use it?''' |
:*Javascript library for building interactive, beautiful and custom data driven charts | :*Javascript library for building interactive, beautiful and custom data driven charts | ||
|- | |- | ||
+ | |||
+ | ! scope="row" style="background: #C0C0C0"| '''jQuery UI<br> Framework''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''What is it?''' | ||
+ | :*jQuery UI is a JavaScript library that provides abstractions for low-level interaction and animation, advanced effects and high-level, themeable widgets, built on top of the jQuery JavaScript library, that can be used to build interactive web applications. | ||
+ | *'''What was complex?''' | ||
+ | :*Challenging process of implementing the jQuery library and aligning it to the client's requirements | ||
+ | *'''Why did we use it?''' | ||
+ | :*jQueryUI is a mature and reliable framework. There is an active community supporting it and plenty of information is available on blog spots and discussion forums. | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background: #C0C0C0"| '''Foundation Framework<br/>by ZURB ''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''What is it?''' | ||
+ | :*ZURB Foundation is a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation and other interface components, as well as optional JavaScript extensions | ||
+ | *'''What was complex?''' | ||
+ | :*Process of learning, downloading and implementing the foundation framework library and aligning it to our project. | ||
+ | *'''Why did we use it?''' | ||
+ | :*Foundation is known to be the most advanced responsive front-end framework in the world. Foundation is developed in Sass, which is powerful CSS pre-processor that helps users to write cleaner, more organized, CSS that users can easily maintain over time. On top of the minimal styling, Foundation has also written powerful Javascript plugins that will make useful interactions easier to implement across screen sizes. | ||
+ | |- | ||
+ | |||
|} | |} | ||
Line 104: | Line 134: | ||
! scope="row" style="background-color:#C0C0C0"|Manage Campaign | ! scope="row" style="background-color:#C0C0C0"|Manage Campaign | ||
− | |style="text-align: center;"|100% developed | + | |style="text-align: center;"|100% developed and deployed |
|style="text-align: center;"|1 | |style="text-align: center;"|1 | ||
|style="text-align: center;"|Leonard | |style="text-align: center;"|Leonard | ||
Line 110: | Line 140: | ||
! scope="row" style="background-color:#C0C0C0"|Manage Hooks - Coupons | ! scope="row" style="background-color:#C0C0C0"|Manage Hooks - Coupons | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"|100% developed and deployed |
|style="text-align: center;"|1 | |style="text-align: center;"|1 | ||
|style="text-align: center;"|Rachel | |style="text-align: center;"|Rachel | ||
Line 116: | Line 146: | ||
! scope="row" style="background-color:#C0C0C0"|Manage Hooks - Social Messages | ! scope="row" style="background-color:#C0C0C0"|Manage Hooks - Social Messages | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"|0% developed |
− | |style="text-align: center;"| | + | |style="text-align: center;"|0.9 |
|style="text-align: center;"|Max | |style="text-align: center;"|Max | ||
|- | |- | ||
Line 128: | Line 158: | ||
! scope="row" style="background-color:#C0C0C0"|Manage Insights | ! scope="row" style="background-color:#C0C0C0"|Manage Insights | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"|20% developed |
|style="text-align: center;"|0.9 | |style="text-align: center;"|0.9 | ||
|style="text-align: center;"|Max | |style="text-align: center;"|Max | ||
Line 136: | Line 166: | ||
=== Project Scope === | === Project Scope === | ||
− | [[Image: | + | [[Image:Corefunctions3.jpg|500px|Project Use Cases|thumb|left]] |
<br /><br /><br /><br /> | <br /><br /><br /><br /> | ||
{| class="wikitable" style="text-align: center; height:50px" | {| class="wikitable" style="text-align: center; height:50px" | ||
|+ | |+ | ||
|- | |- | ||
− | ! scope="row" width="800" style="text-align: left; background: #F5F5F5"| | + | ! scope="row" width="800" style="text-align: left; background: #F5F5F5; font-weight:normal;padding:4px 4px 4px 4px"| |
'''Project scope has not changed since inception''' | '''Project scope has not changed since inception''' | ||
:*Chapters are categorized in priority circles: | :*Chapters are categorized in priority circles: | ||
Line 153: | Line 183: | ||
<br /><br /> | <br /><br /> | ||
− | === Schedule (Planned vs | + | === Schedule (Planned vs Actual) === |
− | Schedule | + | {| |
+ | |[[Image:Planned2.png|500px]] | ||
+ | |[[Image:Actual1.png|560px]] | ||
+ | |} | ||
+ | |||
+ | <br style="clear:both" /> | ||
+ | No changes to proposal and acceptance milestones; and only milestones after them have significant changes to the schedule.<br> Refer to the '''<big><big>[[IS480/2012T2_Team_Chm:_Project_Management#Schedule|current timeline]]'''</big></big> for more information. | ||
+ | <br><br> | ||
+ | '''Change #1''': '''An additional User Testing''', for data gathering needed for our BI tool has been added<br> | ||
+ | '''Change #2''': Part of the '''Manage Hook''' function has been shifted over to past mid terms<br> | ||
+ | '''Change #3''': Part of the '''Manage Insights''' has been shifted to before mid terms<br> | ||
+ | <br> | ||
=== Project Metrics === | === Project Metrics === | ||
+ | |||
==== Schedule Metric ==== | ==== Schedule Metric ==== | ||
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
|scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | |scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | ||
− | The diagram below shows the burn-down charts of the | + | The diagram below shows the burn-down charts of the 9 sprints we have completed thus far: <br /> |
'''Links'''<br> | '''Links'''<br> | ||
Line 175: | Line 217: | ||
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=21 7], | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=21 7], | ||
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=23 8], | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=23 8], | ||
− | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=24 9 | + | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=24 9] |
− | |||
<br> | <br> | ||
+ | <big><big>'''Release Burn-down Chart'''</big></big><br><br> | ||
+ | [[Image:ReleaseBurndown.png|525px]]<br /><br /> | ||
<big><big>'''Burn-down Charts'''</big></big><br><br> | <big><big>'''Burn-down Charts'''</big></big><br><br> | ||
− | [[Image:Burndownchart1.png|525px]][[Image:Burndownchart2.png|525px]] | + | [[Image:Burndownchart1.png|525px]] |
+ | [[Image:Burndownchart2.png|525px]] | ||
+ | [[Image:Sprint91.png|255px]] | ||
<br><br> | <br><br> | ||
Line 192: | Line 237: | ||
|- | |- | ||
! scope="row" width="600" style="text-align: center; background: #F5F5F5"|'''Number of Bugs Found'''<br> | ! scope="row" width="600" style="text-align: center; background: #F5F5F5"|'''Number of Bugs Found'''<br> | ||
− | There was a | + | There was a spike in the number of bugs found in Sprint 9. This is due to the more rigorous testing conducted on our application during User Testing 2. <br><br> |
− | Also, there are six bugs that are carried over from Sprint 9 to 10 because we did not | + | Also, there are six bugs that are carried over from Sprint 9 to 10 because we did not manage to resolve them in time. |
|} | |} | ||
<br> | <br> | ||
Line 221: | Line 266: | ||
|- | |- | ||
| 5. | | 5. | ||
− | | | + | | Getting meaningful and realistic testers |
− | | | + | | In order for the project to realize its full potential, there is a need for professional feedback |
− | | <center> | + | | <center>7</center> |
− | | Project Manager to | + | | Project Manager in talks with sponsor to organise a UAT session with MITB students. |
|- | |- | ||
| 6. | | 6. | ||
− | | | + | | Rate of development is decreasing |
− | | Project | + | | Project would take a longer time to complete |
| <center>5</center> | | <center>5</center> | ||
− | | | + | | Project Manager to plan and pre-empt the team of the tasks coming up in the following sprint and to encourage team mates to start studying earlier. |
+ | |||
+ | |||
|- | |- | ||
Line 276: | Line 323: | ||
|style="text-align: center;"|Use Case | |style="text-align: center;"|Use Case | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | *[https:// | + | *[https://wiki.smu.edu.sg/w/is480/images/8/8f/Consumer_Use_Case.PNG Consumer Use Case] |
+ | *[https://wiki.smu.edu.sg/w/is480/images/3/34/Marketing_Professional_Use_Case_2.png Marketing Professional Use Case] | ||
|- | |- | ||
Line 300: | Line 348: | ||
*'''Web Links''': | *'''Web Links''': | ||
− | :#'''[http://mobisupermarket/ | + | :#'''[http://mobisupermarket.com/bonx Mobisupermarket Frontend Deployment Environment]''' |
− | :#'''[http://mobisupermarket/ | + | :#'''[http://mobisupermarket.com/magento Mobisupermarket Frontend Staging Environment]''' |
:#'''[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#Server_Architecture_.26_Resources Server Architecture & Resources]''' | :#'''[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#Server_Architecture_.26_Resources Server Architecture & Resources]''' | ||
Line 376: | Line 424: | ||
====Conducted Session ==== | ====Conducted Session ==== | ||
− | + | User Testing 1 consisted of 2 sessions was successfully conducted on <b>23 & 24 Jan 2013, 1 – 3pm at the School of Economics SR 5.1 & SR 2.3 respectively.</b><br> | |
A total of <b>30 students</b> from the various schools in SMU assumed the role of a online shopper participated.<br><br> | A total of <b>30 students</b> from the various schools in SMU assumed the role of a online shopper participated.<br><br> | ||
Line 388: | Line 436: | ||
Inferring from the table on the left, there was generally an overall "very good" and "good" feedback given on the easy of usability of Magento. In light of this result, our team has decided to go ahead with the use of Magento, as this E-commerce website was deemed user friendly and easy to use.<br><br> | Inferring from the table on the left, there was generally an overall "very good" and "good" feedback given on the easy of usability of Magento. In light of this result, our team has decided to go ahead with the use of Magento, as this E-commerce website was deemed user friendly and easy to use.<br><br> | ||
− | + | Another feedback given by the users was to add a required fill for the postal code upon checkout, this has since been rectified.<br><br> | |
− | Nevertheless, many users expressed that on the whole, the system is easy to use, streamlined, | + | Nevertheless, many users expressed that on the whole, the system is easy to use, streamlined, “time-saving” and user-friendly. Users also mentioned that they are able to compare items easily and it was easy searching for products by category.<br><br> |
|} | |} | ||
<br><br> | <br><br> | ||
Line 396: | Line 444: | ||
<br> | <br> | ||
− | === User Testing 2 | + | === User Testing 2 === |
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
|scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | |scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | ||
Line 507: | Line 555: | ||
==== Conducted Session ==== | ==== Conducted Session ==== | ||
− | The | + | The User Testing 2 session was successfully conducted on <b>15 Feb 2013, 1 – 4pm at the School of Economics SR 2.5.</b> <br> |
A total of <b>17 marketing major students</b> from Professor Willem Smit class in SMU assumed the role of a marketing professional participated.<br> | A total of <b>17 marketing major students</b> from Professor Willem Smit class in SMU assumed the role of a marketing professional participated.<br> | ||
A total of <b> 30 students</b> from the various schools in SMU assumed the role of a online shopper participated across the week when the campaign was created | A total of <b> 30 students</b> from the various schools in SMU assumed the role of a online shopper participated across the week when the campaign was created | ||
Line 565: | Line 613: | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Max'''<br> | '''Max'''<br> | ||
− | * | + | *I have concluded that caffeine is a placebo effect to me. |
|style="background: #000000"|[[Image:rachel.png|120px]] | |style="background: #000000"|[[Image:rachel.png|120px]] | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Rachel'''<br> | '''Rachel'''<br> | ||
− | * | + | *Huge amount of efforts are needed to make an application user friendly |
+ | |||
|- | |- | ||
Latest revision as of 17:55, 16 April 2013
MID-TERM WIKI |
Project Progress Summary
Presentation Slides
Mobisupermarket Frontend Deployment Environment
Overview
Team Chm is in the midst of Sprint 10 at the moment.
|
Project Highlights
EVENT | HIGHLIGHT / ISSUE |
---|---|
Sprint 2 20 Nov 2012 - 04 Dec 2012 |
Incorrect commits to the repository altered files that were meant to be machine-specific Due to the integration with Magento and its database, the team had some problems committing and updating the project repository. Hence, the project wasn't able to continue and development had to be put on hold so as to address the project repository issue. The issue was then solved, and only certain major files were committed. The new risk and the risk mitigation plan was then recorded so as to prevent such problems from happening again. |
Sprint 5 |
No transactional data for Insights |
Sprint 7 |
No realistic data in our project |
Technical Complexity
The technical complexities of our tools employed are in the following descending order:
COMPLEXITY | DESCRIPTION |
---|---|
Magento Community Edition |
|
D3.js Data Manipulation Framework |
|
jQuery UI Framework |
|
Foundation Framework by ZURB |
|
Project Management
Project Status
Chapters | Status | Confidence Level (0-1) | Member In-Charge |
---|---|---|---|
Authentication | 100% developed and deployed | 1 | Joseph |
Manage Campaign | 100% developed and deployed | 1 | Leonard |
Manage Hooks - Coupons | 100% developed and deployed | 1 | Rachel |
Manage Hooks - Social Messages | 0% developed | 0.9 | Max |
Manage Purchases | 100% developed and deployed | 1 | Leonard & Rachel |
Manage Insights | 20% developed | 0.9 | Max |
Project Scope
Project scope has not changed since inception
|
---|
Schedule (Planned vs Actual)
No changes to proposal and acceptance milestones; and only milestones after them have significant changes to the schedule.
Refer to the current timeline for more information.
Change #1: An additional User Testing, for data gathering needed for our BI tool has been added
Change #2: Part of the Manage Hook function has been shifted over to past mid terms
Change #3: Part of the Manage Insights has been shifted to before mid terms
Project Metrics
Schedule Metric
The diagram below shows the burn-down charts of the 9 sprints we have completed thus far: Links |
Bug Metric
Number of Bugs Found There was a spike in the number of bugs found in Sprint 9. This is due to the more rigorous testing conducted on our application during User Testing 2. |
---|
Links |
---|
Risk Management
Added new Risks as at mid-term. Full entries are shown under the Project Management in the Risk Management Table.
Technical | ||||
---|---|---|---|---|
5. | Getting meaningful and realistic testers | In order for the project to realize its full potential, there is a need for professional feedback | Project Manager in talks with sponsor to organise a UAT session with MITB students. | |
6. | Rate of development is decreasing | Project would take a longer time to complete | Project Manager to plan and pre-empt the team of the tasks coming up in the following sprint and to encourage team mates to start studying earlier.
|
Product Quality
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
Analysis | Use Case | |
Design | ER Diagram | |
Testing | User Testing 2 Plan |
Deployment
- Staging & Development Environment: deployed on GoDaddy server
- Database: Magento EAV database structure
- Web Links:
User Testing 1 (Data Gathering)
Objectives
Scope of Test
Conducted SessionUser Testing 1 consisted of 2 sessions was successfully conducted on 23 & 24 Jan 2013, 1 – 3pm at the School of Economics SR 5.1 & SR 2.3 respectively. User Feedback
|
User Testing 2
Objectives
Scope of Test
Conducted SessionThe User Testing 2 session was successfully conducted on 15 Feb 2013, 1 – 4pm at the School of Economics SR 2.5.
Most Common Feedback & Rectification
|