Thursday, January 26, 2012

Blog1# Communication and Team Behaviour

We have discussed 5 most important attributes of an effective team player and 3 most vital qualities of a team leader in class last week. Beyond that, an effective collaboration team requires two more important elements: effective communication and team behavior.

Firstly, effective communication helps us solve problems, establish trust between each other, and create environments where innovative ideas, conflicts resolving, and important decisions can flourish. According to my observation during our group meeting , I summarized three principles of effective communication here. First principle is 'Practice active listening'.  Active listening can make the speaker feel heard and respected, which can help build closer and deeper relationship among team members. Furthermore, everyone can feel comfortable to exchange ideas, opinions and openly discuss issues in a creative manner. Second principle is 'Use nonverbal signals'. We can make use of nonverbal communication, such as body language, eye contact, laughter, volume, tone or turn-taking to enhance verbal messages that we want to express. Last principle is 'Quick stress relief'. If we are in the middle of a meeting and recognize that we are becoming stressed, looking for humor appropriately is a good way to take a moment to calm down. I believe managing principles of  effective communication will enable us to understand a person or situation better (Robinson, Segal, & Segal, 2011).

Secondly, effective team behavior is the integration of effective team players, team leader and effective interpersonal communication. Each element works both individually and collaboratively. As a team player, he/she can communicate constructively, listen actively, shares openly and willingly, cooperate, show commitment to the team. As a team leader, he/she is capable to make quick decisions, motivate team members and deal with conflicts. In addition, every team member including leader should be able to communicate effectively, so that the whole team can work together to achieve the same goal.

Last but not least,  I found there are two aspects that I can improve on to contribute team work better after examining myself. Generally speaking,  I'm an effective team member, who can respond to requests for assistance, put in good effort in team project, cooperate with  others to accomplish a job together and would like to share my information openly. To be honest, I 'm not a good listener. Sometimes I interrupt speakers to show my agreement or disagreement without allowing them to complete their sentences. Sometimes I may require others to repeat their explanation or questions due to not concentrating listening. The second aspect I can improve on is language. I realized the language barrier of intercultural communication does affect the effectiveness in discussion. For example , my first language is not English. I need to overcome language barrier to express my ideas accurately with a second language, which sometimes slows down our team's discussion progress by spending longer time in explanation to make sure we understand each other clearly.

To sum up, I will put my effort in improving my communication skills according to the study of module CS2101 and overcoming language barrier to contribute to our team in a more effective manner.

Bibliography


Robinson, L., Segal, J., & Segal, R. (2011). Effective Communication.
Thenmozhi, M. (2009). Group Behaviour. Indian Institute of Technology Madras .






Friday, January 20, 2012

Our first meeting for CS2103T project


Posted below is minutes of our meeting for CS2103T project today. After reviewing the content of today's meeting, I have to say we are amazing! As you can see, we've iendtified a clear purpose of this project, sketched out the basic structure of our program and cleared understanding problems with Dr.Bimlesh this afternoon. I'm glad to have Darren and Qin Chuan in the team and work together with them. They both have few years experience in programming and help me broaden my vision in analyzing problems during our discussion today. I hope we can keep a cordial working relationship this semester and try our best to design a good qualified product!
Happy Chinese New Year to all of you!
<> <> <> <> <> <>   <> <> <> <> <> <> <>

Analysis and Planning for CS2103T Project


Minutes

20/01/2012

13:20~14:20

COM2/108



Meeting called by
Darren-Gavin Ho

Type of meeting
Problem-solving, planning

Facilitator
-

Note taker
Zhang Xi

Timekeeper
Teh Qin Chuan

Attendees
Darren-Gavin Ho, Teh Qin Chuan, Zhang Xi



Agenda topics


 

1. PURPOSE OF CS2103T PROJECT

 

Discussion


  • Our program will be designed as a desktop utility, which provides a systematic solution for event organizer to book venue, plan event, calculate budget, broadcast events and receiving registrations from both facilitator and participants.

Action items
Person responsible
Deadline

-
-
-



 

2. REQUIREMENT ANALYSIS

 

Discussion


  • Model the process of organizing an event and sketch out the flow chart

  • Identify types of users: Organizer, facilitator, participant

  • Identify main functions of the program:
ü  Organizer: create, delete, modify events
ü  facilitator/participant: subscribe events
ü  Retrieve and display latest event information in user interface

  • Analyze the required information to create an event:
ü  Name of event
ü  Venue
ü  Time
ü  Content (flow of programs to be held in the event: time,programs)
ü  Budget calculator (items to buy: food, prizes, gifts etc)
ü  Facilitator (limit number)
ü  Participants (limit number)
ü  Submit/ Save as draft

Action items
Person responsible
Deadline

  • To research on the problems of organizing an event
  • To add in necessary functions based on research result
All attendees
Ongoing





 

3. SYSTEM DESIGN

 

Discussion

  • In order to apply OO techniques, we decide to store all the information in view of objects in text files and create a fold called 'database' to keep all text files, instead of using any database servers
  • Darren proposed to design the program with 3-tier model :
ü  GUI
ü  Controller
ü  Actual program code
  • Data structure : Array list

Action items
Person responsible
Deadline
  • Think about algorithms/computations
All attendees
Will be discussed in next meeting
  • To research on calendar implementation (flash, table or other tools)
All attendees
Ongoing

 

4. PROPOSAL COMPONENTS

 
Discussion

  • Components to be included:
ü  Problem statement, solutions
ü  Case Diagram
ü  Domain Model (UML)
ü  Mock user interface
ü  Sample input data
ü  Sample output data
ü  Implementation schedule

Action items
Person responsible
Deadline
  • Details and delegation of work will be discussed in next meeting
-
-