HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 DR.Jean Labs The Team Final Wiki"

From IS480
Jump to navigation Jump to search
 
(42 intermediate revisions by 2 users not shown)
Line 48: Line 48:
 
|}
 
|}
 
<br>
 
<br>
 +
<br />
 +
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 +
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - -  - - - - - - -
 +
<!--Sub Sub-Navigation-->
 +
{| style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" |
 +
 +
| style="padding:0 .3em;  font-size:150%; solid #000000; text-align:center; background-color:white; " width="20%" |  <font face = "Arial" color="red" size = "-1"><b><< Project Summary >></b></font>
 +
 +
| style="padding:0 .3em;  font-size:150%; solid #000000; text-align:center; background-color:white; " width="20%" | [[IS480_Team_wiki:_2013T2 DR.Jean Labs_Final Project Management| <font face = "Arial" color="#101010" size = "-1"><b><< Project Management >></b></font>]]
 +
 +
| style="padding:0 .3em;  font-size:150%; solid #000000; text-align:center; background-color:white; " width="20%" |  [[IS480_Team_wiki:_2013T2 DR.Jean Labs_The Team_Final Quality of the Product| <font face = "Arial" color="#101010" size = "-1"><b><< Quality of the Product >></b></font>]]
 +
 +
| style="padding:0 .3em;  font-size:150%; solid #000000; text-align:center; background-color:white; " width="20%" |  [[IS480_Team_wiki:_2013T2 DR.Jean Labs_The Team_Final Reflections| <font face = "Arial" color="#101010" size = "-1"><b><< Our Reflections >></b></font>]]
 +
 +
|}
 +
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - -  - - - - - - -  
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - -  - - - - - - -  
  
 
<!-- content -->
 
<!-- content -->
[[Image:Dr.JeanLabs Final StoryBoard.png|center|900px ]]
 
  
==Project Progress Summary==
+
==<div style="background: #000; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.1em;font-size:24px"><font color=#176596>Project </font><font color= #FFF>Summary</font></div>==
 +
 
 +
[[Image:Dr.JeanLabs Final StoryBoard.png|center|900px ]] <br />
 +
 
 +
 
 +
[[Image:Photo 2014-04-23 10-01-27 edited.jpg|center|900px]]
  
 
=== Closed Beta Launch ===
 
=== Closed Beta Launch ===
Line 63: Line 83:
 
Beta released app test link <b>(User)</b>: http://test.sqkii.com/ <br />
 
Beta released app test link <b>(User)</b>: http://test.sqkii.com/ <br />
 
Beta released app test link <b>(Advertiser</b>): http://test.sqkii.com/adv <br />
 
Beta released app test link <b>(Advertiser</b>): http://test.sqkii.com/adv <br />
 
 
  
 
<!--
 
<!--
Line 77: Line 95:
 
|-
 
|-
 
|colspan = "2" align = "center"|Advertiser test account  
 
|colspan = "2" align = "center"|Advertiser test account  
<b>http://test.sqkii.com/</b>
+
<b>http://test.sqkii.com/adv</b>
  
 
|-
 
|-
Line 85: Line 103:
 
|-
 
|-
 
|benjamin@gmail.com
 
|benjamin@gmail.com
|123123
+
|adv123
  
 
|-
 
|-
 
|alan@gmail.com
 
|alan@gmail.com
|123123
+
|adv123
 
 
|-
 
|david@gmail.com
 
|123123
 
  
 
|}
 
|}
  
-->
+
{| class="wikitable"
  
Download our MidTerm Slides [ here!]
 
Place your Final slides link and deployed site link here
 
 
===Project Highlights:===
 
 
What unexpected events occurred and how were they handled?
 
*A team member left the project and dropped the course
 
*List of requirement changes
 
** CRUD items replaced with CU/Sync/Archive items
 
** Business analytics replaced with iPad client
 
*Took 8 weeks to learn Ruby on Rails
 
*etc.
 
Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section
 
 
===Project Challenges:===
 
 
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
 
 
===Project Achievements:===
 
 
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
 
 
==Project Management==
 
 
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
 
 
===Project Schedule (Plan Vs Actual):===
 
 
Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
 
 
Provide a comparison of the plan and  actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
 
 
{| border="1"
 
|- style="background:blue; color:white"
 
|| Iterations
 
|colspan="2" align="center"| Planned
 
|colspan="2" align="center"| Actual
 
|| Comments
 
 
|-
 
|-
 +
|colspan = "2" align = "center"|User test account
 +
<b>http://test.sqkii.com/</b>
  
|rowspan="2"| 1
 
|| Customer CRUD
 
|| 1 Sept 2010
 
||
 
|| 25 Aug 2010
 
|| Fiona took the Sales CRUD as well.
 
 
|-
 
|-
 +
! style="background: #176596; color: white; text-align: center"; colspan= "1"; font-weight: bold| Username
 +
! style="background: #176596; color: white; text-align: center"; colspan= "1"; font-weight: bold| Password
  
|| Trend Analytic
 
|| 1 Sept 2010
 
||
 
|| 15 Sept 2010
 
|| Ben is too busy and pushed iteration 1 back
 
 
|-
 
|-
 +
|benjamin@gmail.com
 +
|ben123
  
|rowspan="2"| 2
 
|| User tutorial
 
|| 1 Oct 2010
 
|colspan="2"|
 
|| Removed proposed by Ben
 
 
|-
 
|-
 +
|alan@gmail.com
 +
|allan123
  
|colspan="2"|
 
|| Psycho analysis
 
|| 1 Oct 2010
 
|| New module proposed by sponsor
 
 
|}
 
|}
 +
-->
 +
Download our Final presentation slides [[Media:Dr.JeanLabs FinalPresentation.pdf|here]]
  
===Project Metrics:===
+
=== Project Highlights ===
  
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
+
View our past highlights in our [[IS480_Team_wiki:_2013T2 DR.Jean Labs_The Team_MidTerm Wiki| MidTerm Wiki.]]
  
===Technical Complexity:===
+
{| border="1"
  
{| border = "1"
 
 
|- style="background:black; color:white"  
 
|- style="background:black; color:white"  
| align="center"| Complexity
+
|colspan="4" align="center" |Project Management
| align="center"| Description
 
 
|-
 
|-
  
| align="center"| Jcrop + Javascript boost (Advertiser Platform)
+
|- style="background:black; color:white"
|| Image uploading is a vital function to the merchant partners of Sqkii. Thus, research has been done to find a suitable plugin to cater to the cropping of images - this is to provide a function where merchant partners are able to snap a picture of their product, and immediately crop the desired area. We decided to use jCrop, however there were many disabilities coupled with jCrop.
+
| align="center"| S/N
 +
| align="center"| Change Event
 +
| align="center"| Affected Sprint
 +
| align="center"| Change Action Description
 +
|-
  
 +
|| 1
 +
|| Remove the functions under "Receive Incentives" such as (Multiper Effect and Rating)
 +
|| 8
 +
|| Removed the Multiper effect and the Rating functions. We decided not to do the rating function as it will not provide any value added benefits to advertiser and user. User can use favourite function instead to see squibs again.
  
Firstly, it is the inability to execute the cropping on client side. Which means that there will be more work done on the server side, inducing more costs. To fix this problem, we employed HTML's canvas element. Drawing on a canvas element the desired cropped image. This shifted the work from the server side to the client side and will definitely save costs for Sqkii.
+
Team proposed this change not to biz team not to complicate things within the scope of this FYP.  
 +
|-
  
 +
|| 2
 +
|| Drop UT3 "Change of registering steps"
 +
|| 8
 +
|| As we discussed and realised that only a majority of the user that we have tested have faced the registration issue, we decided to enhance the login side by having FB login for user.
 +
|-
  
Secondly, the images uploaded unto the jCrop api does not cater to a web responsive layout. It ends up with a rigid image size that remains that size. This is fixed by using our technical expertise to manually reconfigure the uploaded image, along with the interwoven jCrop variables. This resulted in a extremely web responsive layout for the image upload function which coincides with our goal to produce a web responsive web app
+
|| 3
 +
|| Drop create new account
 +
|| 8
 +
|| There are no separate administration account for sqkii.The biz requirement is to focus on exclusivity. Therefore it requires only the users in the platform to allow to refer friends to join.
 
|-
 
|-
  
| align="center"| Pseudo Random Credit Algorithm (User Platform)
+
|| 4
|| Our users are as important as our merchant partners, and we want to make their main function at Sqkii a fun and exciting one. Thus, we felt that the mundane revenue sharing concept might not necessarily keep our users interested to keep using Sqkii. Thus, we developed a crediting algorithm that randomises the crediting, at the same time it returns back to the users exactly the amount that they are entitled to. This provides with an exciting and unique where of crediting where no user will have the same path of crediting, while actually having the same path.
+
|| Cashout Tier 3
 +
|| 9
 +
|| Team proposed to drop this function as this is only the beta launch of Sqkii. Have discussed with the Business Team.  
 
|-
 
|-
  
 
|}
 
|}
  
==Quality of product==
 
 
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
 
 
===Project Deliverables:===
 
 
List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.
 
  
 
{| border="1"
 
{| border="1"
|- style="background:blue; color:white"  
+
|- style="background:black; color:white"  
|align="center"| Stage
+
|colspan="4" align="center" |Technical
|align="center"| Specification
 
|align="center"| Modules
 
 
|-
 
|-
  
|rowspan="2"| Project Management
+
|- style="background:black; color:white"
|| Minutes
+
| align="center"| S/N
|| Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
+
| align="center"| Change Event
 +
| align="center"| Changed Date / Sprint
 +
| align="center"| Change Action Description
 
|-
 
|-
  
|| Metrics
+
|| 1
|| Bug metrics
+
|| Drop UT3 change, "Add arrow/movement of squib to show people "swiping" works"
 +
|| 28-Mar-14 / 9
 +
||
 +
Team will implement lazy load for all the squibs.
 
|-
 
|-
  
|| Requirements
+
|| 2
|| Story cards
+
|| Drop squib rank for advertiser
|| [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic]
+
|| 28-Mar-14 / 9
 +
||
 +
Team proposed to drop this function as this is only the beta launch of Sqkii and schedule is behind time.
 
|-
 
|-
  
|rowspan="4"| Analysis
+
|| 3
|| Use case
+
|| Drop enhanced contact form
|| [http://en.wikipedia.org/wiki/Use_case_diagram overall]
+
|| 31-Mar-14 / 9
|-
+
||  
 
+
Team proposed to drop because we will be seeing all feedbacks from users despite being categorized into different sections.
|| System Sequence Diagram
 
|| [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server]
 
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram]
+
|| 4
 +
|| Drop enhanced menu bar for User
 +
|| 12-Apr-14 / 9
 
||  
 
||  
 +
Team proposed to drop because we will be seeing all feedbacks from users despite being categorized into different sections.
 
|-
 
|-
  
|| Screen Shots
+
|}
|| CRUD Customer, Trend Analysis
 
|-
 
  
|rowspan="2"| Design
 
|| [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram]
 
|| 1, 2, 3
 
|-
 
  
|| [http://en.wikipedia.org/wiki/Class_diagram Class Diagram]
+
{| border="1"
|| [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3]
+
|- style="background:black; color:white"
 +
|colspan="4" align="center" |Business Requirement
 
|-
 
|-
  
 
+
|- style="background:black; color:white"
|| Testing
+
| align="center"| S/N
|| Test plan
+
| align="center"| Change Event
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
+
| align="center"| Changed Date / Sprint
 +
| align="center"| Change Action Description
 
|-
 
|-
  
|rowspan="3"| Handover
+
|| 1
|| Manuals
+
|| Added the Cash out Tier 3 for user
|| User tutorial, Developer manual, Setup manual
+
|| 8
 +
|| As one of the main core focus of the project, it is to able to allow user to cash out the cash and donate to a chartiable clause.
 
|-
 
|-
  
|| Code
+
|| 2
|| client server
+
|| Drop create new squib (admin)
 +
|| 8
 +
|| Due to the marketing strategy of the CBL, admin no longer need to create squibs for advertiser. Function is done but is not shown on the application.
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Deployment_diagram Deployment Diagram]
 
|| [[IS480_Midterm_Wiki#Deployment: | instructions]]
 
 
|}
 
|}
  
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
+
===Project Challenges:===
  
=== Quality:===
+
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
  
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
+
{| border="1"
  
===Deployment:===
+
|- style="background:black; color:white"
 +
| align="center"| S/N
 +
| align="center"| Challenge
 +
| align="center"| Consequences
 +
| align="center"| What did we do to make it better?
 +
|-
  
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a [[IS480_Final_Wiki#Project_Deliverables: | deployment diagram link]].
+
|| 1
 +
|| Feedbacks coming in from our beta users.
 +
||
 +
* Caused delays in our planned schedule
 +
* Lost some beta users.
 +
* Team have to do sufficient UT to ensure that the application is usable for the user.
 +
||
 +
* Re-iterate the schedule again to ensure that the changes that we made is still able to keep the schedule in time.
 +
* Implemented Change Management to ensure that only justifiable feedback which falls under the appropriate level we will provide after discussing with the Business Unit.
 +
* Conducted several UT with both Users and Advertisers to ensure the application is usable.
 +
|-
  
===Testing:===
+
|| 2
 +
|| Inefficient mode of communication
 +
||
 +
* Caused mis-communication between members and lack of understanding with each other.
 +
* Delay in Project Schedule.
 +
* Members are unhappy with one another.
 +
||
 +
* Tried out various communication means such as Facebook Chat, Whatsapp, Email, SMS, calling and Face-To-Face. In the end, we conclude that Facebook Chat is the most appropriate as most of them will be on laptop and easier for them to check and reply on Facebook Chat. At the same time, Function check list google docs are also in place to share with the coders to constantly keep track of the bugs that Business Unit has found online.
 +
* Happiness Metric in place to check the three areas of each member's well-being that includes (Happiness, Health & Motivation). The team will do something according to different threshold of the area if it hits below low. Sample of what we did can be found here.
  
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
+
View our past highlights in our [[IS480_Team_wiki:_2013T2 DR.Jean_Labs_Team_Lab_Photos#fun_things| Fun things that we do!]]
 +
|-
 +
|}
  
==Reflection==
+
===Project Achievements:===
 
 
Compile common lessons and reflection for the team and for each team member. Be brief.
 
 
 
===Team Reflection:===
 
 
 
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki [[Knowledge_base | knowledge base]] and linked here.
 
 
 
===Individual Reflection:===
 
 
 
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
 
  
===Sponsor Comment:===
+
* 1300 registered users, 39 advertisers and 102 highly interested to join us.
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
+
* 497 number of squibs online for viewing
 +
* Paid 102 users and 8 more pending to be paid.
 +
* Featured on [http://vulcanpost.com/5685/since-you-are-already-seeing-ads-sqkii-wants-to-pay-you-hard-cold-cash-for-it/ Vulcan] & [https://sg.news.yahoo.com/since-already-seeing-ads-skqii-023029660.html Yahoo].
 +
* Granted iJAM ($250,000) & AES ($10,000).
 +
* Conducted 4 User Test and one A|B testing experiment.

Latest revision as of 10:06, 23 April 2014

Agurz avatar.png
Denise avatar.png
Eleazar avatar.png
Dr.jeanlabs logo.jpg
Janan avatar.png
Nicholas avatar.png
Rafael avatar.png

HOME

 

DR.JEAN LABS

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

PROJECT DOCUMENTATION

 


{ In a nutshell } { Acceptance Wiki } { MidTerm Wiki } { Final Wiki }



- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

<< Project Summary >> << Project Management >> << Quality of the Product >> << Our Reflections >>

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


Project Summary

Dr.JeanLabs Final StoryBoard.png



Photo 2014-04-23 10-01-27 edited.jpg

Closed Beta Launch

Beta Launch released date: 20 Feb 2014, 1pm
Beta released app link (User): http://app.sqkii.com/
Beta released app link (Advertiser): http://app.sqkii.com/adv

Beta released app test link (User): http://test.sqkii.com/
Beta released app test link (Advertiser): http://test.sqkii.com/adv

Download our Final presentation slides here

Project Highlights

View our past highlights in our MidTerm Wiki.

Project Management
S/N Change Event Affected Sprint Change Action Description
1 Remove the functions under "Receive Incentives" such as (Multiper Effect and Rating) 8 Removed the Multiper effect and the Rating functions. We decided not to do the rating function as it will not provide any value added benefits to advertiser and user. User can use favourite function instead to see squibs again.

Team proposed this change not to biz team not to complicate things within the scope of this FYP.

2 Drop UT3 "Change of registering steps" 8 As we discussed and realised that only a majority of the user that we have tested have faced the registration issue, we decided to enhance the login side by having FB login for user.
3 Drop create new account 8 There are no separate administration account for sqkii.The biz requirement is to focus on exclusivity. Therefore it requires only the users in the platform to allow to refer friends to join.
4 Cashout Tier 3 9 Team proposed to drop this function as this is only the beta launch of Sqkii. Have discussed with the Business Team.


Technical
S/N Change Event Changed Date / Sprint Change Action Description
1 Drop UT3 change, "Add arrow/movement of squib to show people "swiping" works" 28-Mar-14 / 9

Team will implement lazy load for all the squibs.

2 Drop squib rank for advertiser 28-Mar-14 / 9

Team proposed to drop this function as this is only the beta launch of Sqkii and schedule is behind time.

3 Drop enhanced contact form 31-Mar-14 / 9

Team proposed to drop because we will be seeing all feedbacks from users despite being categorized into different sections.

4 Drop enhanced menu bar for User 12-Apr-14 / 9

Team proposed to drop because we will be seeing all feedbacks from users despite being categorized into different sections.


Business Requirement
S/N Change Event Changed Date / Sprint Change Action Description
1 Added the Cash out Tier 3 for user 8 As one of the main core focus of the project, it is to able to allow user to cash out the cash and donate to a chartiable clause.
2 Drop create new squib (admin) 8 Due to the marketing strategy of the CBL, admin no longer need to create squibs for advertiser. Function is done but is not shown on the application.

Project Challenges:

Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.

S/N Challenge Consequences What did we do to make it better?
1 Feedbacks coming in from our beta users.
  • Caused delays in our planned schedule
  • Lost some beta users.
  • Team have to do sufficient UT to ensure that the application is usable for the user.
  • Re-iterate the schedule again to ensure that the changes that we made is still able to keep the schedule in time.
  • Implemented Change Management to ensure that only justifiable feedback which falls under the appropriate level we will provide after discussing with the Business Unit.
  • Conducted several UT with both Users and Advertisers to ensure the application is usable.
2 Inefficient mode of communication
  • Caused mis-communication between members and lack of understanding with each other.
  • Delay in Project Schedule.
  • Members are unhappy with one another.
  • Tried out various communication means such as Facebook Chat, Whatsapp, Email, SMS, calling and Face-To-Face. In the end, we conclude that Facebook Chat is the most appropriate as most of them will be on laptop and easier for them to check and reply on Facebook Chat. At the same time, Function check list google docs are also in place to share with the coders to constantly keep track of the bugs that Business Unit has found online.
  • Happiness Metric in place to check the three areas of each member's well-being that includes (Happiness, Health & Motivation). The team will do something according to different threshold of the area if it hits below low. Sample of what we did can be found here.

View our past highlights in our Fun things that we do!

Project Achievements:

  • 1300 registered users, 39 advertisers and 102 highly interested to join us.
  • 497 number of squibs online for viewing
  • Paid 102 users and 8 more pending to be paid.
  • Featured on Vulcan & Yahoo.
  • Granted iJAM ($250,000) & AES ($10,000).
  • Conducted 4 User Test and one A|B testing experiment.