We recently had our first CG1102 Group Project Meeting. I apologise about the audio quality. We were using the laptop to record and there wasn't an external microphone.
First off, I would like to clarify some points/words that were used during the video in case anyone does not understand programming terms.
Variables - These store certain values or inputs and have to be given a type.
Private variables - These are variables, which are found in classes, and can only be changed through functions
Function - Functions are a series of commands that will work with your data.
Class - A class is a set of variables and functions that limits how a user can access and change the variables stored.
Inheritance/Inherit - The class that is inheriting the other will be able to use the functions and variables in the previous class.
Before the video, we had done some slight discussion regarding how several topics that we were unclear of. We also shared some of our initial ideas about how we thought the project would be like.
After reviewing the video, I realised that my expressions seem to portray that I was angry throughout most of the discussion even though I was just thinking. I guess this is a part I have to work on since people might get the wrong impression that I am upset or rejecting their ideas.
I also tend to cover my mouth with my hand when I think. While this shows that I am actively thinking, it also muffles my voice when I speak, which could then cause miscommunication since people might not hear what I said clearly. I would have to keep check of my body movements in the future too.
Overall, I felt that this meeting was slightly unproductive. I still had some uncertainties regarding the program design. Also, we didn't have a time keeper to keep us on schedule and this caused our meeting to run late. I believe we will have to revise the way the team conducts its meetings, and for me, my body language, for future meetings to improve.
Subscribe to:
Post Comments (Atom)
Hi Rayner,
ReplyDeleteThe filming part was hard for every team I guess; at least the effort was made to produce it. At first, I felt that your team was a bit camera conscious, but you all were in the mood of the discussion not long after that.
It is good that you noticed about your non-verbal gestures and expressions. Doing the clarification now is good since your teammates will be able to understand them in the future (when they read your blog post). The part where you explain some of the technical terms is very useful for people who do not have prior experience on C++ programming. (For the CG1413 lecturers and other people who views the blog)
From my point of view, the cause of unproductiveness may be because of the presence of the filming which made everyone uncomfortable. The preparation work (understand the question /task beforehand) may not be perfect. Anyway, do not be discouraged. It was the first meeting and some things would definitely go wrong (applies to all team).
That was why we need to do the filming! Knowing our mistake now and improving on them soon would be better than to leave it and then let them affect the overall performance of the project. Anyway, good job! Keep it up. I believe the performance of your team would only get better and better.
Regards,
Kevin Lin
Hi Rayner,
ReplyDeleteDespite the flaws that you had pointed out, I feel that your team had done an excellent job of listening to each other. Of the parts I reviewed, there were almost always only one person speaking at a time. :) This ensures that everyone will get to listen to the inputs of any one member. :)
Towards the end of the meeting, when one of your other teammate returned from answering a phone call; I feel that you should had taken the initiative to update him on the course of the discussion. Despite that though, I haven't noticed any other flaws.
Active listening is integral to the success of any team meeting, and I applaud your team for being good listeners. :) Whilst this particular meeting may had been unproductive for you. I feel that, with the camaraderie between your team, you guys will be able to pull through! :)
All the best! :)
Yours sincerely,
Juncheng Chen
Hi Rayner,
ReplyDeleteYour idea of putting the programming terms in the beginning is good. It would certainly help many people who do not have a programming background reading your post.
After seeing your video, I think that your team could choose a better venue where you could see each other. Moreover, you could keep the laptop in between making it easier for your teammates to look at the coding.
I think your team members are good listeners. You tend to listen to your teammate very carefully, think critically and then voice out your opinion. Though I think you need to work on your non verbal cues like your gestures and your expressions.
Confusions during the meeting can be avoided by preparing for it before hand so that you have a clearer picture of the discussion going on. Time management is very important and the team leader should take the charge to ensure that you devote time to each topic effectively. Your team should work on those things.
It was just the first meeting and you need not worry that the meeting was ineffective and unproductive. As time passes by you will have better and more successful meetings .Try to work on the mistakes.
I feel that there were some typos in your post so do pay attention while writing your post.
:) :)
Best Regards,
Nitika
Hi Rayner,
ReplyDeleteThanks for the comment you left on my blog. I will take note of the pointers you gave and work towards these improvements.
It is good that you have explained the terms you and your teammates have used in the video. It will help people without programming background to understand your video better. They may not get too bored from watching a video which they do not understand half of the terms used.
I am glad that you realized that there are some nonverbal cues that will disrupt the message you are trying to send across. Do take note of such cues and try to avoid them in future.
Could it be because that you are unprepared for the meeting which results in having uncertainties regarding the program design at the end of the meeting? If this is the reason, you may want prepare before each meeting and clarify your doubts with your teammates before each meeting.
Hope my suggestion helps.
Li Hua
Hi Rayner,
ReplyDeleteAfter watching parts of your team's meeting, I thought it was quite an effective meeting. All of you looked comfortable and connected well with each other. I liked the fact that you guys shared a few chuckles here and there instead of being serious throughout the entire meeting.
However, I feel that that the laptop should have been in the centre so that the other two members would have a much clearer picture of the code and can communicate their thoughts and opinions effectively. In the video, the team member furthest away from the laptop (Junius) could not get a view of the code and thus looked disconnected and disinterested at times. This could be a hinderance to an effective team meeting.
As for your non verbal cues, I thought it was not too bad. As long as your team members are able to understand you, it should not be much of a problem.
Finally, if you feel that the meeting was not productive and still feel confused, then during the meeting I suggest you should clarify all your doubts and confusions. Confusions occur because different people have different interpretations of the task. Sharing your thoughts with the team and receiving their feedback will ensure that you are headed on the right track.
Hi Rayner, your team mate here. This is a good reflection as it was detailed in where the problem was, why it was even a problem and finally, the most important, the steps you will take to overcome the problem.
ReplyDeleteI feel that the meeting did not drag any longer than it was necessary to get everything done. It was well under an hour and there were no awkward long pauses.
I realised that you could have also stated some of the good points of the meeting and suggest improvements for it. I believe that there is nothing that needs no improvement.
Regarding your body language, I would like to take this opportunity as a team mate to reassure you. I practically did not even notice it. Even if I did, it was pretty obvious you were in deep thought and I am sure Angad understood too.