IS480 Team wiki: 2016T1 CLEBS Finals

From IS480
Jump to navigation Jump to search
ClebsHome.png HOME

ClebsAboutUS.png THE TEAM

ClebsProjectOverview.png PROJECT OVERVIEW

ClebsProjectManagement.png PROJECT MANAGEMENT

ClebsDocumentation.png DOCUMENTATION


M I D - T E R M


Project Progress Summary

Final Slides:

Deployed Site Link:


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:

And this is our actual Project Scope (With Changes):

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:

This is our Actual Schedule:

Listed below is our Schedule Progress Chart to show the tasks that are completed or incomplete:

Project Metrics

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


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



System Architecture Diagram


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



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


  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

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


  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

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


  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

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


  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


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


Team Reflection