HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 CLEBS Finals"

From IS480
Jump to navigation Jump to search
 
(8 intermediate revisions by 2 users not shown)
Line 23: Line 23:
 
{|style=" cellspacing="20px" cellpadding="0px" align="center" valign="top"|
 
{|style=" cellspacing="20px" cellpadding="0px" align="center" valign="top"|
 
| style="font-size:85%; font-variant: small-caps; text-align:center" width="20%" border="2px solid black" |  
 
| style="font-size:85%; font-variant: small-caps; text-align:center" width="20%" border="2px solid black" |  
[[IS480 Team wiki: 2016T1 CLEBS| <font face="Century Gothic" color="#666"><b>M A I N</b></font>]]
+
[[IS480 Team wiki: 2016T1 CLEBS| <font face="Century Gothic" color="#666">M A I N</font>]]
  
 
| style="font-size:85%;  font-variant: small-caps; text-align:center " width="20%"  |  
 
| style="font-size:85%;  font-variant: small-caps; text-align:center " width="20%"  |  
[[IS480 Team wiki: 2016T1 CLEBS Mid-Term| <font face="Century Gothic" color="#666"><b>M I D - T E R M</b></font>]]
+
[[IS480 Team wiki: 2016T1 CLEBS Mid-Term| <font face="Century Gothic" color="#666">M I D - T E R M</font>]]
  
 
| style="font-size:85%; font-variant: small-caps; text-align:center " width="20%"  |
 
| style="font-size:85%; font-variant: small-caps; text-align:center " width="20%"  |
Line 33: Line 33:
 
<!-- end of sub-nav bar -->
 
<!-- end of sub-nav bar -->
  
<!-- CURRENT SPRINT INFO -->
+
<!-- start of final wiki requirements -->
<div style="background:#00beff; padding: 10px; font-weight: bold; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Calibri" color="#F7F7FF"> Current Sprint Information</font></div>
+
=Project Progress Summary=
 +
 
 +
Final Slides: <!-- Input here -->
 +
 
 +
Deployed Site Link:
 +
[[File:Ybco-web.png|frameless|center|800px|]]
 +
 
 +
Note: We have yet to publish on the existing YBCO website as the client is still looking to make changes to the business model as well as carry out testing first.
 +
 
 +
==Project Highlights==
 +
<b>What was achieved from Mid-Terms?</b>
 +
*Confirmed on our Payment Gateway Technology (PayPal)
 +
*Completion of the entire Projects Module
 +
**Project Creation Module (Iteration 5) was completed and users, after having their project proposal accepted, are able to create their projects
 +
**Project creators are now also able to edit their projects and submit their completed projects to go LIVE
 +
*Completion of Messaging Module
 +
**Users are now able to interact with one another using Facebook Messenger
 +
*En-route to achieving final X-Factor:
 +
**8 Projects Submitted
 +
**3 Projects Funded
 +
<br/>
 +
<b>What unexpected events occurred? </b>
 +
*Changes to Project Scope and Timeline
 +
**Sponsor experienced difficulty in setting up a BrainTree and Stripe account and was only given PayPal to work with (on 2nd November 2016)
 +
**Sponsor requested changes to content in home page
 +
*Changes to business model
 +
**Sponsor was contemplating changing the business model, which further affected our development
 +
 
 +
=Project Management=
 +
==Project Status==
 +
<div style="text-align: center;"><b>This was our initial planned Project Scope, before the changes:</b></div>
 +
[[File:Clebs-scope-2.png|frameless|center|800px|]]
 +
<br/>
 +
 
 +
<div style="text-align: center;"><b>And this is our actual Project Scope (With Changes):</b></div>
 +
[[File:CLEBSScope-finals-highlightedchanges.png|frameless|center|800px|]]
 +
<br/>
 +
 
 +
<div style="text-align: center;"><b>This chart below shows the changes to our Project Scope</b></div>
 +
{| class="wikitable" width="100%" padding="5px"
 +
|-
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Date
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Scope Type
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Module Name
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Original Details
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Changes
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Final Details
 +
 
 +
|-
 +
| align=center | 23 Oct 2016
 +
| align=center | Secondary Scope
 +
| align=center | Messaging Module
 +
| align=center | Inbox Messaging (Via E-mail)
 +
| align=center | Use of Facebook Messenger for users to contact one another (including admin)
 +
| align=center | Facebook Messenger Messaging
 +
|-
 +
 
 +
|-
 +
| align=center | 2 Nov 2016
 +
| align=center | Primary Scope
 +
| align=center | Payment Gateway Module
 +
| align=center | Use of Braintree API
 +
| align=center | Change in payment gateway option
 +
| align=center | Use of PayPal API
 +
|-
 +
 
 +
|}
 +
 
 +
==Project Schedule (Plan Vs Actual)==
 +
 
 +
<div style="text-align: center;"><b> This was our initial Planned Schedule:</b></div>
 +
[[File:CLEBS-timeline-2.png|frameless|center|800px|]]
 +
<br/>
 +
 
 +
<div style="text-align: center;"><b> This is our Actual Schedule:</b></div>
 +
[[File:clebsfinaltimelinechanges.png|frameless|center|800px|]]
 +
<br/>
 +
 
 +
<div style="text-align: center;"><b>Listed below is our Schedule Progress Chart to show the tasks that are completed or incomplete:</b></div>
 +
[[File:Clebs-task-final-1.png|frameless|center|800px|]]
 +
[[File:Clebs-task-final-2.png|frameless|center|800px|]]
 +
[[File:Clebs-task-final-3.png|frameless|center|800px|]]
 +
 
 +
==Project Metrics==
 +
 
 +
<div style="text-align: center;"><b>Listed below are our collated and updated Schedule Metrics and Bug Metrics.</b></div>
 +
 
 +
[[File:CLEBSSchMetricsGraph.png|frameless|center|800px|]]
 +
<br/>
 +
 
 +
[[File:CLEBSBugMetricsGraph.png|frameless|center|800px|]]
 +
 
 +
<!-- Why Schedule delay? Why BM high? -->
 +
 
 +
==Change Management==
 +
{| class="wikitable" width="100%" padding="5px"
 +
|-
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Change Request
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Reason For Change
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Team's Decision
 +
 
 +
|-
 +
| align=center | Mobile-friendly (Responsive) UI
 +
| align=center | Most users now surf the web using their smart phones or tablets, and thus, the sponsors feel that we should make the YBCO platform responsive and mobile-friendly to cater to these group of people
 +
| align=center | Approved (to be completed in the last iteration)
 +
|-
 +
 
 +
|-
 +
| align=center | Move Payment Gateway Module Back
 +
| align=center | Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back to give them time to settle the administrative issues
 +
| align=center | Approved
 +
|-
 +
 
 +
|-
 +
| align=center | Make Project Creation Module Editable In-page
 +
| align=center | Sponsor asked for us to implement user-friendly and in-page editing for project creators (so that they won't be constantly redirected to other pages) when creating a project. This enhances the overall user experience for them
 +
| align=center | Approved
 +
|-
 +
 
 +
|-
 +
| align=center | Create intuitive "TypeForm-like" Forms in Project Proposal
 +
| align=center | Sponsor requested for us to consider enhancing the Project Proposal form, similar to that of TypeForm.
 +
| align=center | Rejected (Too complex)
 +
|-
 +
 
 +
|-
 +
| align=center | Switch from E-Mail to Facebook Messenger
 +
| align=center | Sponsor requested for us to consider using Facebook Messenger for internal YBCO conversation between users
 +
| align=center | Approved
 +
|-
 +
 
 +
|-
 +
| align=center | Switch from Braintree to PayPal
 +
| align=center | Sponsor requested for us to use PayPal for payment gateway (using his account) as Braintree does not support crowdfunding
 +
| align=center | Approved
 +
|-
 +
 
 +
|-
 +
| align=center | Populate static pages (e.g. FAQ, Help, About Us pages)
 +
| align=center | Sponsor would like to give us information to fill up these pages with to ensure that there are information available for potential and current users
 +
| align=center | Rejected (focus on core functions)
 +
|-
 +
 
 +
|-
 +
| align=center | Change in Business Model
 +
| align=center | Sponsor would like to adopt a batch-based project release (e.g. 6 projects to go LIVE every 3 months) instead of current "accept-and-approve" approach
 +
| align=center | Accepted (Easy to implement)
 +
|-
 +
 
 +
|}
 +
 
 +
==Project Risks==
 +
 
 +
<!-- Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken. -->
 +
 
 +
{| class="wikitable" width="100%" padding="5px"
 +
 
 +
|-
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Number
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Risk & Description
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Impact
 +
! style="text-align: center; bold;background: #00beff;color:#ffffff; width:100px; border:1px solid #00beff" | Mitigation Plan
 +
 
 +
|-
 +
| align=center | 1
 +
| align=center | Taking on Ruby on Rails Development without prior knowledge
 +
| align=center | High
 +
| align=center | Team has to constantly work together and ask questions if there are any issues. In the event that a member(s) is/are unsure of how to code out a function, he or she should source for help, not just among the team, but other alternative options as well
 +
|-
 +
 
 +
|-
 +
| align=center | 2
 +
| align=center | Choice of servers (GoDaddy, AWS and Heroku) that are unfamiliar and complex
 +
| align=center | High
 +
| align=center | Team has to read online documentations as much as possible and look out for related online forums for help. Team should also look into asking YBCO CTO Uttam for help as he is familiar with such technologies
 +
|-
 +
 
 +
|-
 +
| align=center | 3
 +
| align=center | Additional project scope from the sponsors
 +
| align=center | Medium
 +
| align=center | As of now, most of the plans have been finalised. In the event that there are changes to the scope, Project Manager should evaluate and decide as a team whether to take up the change request and inform the sponsors of the team's decision. Team has to manage the expectations of the sponsors and ensure that we can deliver what we aim to
 +
|-
 +
 
 +
|}
 +
 
 +
=Technical Complexity=
 +
 
 +
<!-- Add images or scenarios -->
 +
 
 +
[[File:Clebs-finals-techcomplexity-words-1.png|frameless|center|600px|]] <br/><br/>
 +
[[File:Clebs-finals-techcomplexity-words-2.png|frameless|center|600px|]]
 +
 
 +
==System Architecture Diagram==
 +
 
 +
<!-- 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.-->
 +
[[File: Clebsarchitecture.png|frameless|center|700px|]]
 +
 
 +
==Intermediate Deliverables==
 +
 
 +
{|  class="wikitable"  border="1"
 +
|- style="background:#00beff; color:white"; text-align:center;"
 +
! style="text-align: center; bold;background: #00beff;color:white; width:20px; border:1px solid #999" | Stage
 +
! style="text-align: center; bold;background: #00beff;color:white; width:20px; border:1px solid #999" | Specification
 +
! style="text-align: center; bold;background: #00beff;color:white; width:20px; border:1px solid #999" | Module
 +
|-
 +
|rowspan="8" style="text-align:center;"| Project Management
 +
 
 +
|| Minutes
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION MINUTES|Meeting Minutes]]
 +
|-
 +
|| Project Schedule
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PLANNING|Project Schedule]]
 +
|-
 +
|| Project Scope
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PROJECT OVERVIEW SCOPE|Project Scope]]
 +
|-
 +
|rowspan="2"| Metrics
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PROJECT PLANNING METRICS|Schedule Metrics]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PROJECT PLANNING METRICS|Bug Metrics]]
 +
|-
 +
|rowspan="2"| Management
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PROJECT PLANNING CHANGE MGMT|Change Management]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PROJECT PLANNING RISK|Risk Management]]
 +
|-
 +
|| X-Factor
 +
|| [[IS480 Team wiki: 2016T1 CLEBS PROJECT OVERVIEW X-FACTOR|X-Factor]]
 +
 
 +
|-
 +
|rowspan="7"| Documentation & Design
 +
|| Use Case
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION| Use Case Diagram]]
 +
|-
 +
|rowspan="3"| Designs
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION|ER Diagram]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION|LD Diagram]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 CLEBS IMPLEMENTATION|User Story]]
 +
|-
 +
|rowspan="2"| Tools & Architecture
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION|Tools Used]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION|Technologies Used]]
 +
|-
 +
|| Architecture Diagram
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION DESIGN|Architecture Diagram]]
 +
 
 +
|-
 +
|rowspan="7" style="text-align:center;"| Testing
 +
|| Iteration Tests
 +
|| [[IS480 Team wiki: 2016T1 CLEBS DOCUMENTATION TEST|Iteration Test Results]]
 +
|-
 +
|rowspan="4"| User Tests
 +
|| [[IS480 Team wiki: 2016T1 Team CLEBS User Test 1|User Test 1]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 Team CLEBS User Test 2|User Test 2]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 Team CLEBS User Test 3|User Test 3]]
 +
|-
 +
|| [[IS480 Team wiki: 2016T1 Team CLEBS User Test 4|User Test 4]]
 +
 
 +
|}
 +
 
 +
<!--
 +
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
 +
-->
 +
 
 +
==Deployment Link==
 +
<!--
 +
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]].-->
 +
[[File:Ybco-web.png|frameless|center|800px|]]
 +
 
 +
==Testing==
 +
 
 +
As of 11th November 2016, we have completed 3 User Tests with a group of users (including some from our sponsors) comprising of students and members of public. These tests were to get a good indication that we are progressing in the right direction with regards to our web application and get users' feedback on the User Interface, the overall User Experience as well as the time taken to complete different functions to know where we may fall short.
 +
 
 +
<div style="background:#00beff; padding: 10px; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Century Gothic" color="#F7F7FF">
 +
User Test 1 Test Plan</font></div>
 +
<div style="background:#ffffff; padding: 10px">
 +
<b>Date:</b> 27 July 2016, Wednesday<br/>
 +
<b>Venue:</b> At participants' convenience<br/>
 +
<b>Duration:</b> 10 – 20 minutes per participant<br/>
 +
<b>Number of Participants:</b> 12<br/>
 +
<b>Age range:</b> 19 – 26<br/>
 +
<br/>
 +
<hr>
 +
<br/>
 +
 
 +
<b>Objectives:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Identify functionalities and usability issues</li>
 +
<li>&nbsp;&nbsp;Determine is the user interface is intuitive</li>
 +
<li>&nbsp;&nbsp;Discover ways to improve features and functions of the website based on the results of User Testing #1</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Scope:</b><br/>
 +
The scope for User Testing 1 are the modules from sprints 1 - 3<br/>
 +
<ol>
 +
<li>&nbsp;&nbsp;Registration Module</li>
 +
<ul>
 +
  ''<li>Log In</li>''
 +
  ''<li>Log Out</li>''
 +
  ''<li>Registration</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Profile Management Module</li>
 +
<ul>
 +
  ''<li>Update Profile (including upload profile picture)</li>''
 +
  ''<li><strike>Reset Password</strike> (Shifted to sprint 5)</li>''
 +
  ''<li>Change password</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Proposal Module</li>
 +
<ul>
 +
  ''<li>Submit Project Proposal</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;User Management Module</li>
 +
<ul>
 +
  ''<li>View All Users</li>''
 +
  ''<li>Ban Users</li>''
 +
  ''<li>Un-ban Users</li>''
 +
</ul>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
 
 +
 
 +
<div style="background:#00beff; padding: 10px; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Century Gothic" color="#F7F7FF">
 +
User Test 2 Test Plan</font></div>
 +
<div style="background:#ffffff; padding: 10px">
 +
<b>Date:</b> 21 September 2016, Wednesday, 7 PM Onwards<br/>
 +
<b>Venue:</b> SIS GSR 2-3 <br/>
 +
<b>Duration:</b> 10 – 20 minutes per participant<br/>
 +
<b>Number of Participants:</b> 20<br/>
 +
<b>Age range:</b> 19 – 24<br/>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Objectives:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Identify functionalities and usability issues</li>
 +
<li>&nbsp;&nbsp;Determine is the user interface is intuitive</li>
 +
<li>&nbsp;&nbsp;Discover ways to improve features and functions of the website based on the results of User Test 2</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Scope:</b><br/>
 +
The scope for User Testing 2 are the modules from sprints 3 - 6<br/>
 +
<ol>
 +
<li>&nbsp;&nbsp;Module</li>
 +
<ul>
 +
  ''<li>Log In</li>''
 +
  ''<li>Log Out</li>''
 +
  ''<li>Registration</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Proposal Module</li>
 +
<ul>
 +
  ''<li>Submit Project Proposal</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Review Module</li>
 +
<ul>
 +
  ''<li>Accept/Reject project proposals</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Creation Module (Edit)</li>
 +
<li>&nbsp;&nbsp;Reset Password</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
 
 +
<div style="background:#00beff; padding: 10px; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Century Gothic" color="#F7F7FF">
 +
User Test 3 Test Plan</font></div>
 +
<div style="background:#ffffff; padding: 10px">
 +
<b>Date:</b> 23 October 2016, Sunday, 730 PM Onwards<br/>
 +
<b>Venue:</b> SMU Labs Level 3 <br/>
 +
<b>Duration:</b> 20 - 30 minutes per participant<br/>
 +
<b>Number of Participants:</b> 28<br/>
 +
<b>Age range:</b> 19 – 26<br/>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Objectives:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Identify functionalities and usability issues</li>
 +
<li>&nbsp;&nbsp;A/B Testing to find out which design can speed up the time taken to 1) submit a project proposal and 2) create a project</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Scope:</b><br/>
 +
The scope for User Testing 3 are the following modules<br/>
 +
<ol>
 +
<li>&nbsp;&nbsp;Project Proposal Module</li>
 +
<ul>
 +
  ''<li>Submit project proposal</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Creation Module</li>
 +
<ul>
 +
  ''<li>Create a project, should it be accepted</li>''
 +
  ''<li>Update project description, project rewards, project milestones and project updates</li>''
 +
</ul>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
 
 +
<div style="background:#00beff; padding: 10px; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Century Gothic" color="#F7F7FF">
 +
User Test 4 Test Plan</font></div>
 +
<div style="background:#ffffff; padding: 10px>
 +
<b>Date:</b> 16 November 2016, Wednesday<br/>
 +
<b>Venue:</b> SMU Labs<br/>
 +
<b>Duration:</b> 3 hours<br/>
 +
<b>Number of Participants:</b> 25 participants, 4-5 participants per session
 +
 
 +
<br/>
 +
<hr>
 +
<br/>
 +
 
 +
<b>Objectives:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Identify functionalities and usability issues</li>
 +
<li>&nbsp;&nbsp;''100%'' should be able to sign up for an account</li>
 +
<li>&nbsp;&nbsp;''100%'' should be able to submit project proposal</li>
 +
<li>&nbsp;&nbsp;''100%'' should be able to accept/reject project proposal</li>
 +
<li>&nbsp;&nbsp;''At least 85%'' should be able to edit project</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
 
 +
<br/>
 +
<b>Scope:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Registration Module</li>
 +
<li>&nbsp;&nbsp;Create project proposal Module</li>
 +
<li>&nbsp;&nbsp;Project review Module</li>
 +
  <ul>
 +
    <li>&nbsp;&nbsp;''Accept/Reject project proposal''</li>
 +
  </ul>
 +
<li>&nbsp;&nbsp;Project creation Module</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
 
 +
=Reflection=
 +
==Team Reflection==
 +
 
 +
 
 +
[[File:CLEBS-final-reflection-1.png|frameless|center|700px|]]
 +
[[File:CLEBS-final-reflection-2.png|frameless|center|700px|]]
 +
[[File:CLEBS-final-reflection-3.png|frameless|center|700px|]]

Latest revision as of 04:46, 22 November 2016

ClebsLogo.png
ClebsHome.png HOME

ClebsAboutUS.png THE TEAM

ClebsProjectOverview.png PROJECT OVERVIEW

ClebsProjectManagement.png PROJECT MANAGEMENT

ClebsDocumentation.png DOCUMENTATION

M A I N

M I D - T E R M

F I N A L

Project Progress Summary

Final Slides:

Deployed Site Link:

Ybco-web.png

Note: We have yet to publish on the existing YBCO website as the client is still looking to make changes to the business model as well as carry out testing first.

Project Highlights

What was achieved from Mid-Terms?

  • Confirmed on our Payment Gateway Technology (PayPal)
  • Completion of the entire Projects Module
    • Project Creation Module (Iteration 5) was completed and users, after having their project proposal accepted, are able to create their projects
    • Project creators are now also able to edit their projects and submit their completed projects to go LIVE
  • Completion of Messaging Module
    • Users are now able to interact with one another using Facebook Messenger
  • En-route to achieving final X-Factor:
    • 8 Projects Submitted
    • 3 Projects Funded


What unexpected events occurred?

  • Changes to Project Scope and Timeline
    • Sponsor experienced difficulty in setting up a BrainTree and Stripe account and was only given PayPal to work with (on 2nd November 2016)
    • Sponsor requested changes to content in home page
  • Changes to business model
    • Sponsor was contemplating changing the business model, which further affected our development

Project Management

Project Status

This was our initial planned Project Scope, before the changes:
Clebs-scope-2.png


And this is our actual Project Scope (With Changes):
CLEBSScope-finals-highlightedchanges.png


This chart below shows the changes to our Project Scope
Date Scope Type Module Name Original Details Changes Final Details
23 Oct 2016 Secondary Scope Messaging Module Inbox Messaging (Via E-mail) Use of Facebook Messenger for users to contact one another (including admin) Facebook Messenger Messaging
2 Nov 2016 Primary Scope Payment Gateway Module Use of Braintree API Change in payment gateway option Use of PayPal API

Project Schedule (Plan Vs Actual)

This was our initial Planned Schedule:
CLEBS-timeline-2.png


This is our Actual Schedule:
Clebsfinaltimelinechanges.png


Listed below is our Schedule Progress Chart to show the tasks that are completed or incomplete:
Clebs-task-final-1.png
Clebs-task-final-2.png
Clebs-task-final-3.png

Project Metrics

Listed below are our collated and updated Schedule Metrics and Bug Metrics.
CLEBSSchMetricsGraph.png


CLEBSBugMetricsGraph.png


Change Management

Change Request Reason For Change Team's Decision
Mobile-friendly (Responsive) UI Most users now surf the web using their smart phones or tablets, and thus, the sponsors feel that we should make the YBCO platform responsive and mobile-friendly to cater to these group of people Approved (to be completed in the last iteration)
Move Payment Gateway Module Back Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back to give them time to settle the administrative issues Approved
Make Project Creation Module Editable In-page Sponsor asked for us to implement user-friendly and in-page editing for project creators (so that they won't be constantly redirected to other pages) when creating a project. This enhances the overall user experience for them Approved
Create intuitive "TypeForm-like" Forms in Project Proposal Sponsor requested for us to consider enhancing the Project Proposal form, similar to that of TypeForm. Rejected (Too complex)
Switch from E-Mail to Facebook Messenger Sponsor requested for us to consider using Facebook Messenger for internal YBCO conversation between users Approved
Switch from Braintree to PayPal Sponsor requested for us to use PayPal for payment gateway (using his account) as Braintree does not support crowdfunding Approved
Populate static pages (e.g. FAQ, Help, About Us pages) Sponsor would like to give us information to fill up these pages with to ensure that there are information available for potential and current users Rejected (focus on core functions)
Change in Business Model Sponsor would like to adopt a batch-based project release (e.g. 6 projects to go LIVE every 3 months) instead of current "accept-and-approve" approach Accepted (Easy to implement)

Project Risks

Number Risk & Description Impact Mitigation Plan
1 Taking on Ruby on Rails Development without prior knowledge High Team has to constantly work together and ask questions if there are any issues. In the event that a member(s) is/are unsure of how to code out a function, he or she should source for help, not just among the team, but other alternative options as well
2 Choice of servers (GoDaddy, AWS and Heroku) that are unfamiliar and complex High Team has to read online documentations as much as possible and look out for related online forums for help. Team should also look into asking YBCO CTO Uttam for help as he is familiar with such technologies
3 Additional project scope from the sponsors Medium As of now, most of the plans have been finalised. In the event that there are changes to the scope, Project Manager should evaluate and decide as a team whether to take up the change request and inform the sponsors of the team's decision. Team has to manage the expectations of the sponsors and ensure that we can deliver what we aim to

Technical Complexity

Clebs-finals-techcomplexity-words-1.png



Clebs-finals-techcomplexity-words-2.png

System Architecture Diagram

Clebsarchitecture.png

Intermediate Deliverables

Stage Specification Module
Project Management Minutes Meeting Minutes
Project Schedule Project Schedule
Project Scope Project Scope
Metrics Schedule Metrics
Bug Metrics
Management Change Management
Risk Management
X-Factor X-Factor
Documentation & Design Use Case Use Case Diagram
Designs ER Diagram
LD Diagram
User Story
Tools & Architecture Tools Used
Technologies Used
Architecture Diagram Architecture Diagram
Testing Iteration Tests Iteration Test Results
User Tests User Test 1
User Test 2
User Test 3
User Test 4


Deployment Link

Ybco-web.png

Testing

As of 11th November 2016, we have completed 3 User Tests with a group of users (including some from our sponsors) comprising of students and members of public. These tests were to get a good indication that we are progressing in the right direction with regards to our web application and get users' feedback on the User Interface, the overall User Experience as well as the time taken to complete different functions to know where we may fall short.

User Test 1 Test Plan

Date: 27 July 2016, Wednesday
Venue: At participants' convenience
Duration: 10 – 20 minutes per participant
Number of Participants: 12
Age range: 19 – 26



Objectives:

  1.   Identify functionalities and usability issues
  2.   Determine is the user interface is intuitive
  3.   Discover ways to improve features and functions of the website based on the results of User Testing #1




Scope:
The scope for User Testing 1 are the modules from sprints 1 - 3

  1.   Registration Module
    • Log In
    • Log Out
    • Registration
  2.   Profile Management Module
    • Update Profile (including upload profile picture)
    • Reset Password (Shifted to sprint 5)
    • Change password
  3.   Project Proposal Module
    • Submit Project Proposal
  4.   User Management Module
    • View All Users
    • Ban Users
    • Un-ban Users





User Test 2 Test Plan

Date: 21 September 2016, Wednesday, 7 PM Onwards
Venue: SIS GSR 2-3
Duration: 10 – 20 minutes per participant
Number of Participants: 20
Age range: 19 – 24



Objectives:

  1.   Identify functionalities and usability issues
  2.   Determine is the user interface is intuitive
  3.   Discover ways to improve features and functions of the website based on the results of User Test 2




Scope:
The scope for User Testing 2 are the modules from sprints 3 - 6

  1.   Module
    • Log In
    • Log Out
    • Registration
  2.   Project Proposal Module
    • Submit Project Proposal
  3.   Project Review Module
    • Accept/Reject project proposals
  4.   Project Creation Module (Edit)
  5.   Reset Password




User Test 3 Test Plan

Date: 23 October 2016, Sunday, 730 PM Onwards
Venue: SMU Labs Level 3
Duration: 20 - 30 minutes per participant
Number of Participants: 28
Age range: 19 – 26



Objectives:

  1.   Identify functionalities and usability issues
  2.   A/B Testing to find out which design can speed up the time taken to 1) submit a project proposal and 2) create a project




Scope:
The scope for User Testing 3 are the following modules

  1.   Project Proposal Module
    • Submit project proposal
  2.   Project Creation Module
    • Create a project, should it be accepted
    • Update project description, project rewards, project milestones and project updates




User Test 4 Test Plan

Date: 16 November 2016, Wednesday
Venue: SMU Labs
Duration: 3 hours
Number of Participants: 25 participants, 4-5 participants per session




Objectives:

  1.   Identify functionalities and usability issues
  2.   100% should be able to sign up for an account
  3.   100% should be able to submit project proposal
  4.   100% should be able to accept/reject project proposal
  5.   At least 85% should be able to edit project




Scope:

  1.   Registration Module
  2.   Create project proposal Module
  3.   Project review Module
    •   Accept/Reject project proposal
  4.   Project creation Module



Reflection

Team Reflection

CLEBS-final-reflection-1.png
CLEBS-final-reflection-2.png
CLEBS-final-reflection-3.png