IS480 Team wiki: 2011T1 Discover Linkage

From IS480
Jump to navigation Jump to search
DiscoverLinkage Team and Logo.jpg

About Us

Discover Linkage is a team of five purposeful and innovative Singaporean students from School of Information Systems (SIS), Singapore Management University. We aspire to create newfangled IT solutions that will fascinate the world.

When the World Wide Web was first introduced, no one had any idea how it was going to change the lifestyle of millions around the world. Currently, people of all ages and various nationalities have started using the cyberspace immensely as web technologies have leaped forward faster than ever before in the past decade.

Our trademark represents a two Cs- the left C represents Curiosity & Creativity and the right represents Connectivity that brings our ideas together. With these three elements in mind, we call ourselves Linkers to bridge the gap between technological and business needs. Being young, dynamic and mobile, we are ready to handle exciting challenges as and when they come our way. As we have worked together in past projects, we know that together as a team we are dedicated Linkers and we are ready to tackle this!

Team Discover Linkage

Name Role Responsibility
Madhan S/O Kaliappan Project Manager
  • Assign the various tasks to the team
  • Set milestones
  • Calculate the duration of the project
  • Arrive at an optimal project plan and to avoid resources conflicts
  • Ensure that the team members stay focused on the objectives and remain motivated during their work
  • Envision possible risks and their impacts on the project
  • Handle risks in a professional way when they appear
  • Make sure that the sponsors requirements are met
  • Ensure the success of the project
Lionel Pan Poheng Lead Software Developer
  • Ensure that every team member keep up the coding standards
  • Assign the various coding tasks to team members
  • Set up the coding environment
  • Ensure that coding conform to written technical specifications
  • Lead the team to perform maintenance programming and correction of identified defects
  • Supervise team members on their coding tasks
Manesh Kumar Rai Interface Designer
  • Assist the Lead Software Developer
  • Sketch UI
  • Code CSS and scripts
  • Research third party scripts
  • Design UI
  • Ensure that UI meets sponsor requirements
  • Ensures that the system is well planned and conduct UI Updates with the team
Kenny Lin Baochong System Analyst & Relations
  • Interpret written business requirements and technical specification documents
  • Critique the software development process
  • Create and maintain technical documentation using defined technical documentation templates
  • Investigate, analyse and document reported defects
  • Create, document, and implement unit test plans, scripts, and test harnesses
  • Incharge of UAT testing
  • Update the team Wiki page
  • Main communication source to the sponsors
Nittala Swetha Sharmista Database Developer
  • Design database architecture
  • Ensure that the database is running smoothly
  • Plan mitigation strategies for database related problems
  • Assist in updating team Wiki page
  • Documentation of the user manuals, etc



Professor Jason Woodard

Client & Sponsor

Organization Name Position
TEDx Singapore Mr. Dave Lim Curator and Founder

Project Overview

Current Scenario

Discover Linkage Current Scenario.jpg

Proposed Scenario

Discover Linkage Proposed Scenario.jpg

Project Description

  • Team Discover Linkage will be building a Social Networking Site (SNS) for the curator of TEDx Singapore, Mr. Dave Lim. The main goal is to allow people of same interests to meet and interact with each other on a social platform. This SNS will be primarily called xConnect. Unlike other social networking sites, which mainly focus on their member’s friends’ lists, xConnect would be focusing on being a platform for individuals to communicate with other individuals who share a similar interest via interests groups.


  • The motivation is to ensure that there is a bigger and better communication channel. This website is meant to find people of similar tastes and be able to interact with them and enhance that aspect of their life. The user can then contact these members and request for a meet-up or start up a discussion about their common interests

Project Scope

  • xConnect aims to design and launch an online social network platform that complements existing social networks. Most importantly, this platform will enable members of the community to find and connect with others in more meaningful and useful ways that general social network platforms cannot do. Also, members will be able to find and connect with each other based on common interests, passion and other fields. They could also connect based on common interest in particular topics, talks / initiate or join groups.

Project Assumptions

  • The xConnect social networking platform will be mainly connecting Singapore users during the testing phases of the project.

Development Tools & Technologies

DiscoverLinkage dvpmtTools.jpg

Team's Collaboration Tools

Google Docs

DiscoverLinkage GoogleDocs.png
Reference: http://docs.google.com/


DiscoverLinkage TortoiseSVN.PNG
Reference: http://tortoisesvn.tigris.org/

Project Management

Project Milestone & Schedule

DiscoverLinkage Timeline.png

Project Meeting Minutes

Project Risk Management

Risk Management Process

DiscoverLinkage Risk.png

Risk Management Process Image Reference

Risk Assessment Table

DiscoverLinkage RiskManagement.png
S/N Risk Description Likelihood of Occurrence (H/M/L) Impact of Risk (H/M/L) Level Derived Mitigation Plan
1 Team members unaware of procedure for synchronising and understanding of PHP framework. L H B
  • PM to ensure all is in the loop for the chosen framework.
  • Urgent meeting to be held to explain usage and importance of synchronising fundamentals.
2 Project outline changes from client. L M B
  • The team structure of the programme will not be heavily affected.
  • PM to review new outline and hold meeting to discuss changes to project and also do a comprehensive re-scheduling.
3 Team members is unfamiliar with deployment platform. M H A
  • Development team to be trained
  • Research team to educate rest of the team.

Project Metrics

Bug Metric

  • Resolved Rate (x) = Number of bugs resolved / Total number of bugs found
Metric Priority Implication
0.7 < x <= 1 Minor Codes on Track
0.3 <= x <= 0.7 Major Debugging must be given greater emphasis
x < 0.3 Critical Debugging will have to take priority before moving on to other functionalities

  • Bug Metric Action Plan
Priority Severity Description
Critical High
  • Requires urgent attention.
  • Bug needs to be resolved urgently. PM to stop all further coding and all members of the team including the PM have to focus on debugging the codes.
Major Medium
  • Requires timely attention.
  • Bugs required more time then predicted to resolve. PM to plan for debugging sessions to resolve the bugs.
Minor Low
  • Requires attention.
  • Bugs are resolve quickly and required little or no changes to the schedule.

Stress Metric

  • Level Of Stress (x) = Total stress points per week and Rate of change of average stress points per week

Our Goal Improve happiness and stress level in the team

Question How do we know when one of us is under tremendous stress? How do we define stress?

Total stress points per week

Complete a list of 8 emotional-related questions on a scale from 1 to 5 weekly. The maximum score is 40, the higher the score, the more stressed and unhappy that member is.

Metric Priority Implication
x > 20 Minor Minor Stress Levels
x > 25 Major Major Stress Levels
x > 30 Critical Critical Stress Levels

  • Stress Metric Action Plan
Priority Severity Description
Critical High
  • Requires urgent attention.
  • PM chats with that member and lessen his/her workload, and notify the rest of the team members
Major Medium
  • Requires timely attention.
  • PM chats with that member and understand his/her emotional states.
Minor Low
  • Requires attention.
  • PM takes note of his/her behaviour and monitor quietly.

Rate of change of average stress points per week (y)

Maximum score for average stress point per week is 1. The purpose is to measure the rate of emotional well-been of members throughout the week.

Metric Priority Implication
y > 0.1 Minor Minor Stress Levels
y > 0.2 Major Major Stress Levels
y > 0.3 Critical Critical Stress Levels

  • Stress Metric Action Plan
Priority Severity Description
Critical High
  • Requires urgent attention.
  • PM chats with that member and notify the rest of the team members. Possible action includes lessening of workload.
Major Medium
  • Requires timely attention.
  • PM chats with that member and understand his/her emotional states.
Minor Low
  • Requires attention.
  • PM takes note of his/her behaviour and monitor quietly.

Schedule Metric

  • Factor (x) = Actual time taken (Days) / Planned time (Days)
Metric Status
x < 1 Ahead of Schedule
x = 1 On Schedule
x > 1 Behind Schedule

  • Schedule Metric Action Plan
Status Action
Behind Schedule PM may increase individual workload to keep up the pace
On Schedule PM will need to actively review the task in schedule at the end of iteration
Ahead of Schedule PM to assess the deliverables of the project and adjust accordingly

Performance Metric

  • PM evaluates after every iterations:
  1. Inception
  2. Elaboration
  3. Construction
  4. Transition
  • Evaluation based upon:
    • Categories
      • Contribution to group goals
      • Task accomplishment
      • Consideration of others
      • Contribution of knowledge
      • Group cooperation
    • Scores(1 to 4)

Project Deliverables

Use Case Diagram

Core Features

DiscoverLinkage Usecase 1.png

Additional Features

DiscoverLinkage Additional.png

Future Enhancement

DiscoverLinkage Future.png

Solution Architecture Diagram

Discover Linkage Solution Archi.jpg


Click here to access our Mid-Term deployment

User Acceptance Testing

Click here to view our UAT testing information

Project Summary

Project challenges

  • To be filled

Project Achievements


  • To be filled

Overall Group Learning Outcomes (LOMS)

DiscoverLinkage LOMS.png

Individual Learning Outcomes (Mid-Term)


  • To manage the team despite team members’ different schedules and commitments
  • To code in php which i have not done at all
  • Handle client requirements and negotiate with client
  • Handle technical problems when they appear as a bottleneck


  • Learned to mediate conflicts within the team
  • Familiarize with php coding
  • Understand the importance of team dynamics in order to get things done
  • Learned to prioritize things in the midst of busy schedule and school work
  • Learned to delegate task to team members base on their strengths and weaknesses


  • To work with different working styles and schedules of team and project sponsor
  • Handle project sponsor’s requirements and to negotiate scope
  • To foresee project’s or team’s problems, analyse problems encountered & communicate with members
  • To understand team’s strengths and weaknesses based on each individual


  • Learned how to code using a new framework and understand the pros and cons of using a framework
  • Learned how to handle client’s expectations and communicate effectively and clearly in terms of expected project scope and requirements
  • Learned how to work with new teammates, recognise each others’ strengths and weaknesses and learn how to manage a team when we hit a situation.
  • Iterative approach is hugely beneficial in terms of communication with clients, supervisor and within the team.


  • Gained confidence in using Cascading Style Sheets (CSS) when designing the User Interface
  • Gained the knowledge in creating and integrating CSS designs within PHP
  • Better knowledge in CakePHP framework and understanding traditional fundamentals when incorporating CSS into CakePHP framework
  • Learned how to identity and foresee critical project or group problems, evaluate the problems encountered, and communicate the solutions effectively within the group
  • Acquired the skills to assess individual team members strengths and weaknesses
  • Acquired the skills to listen critically to interpret and evaluate client’s requirements and expectations
  • Understand the importance of continuous learning process and group dynamics which are essential components for a group to function in an effective manner


Team Reflection

Comment on Iterative Approach

Our team believes that the iterative approach is hugely beneficial in terms of communication with clients, supervisor and within the team. However, drawbacks might include lesser time for actual coding and more time and effort spent on meetings

As a team, we believe that the Iterative Approach is hugely beneficial in terms of communication with clients, supervisor and within the team. However, drawbacks might include lesser time for actual coding and more time and effort spent on meetings. Many of our meetings are taken up by project management and though it is an important and in fact a crucial part of the project, we were not able to concentrate so much on the technical aspect of the project. As important as project management is, technical aspect and coding is also an important part of the entire project.

Seeing as how we are 5 man team, in the beginning it was difficult for us to stick to our roles because everyone had different strengths and beliefs on how to approach a certain issue. It was only much into the term that we came up with a proper system to handle both project management and technical aspects of the project. We also had to deal with team conflicts on commitment issues and different working styles adaptation issues. This has certainly slowed us down, but in a way, it helped us deal with such real world situations, which will only be a good thing for us in our individual careers.

Learning to code in an entirely new language was a steep learning curve for us but the many resources we had at hand helped us. The only issue we had was the lack of time to do in-depth learning before having to jump into coding. We understand now the importance of having all the technologies sorted out way before term actually starts, which is why we now have taken steps to ensure we do not face any hiccups along the rest of our FYP journey.

Individual Reflection

Mid-term Wiki

Final Wiki