IS480 Team wiki: 2011T1 Discover Linkage
- 1 About Us
- 2 Team Discover Linkage
- 3 Stakeholders
- 4 Project Overview
- 5 Development Tools & Technologies
- 6 Team's Collaboration Tools
- 7 Project Management
- 8 Project Deliverables
- 9 Project Summary
- 10 Overall Group Learning Outcomes (LOMS)
- 11 Reflection
- 12 Mid-term Wiki
- 13 Final Wiki
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
|Madhan S/O Kaliappan||Project Manager||
|Lionel Pan Poheng||Lead Software Developer||
|Manesh Kumar Rai||Interface Designer||
|Kenny Lin Baochong||System Analyst & Relations||
|Nittala Swetha Sharmista||Database Developer||
Client & Sponsor
|TEDx Singapore||Mr. Dave Lim||Curator and Founder|
- 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
- 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.
- The xConnect social networking platform will be mainly connecting Singapore users during the testing phases of the project.
Development Tools & Technologies
Team's Collaboration Tools
Project Milestone & Schedule
Project Meeting Minutes
Project Risk Management
Risk Management Process
Risk Assessment Table
|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||
|2||Project outline changes from client.||L||M||B||
|3||Team members is unfamiliar with deployment platform.||M||H||A||
- Resolved Rate (x) = Number of bugs resolved / Total number of bugs found
|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
- 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.
|x > 20||Minor||Minor Stress Levels|
|x > 25||Major||Major Stress Levels|
|x > 30||Critical||Critical Stress Levels|
- Stress Metric Action Plan
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.
|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
- Factor (x) = Actual time taken (Days) / Planned time (Days)
|x < 1||Ahead of Schedule|
|x = 1||On Schedule|
|x > 1||Behind Schedule|
- Schedule Metric Action Plan
|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|
- PM evaluates after every iterations:
- Evaluation based upon:
- Contribution to group goals
- Task accomplishment
- Consideration of others
- Contribution of knowledge
- Group cooperation
- Scores(1 to 4)
Use Case Diagram
Solution Architecture Diagram
User Acceptance Testing
- To be filled
- To be filled
Overall Group Learning Outcomes (LOMS)
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
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.