HeaderSIS.jpg

IS480 Team wiki: 2010T2 Let’s Give!

From IS480
Jump to navigation Jump to search
Let's Give!
Team Let's Give
Founded Singapore Management University, Dec 2010
Type Private Limited
Area User Experience
Social Media
Web Design
Web 2.0
Industry Non-Profit Organization
Project Design Your Life
Team members CHAN Chin Hong
LAU Pei En
LAU Sheng Shiun
TAN Jian Wei
Sandy TUN
XU Xiao Yue

Established in 2007, Buy1Give1's (B1G1) mission is to provide the systems, structure and inspiration to turn our world into a world full of giving, thus directly creating a much happier world. B1G1 gives businesses and individuals the power to change lives; by transforming giving from an ad-hoc, event-driven model to a very specific transaction-based giving model — a world where every transaction gives back and makes a difference.

This makes giving an effortless habit, changing lives and making a difference every second, every day and in every little way. Until now, B1G1 has brought the power, resonance and ‘connected-ness’ of transaction-based giving and Impact-Based Giving to literally hundreds of thousands of small-to-medium-scale enterprises (SMEs) that form the backbone of every economy.

Team Lets Give! Poster

Contents

Introduction

Team

Team Let's Give! Group Photo

From Left: Tan Jian Wei, Shank Lau, Chan Chin Hong, Sandy Tun, Xu Xiaoyue, Lau Pei En
  • Tan Jian Wei - Project Manager
    • Oversees the Project Progress and manages the team schedule and set objectives for each iterations.
    • Breaks down and assign tasks to group members based on their strengths and schedule and keep track of metrics
  • Chan Chin Hong - Interface Subject Specialist
    • Principle developer for interface and Front-End Components
    • Liaises with sponsors with design requirements and how feasible are they
  • Lau Pei En - Developer
    • Principal developer for logic and back-end classes
    • Liaises with sponsors and key stakeholders regarding functionality and how feasible they are
  • Xu Xiaoyue - Developer
    • Developer for both Front-End and Back-End Components
    • Subject expert in terms of bridging functionality and design requirements
  • Sandy Tun - Database and Facebook Subject Expert
    • Implements and integrate various Facebook services with Giving Central
    • Oversees the development of schema for Giving Central's data needs in current B1G1 Drupal CMS-derived database

Mentors

Technical Advisors

Previous FYP teams that worked with B1G1

Stakeholders' Coordination

Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Team Bonding

Coding

Supervisor

Meeting

Internal

Meeting

Discussion

Coding

Meetings are usually with the client are on a fortnight basis.

Due to our close working relationship, meetings may occur whenever either side feels that it is necessary. In addition to meetings, we decided it was far more productive holding email and Skype conversations. This enabled us to accurately provide our client with exactly what they want, instead of second guessing. This saved us much time and ensured the rapid progress of our work.

The project's emphasis on the look and feel of the website meant that rigorous user testing is required. We capitalized on TeamViewer in the initial stages as it was not ready to be migrated to a live server. The client was regularly invited to test out the system whenever we completed a few functions, to ensure the quality of the experience that was delivered via our project. Once it was ready to be migrate to the testing server, regular emails were sent to invite the client to test and comment.

Project

Overview

Description - Project "Design Your Life"

Charity is, more often than not, a one off event driven by campaigns and drives. The "Design your Life" project aims to build an interactive web page that aids Buy1Give1 (B1G1) in raising awareness of worthy causes; by showing the general public the potential each individual has in creating an impact on others’ life. The web page will be accessed by both B1G1 members and non-members. All users are able to enter their daily lifestyle and the web page would generate how one can support the various initiatives under B1G1 that is complementary to their personal lifestyle and preferences.

Thus, B1G1 Giving Central was conceptualized by Masami and in 14 weeks, materialized by Team Let's Give.

Add comment here

B1G1 previous projects with SIS has grealy improved their outreach towards business-base giving. Now, the 4th collabration with SIS, Giving Central provides B1G1 a system for the other significant demographics of givers - Individual who wants to give and feel the impacts of their giving as per Businesses who give and impact per every transaction.

Furthermore, besides individual users, current businesses partners with B1G1 will also able to visit the web page and enter their respective revenue and pledge how much they would like to contribute to each initiative in accordance to their revenue. The more initiative the businesses support, the more exposure it gets via B1G1 as individual users who support common causes would discover these particular businesses. This provides an incentive to carry out CSR activities via B1G1 as it would provide exposure to the global market.

Motivation

To increase both businesses' and individuals' awareness of the potential impact they can create by the means of a highly interactive, easy to use and hassle-free website. The final vision, together with Individual Giving Central and Business Giving Central, the website will serves as a "forum" for current B1G1 business partners as well as individuals with like-minded objectives in giving for a better world to meet and collaborate to achieve greater impact to beneficaries around the world.

Objectives

Through this web page, the team hopes to achieve the following objectives:

  • Reach out to the individuals who are unaware of the world of giving.
  • Increase public awareness of their own capability to create an impact on others’ life
  • Incorporate giving as part of an individual and/or business lifestyle
  • Bring the businesses and individuals together to a community

Analysis

Use Cases**
Story Board

1. User logs in via Facebook landing page Lg 1.jpg

2. Profile Page Lg 2.jpg

3. Giving Categories Lg 3.jpg

4. Select Worthy Cause for Giving Category Lg 4.jpg

5. Refine Search Lg 5.jpg

6. Monthly Giving Page Lg 6.jpg

Design

Architecture Overview

ArchitectureB1G1.png

Scope

  • Facebook SSO Login
  • Login for Current B1G1 Users
  • Create New Account
  • Categories selection
  • Project Selection
  • Project Popularities (for project detail pop-up)
  • 'Refine Search' feature for project selection
  • 'Skip' feature for project selection
  • Profile edit feature
  • Password change feature
  • Impact calculator (the impact measuring bar and linking the impact with plant images)
  • 'How to grow' info pop-up for Giving impact tab
  • Giving - 'Make it happen process' including the payment part (is it part of final presentation requirement?)
  • Facebook 'Share' button for Giving History
  • Shop and Give feature
  • Business Recommendation feature
  • Award feature
  • Favourite Business feature
  • Pledge feature
  • User's public profile page

Management

Workplan**


Milestones

LGMilestones.png

Metrics

To facilitate effective project management, 2 metrics are used.

Schedule Metric
  • Measures schedule effectiveness
  • Reviewed after each week and iteration
  • Schedule Effectiveness Index = Actual Completed Time (days) / Estimated Time (days)

Weekly Action Plan

SEI Action to be taken
<0.5
  • Look into why functionalities are completed in such a rapid pace
  • Revision of Schedule for ongoing iteration
0.5 - 1.5
  • Normal Pace
>1.5
  • Look into the reasons behind the slow progress
  • Revision of Schedule

Iteration Action Plan

SEI Action to be taken
<0.7
  • Overestimated Task Schedule
  • Revision of Schedule for next iteration(s)
  • Possible Enhancements or Functionalities to be implemented
0.7 - 1.3
  • Normal Pace
>1.3
  • Underestimated difficulty of tasks
  • Need to allocate more meetings and time
  • Revision of Schedule for next iteration(s)
  • Look into dropping of non-critical functionalities

Final Schedule Metric Chart

B1G1 LG Slide48.PNG

Bug Metric
  • Dictates action to be taken when dealing with bugs
  • Provides a tangible indication and action plan
  • Iteration Bug Severity (IBS) = ∑ (No. of bugs x bug severity level) per iteration
Bug Severity Level
Severity Description
5 - Severe
  • Hinders completion of key functions
  • Affects completed functions of previous built
3 - Normal
  • Bug affects key output or other functions of the system
1 - Minor
  • Isolated bug that does not affects other functions
  • Cosmetically output based bugs


Bug Resolution
IBS Action to be taken
<4
  • Debuggers: 1 - 2
  • Deadline : Flexible
4-9
  • Debuggers: 1 - 2
  • Deadline : Before next iteration
>9
  • Debuggers: >2 or as necessary
  • Deadline : Before next iteration
  • Re-assessment of current implementation

Final Bugs Metric Chart

B1G1 LG Slide51.PNG B1G1 LG Slide52.PNG

Risks and Mitigation Strategy

LG Risk and Migitation.png

Minutes

Week 1 Meeting
Weel 2 Meeting
Week 3 Meeting
Week 4 Meeting
Week 5 Meeting
Week 6 Meeting
Week 7 Meeting
Week 8 Meeting
Week 9 Meeting
Week 10 Meeting
Week 11 Meeting
Week 12 Meeting
Week 13 Meeting
Week 14 Meeting
Week 15 Meeting

Suite of Applications

Project Retrieval Algorithm

Project algor.png

Country Filter

Country filter.png

Facebook Sign-in

Awesome Feature 1

Stupendous Feature 2

Bombastic Feature 3

Quality

Bugs

UAT

Heuristics

Functionality

Usability

Testing

Execution

Code

Documentation

Deployment

Test Plan

2 versions of UAT has been created. First (Long) version used mainly for regressional testing to be done by SIS Peers and B1G1 Staff that spans from validation to functionality and heuristic feedbacks
UAT Long Version

Short version that is distributed to Non-SIS Peers and B1G1 Current Users that focus mainly on functionality and heursitic issues.
UAT Short Version

UAT

Resources

Technology Used Software Used

Learning Outcomes**

New Skills

Improving Existing Skills

Challenges

Team Reflection

Individual Reflection

Deliverables**

Use Case Diagram

Use Case Descriptions and Technologies Used

Mobile Version Screen Shots

Test Plan

Source Codes

User Manual

Presentation Slides

Old Wiki---------------------------------------------

Project Overview

Current Status

  • Collapsible Side Menu [Completed]
  • Giving Impact Calculator [Completed]
  • JCarousel Project Browsers [Completed]
  • Project Search with QTip [Completed]
  • Search Function for Projects [Completed]
  • Facebook Sign on [Completed]
  • Filters
  • Paypal Integration
  • Business Giving Central [Removed from FYP scope... BUT WILL BE DONE!]
  • Awards Module
  • Business Recommendation
  • Business Connections
  • Daily Habits Calculator Interface
  • Giving History

Metric

Metrics

To facilitate effective project management, 2 metrics are used.

Schedule Metric
  • Measures schedule effectiveness
  • Reviewed after each week and iteration
  • Schedule Effectiveness Index = Actual Completed Time (days) / Estimated Time (days)
Weekly Action Plan
SEI Action to be taken
<0.5
  • Look into why functionalities are completed in such a rapid pace
  • Revision of Schedule for ongoing iteration
0.5 - 1.5
  • Normal Pace
>1.5
  • Look into the reasons behind the slow progress
  • Revision of Schedule
Iteration Action Plan
SEI Action to be taken
<0.7
  • Overestimated Task Schedule
  • Revision of Schedule for next iteration(s)
  • Possible Enhancements or Functionalities to be implemented
0.7 - 1.3
  • Normal Pace
>1.3
  • Underestimated difficulty of tasks
  • Need to allocate more meetings and time
  • Revision of Schedule for next iteration(s)
  • Look into dropping of non-critical functionalities
Metric Chart

Metric1.JPG

Bug Metric
  • Dictates action to be taken when dealing with bugs
  • Provides a tangible indication and action plan
  • Iteration Bug Severity (IBS) = ∑ (No. of bugs x bug severity level) per iteration
Bug Severity Level
Severity Description
5 - Severe
  • Hinders completion of key functions
  • Affects completed functions of previous built
3 - Normal
  • Bug affects key output or other functions of the system
1 - Minor
  • Isolated bug that does not affects other functions
  • Cosmetically output based bugs


Bug Resolution
IBS Action to be taken
<4
  • Debuggers: 1 - 2
  • Deadline : Flexible
4-9
  • Debuggers: 1 - 2
  • Deadline : Before next iteration
>9
  • Debuggers: >2 or as necessary
  • Deadline : Before next iteration
  • Re-assessment of current implementation

Minutes

Meeting 1
Meeting 2
Meeting 4

Mid Term Review

Mid Term Review Deliverables