Monday, March 8, 2010

Post 4.1: CG1102 Meeting Video - All about me!

Note: In the x.1 posts, I'll be reviewing the previous post and comments while also touching on points I might have missed.

As mention in the original post, I have pointed out several points regarding my body language. This time I will touch on my role in the team.

Looking at the video, I seem to be playing the role of supporter. Most of the time, I came up with the methods to implement the functions instead of coming up with the actual idea for the functions themselves. I would have to be more active in providing ideas in future meetings.

I also realised that I ask questions quite often to help clarify my doubts or to bring up points that I felt were missed. While this is a good habit, since I make sure that I do understand what direction we are going with in the project, some people might be irritated by this since they would have to keep repeating or explaining themselves.

A simple checklist for my personal actions during meetings:
  • Keep watch of my facial expressions
  • Control how I place my hands
  • Be more active in providing solutions, not steps for the solutions
  • Keep asking questions - Try to act as the "what-if" guy in the team


Thanks everyone for the comments. I'll try and put into practice the suggestions made.

While I did read through the lab, I could actually wrote out a pseudo-code/actual code before the lab so I had something to refer to and suggest for future meetings. Also, we would have to adjust our sitting plans in the future. As Ganesh suggested, allowing everyone to view the screen would allow greater participation for all members.

1 comment:

  1. Hi Rayner,

    The role of the supporter is just as important as any of roles in the team. I feel that it is ok to clarify any of your doubts about the lab; you just need your teammates to understand your situation. Explain to them that you need time to digest the discussion. I guess you would not want to misunderstand the question and proceed to do something wrong. The unpleasantness in correcting the mistake would definitely be higher than the clarification process.

    As for providing the solution, I believe that your strength is in the implementation. Your other teammates may be better at the general solution while you could focus on the details. The group can complement each other strength and weakness.

    Regards,
    Kevin Lin

    ReplyDelete