On our team's problems

We, being a multi-culture group, have been going through half of the semester. At the moment, I'm glad that we have done our job well. I have good experience working with you. And more time spending with you, I have more chance to realize some problems which we can improve. I want to have a clear sight into it.

First of all, we are lucky to be in a group where every member is strong in IT. However, that also means that we have to consider clearly to choose the best idea when discussing something. Let's take the GUI meeting for an example. When discussing about the features and how the GUI should look like, we have a lot of different ideas, all are interesting. I understand that you have good knowledge in IT and always have some solution to a problem, but if we can listen to each other and understand him a bit better, then perhaps we could have come up with more interesting ideas in our project.

This is a common problem faced by all teams, when all member are good at something in common, and it can be definitely resolved. We should listen to each other's ideas carefully and understand its pros, cons before we make any comments on that. We are all doing heavy work in this semester: Zhou Jun taking 8 modules, the other 3 taking CS2010, which requires a lot of coding efforts, so we don't have much time for meeting. Perhaps at this moment, each of us have personal stuff to do. Like me, I'm working on a NUSSU project and working part-time. But in the next weeks, when we have come to the coding stage, I think we have to meet more regularly and by then, we should have more time to discuss problems more carefully.

It is not something very serious and I think we can resolve it. It is a common problem that must be solved in order to improve teamwork ability. We're a great group, doing a great job and I believe we can pass all problems and go further in this project if we put more effort.

Insights into one of our problems

As I had pointed out earlier (in my previous blog post), being a team of like-minded people helped us gel as an outfit in the early half of the semester. We were to find out later that this by itself was one of our biggest shortcomings.

Let me expand on this problem. All of us are alike on many different fronts. Both while separating topics for our oral presentations as well as dividing responsibilities for our project, we found out that all of us were intent on taking up similar tasks/responsibilities. This was because our skill sets overlapped significantly. All of us are good programmers, natural leaders, speakers more comfortable while presenting topics with heavy content rather than abstract ones and so on. This is a problem as it restricts our variety to a great extent. An even bigger problem arises when we are left with no choice but to pick tasks outside of our comfort zone. This is bound to happen as we need to do a variety of subtasks for each submission with limited resources at hand.

We could solve this problem by proposing a system wherein a person can ask for what he/she wants and will be assigned the task on a first cum first serve basis. Still, this solution does not work fairly as team members who are extroverts tend to gain an advantage over others as they are the ones who generally speak out first. A possible advantage of this system is that it gives the silent members of the team an incentive to speak out thereby indirectly enhancing their communication skills. The least we could do is to ensure that the same guy does not suffer every time.

Every coin has two sides. Even this problem has helped us in certain ways. We were forced to move out of our comfort zones on a few occasions and hence were exposed to newer things. In this process, we had an opportunity to explore newer arenas which may be to our liking. I am quite sure that we wouldn’t have taken the pains to experiment otherwise and thus wouldn’t have realized our full potential.

Personally, I feel that I have gained a lot in this process. Opening presentations was not my forte. I now feel more confident when I am opening presentations. If I had been given the choice, I wouldn’t have opened presentations and thus would not have realized that I actually like it.

This problem – a result of our team composition – cannot be avoided but can definitely be resolved. It is our responsibility as a team to ensure that no team member suffers extensively because of a conflict of interest. I can tell that we are proceeding in the right direction from the way we have split tasks for our upcoming submissions. Hope that this good work continues!

We need to make more efforts

We, as a wonderful group, have gone through half the semester. I do believe that we have done a really good job and everything goes well. However, since we are trying our best to be the best group, I still want to point out an aspect we can improve, which is the effort we make for this project.

In this semester, every one of us has a very heavy workload from other modules. I have 8 modules to study and the other three take CS2010, which is difficult and requires a lot of programming efforts.  As a result, we have to spend less time and efforts on this project. However, this project is really important and need more time and efforts.

We must first keep in mind that this project is related to both CS2101 and CS2103, which worth 8 MCs. With so many MCs, it deserves more time and efforts. Moreover, for most of us, this project is the first time we work like real software engineers and we can learn a lot about software development. This opportunity is quite important for us and we should try our best to learn as much as possible.

This project has no quizzes and weekly progress requirements, but this does not mean we can spend less time on it. Since the total workload is almost fixed for us, if we do less now, we need to make up in the future. Then, the project can become a final week project and we need to rush a lot. As a result, the quality is low and we have to interrupt our plan of other modules. This is quite terrible and we should try to avoid it by completing tasks as early as possible. Therefore, we need to make more efforts on it.

Now we have come to the stage of coding, which is the most important part of the project. I hope we can spend more time working together, discussing problems and communicating. We may have to squeeze the time of other modules, but the project worth it. I think the meeting today is quite a good beginning. By the two-hour meeting, we have made clear of the components we need to implement in version 0.1 and the parts for everyone to code. As the work gets more complicated, we really need to work more on this project, programming, writing reports, discussing problems, etc.

Now we have fell behind many groups in progress since we did not do any extra works, but it is still under control. Let’s work more from now on and catch up. I do believe we will do an excellent job for this project in both CS2101 and CS2103. 

A Particular Problem Faced By The Team

There are many challenges and problems the team faced during this period of time. And as our team approaches the halfway mark of the project, I would like to highlight this particular problem that I as the team leader feels the team should address.

And the problem is, the team is too casual and laid-back at times. While this can be a good thing but at the same time it can be disastrous as well. Our team's laid-back and casual approach is most likely caused by our very own doing and that is our own abilities. Our team is very fortunate to have every member being strong in a lot of areas of work in the project. And this leads to the emerging problem of being too casual and laid-back. Members of the team have been excelling in the task that are assigned or handed out to them. As a result the team started to develop a laid-back and casual stance. This problem might develop and become difficult to overcome or to handle in the future. I felt that being this laid-back might be harmful to the progression of the team in the future and might really be detrimental in the long run. As we approach the toughest phase of the project, being this laid-back and casual would only harm the quality of the work that is produced.

However being casual and laid-back can be a positive thing as well. Being casual and laid-back allows the team to remain calm and not to panic when the going gets tough. Since everyone in the team is confident of their abilities and the work they have produced so far has been of great quality, being laid-back and casual might actually be a positive thing to the team.

To be this casual and laid-back allow the team to look at things in a bigger perspective. To come up with ideas or ways to solve a problem. Unconventional ways that could have easily solve the problem could be thought of in a less stressful environment.

Being laid-back and casual allow team members to express their views freely. This is a good thing given that a lot of creativity is needed and is involved in the project. Competition is tough, with all the groups in the module developing the same program. Therefore to beat the other groups out there, is to come up with something different, creative and intuitive. With this current attitude of the team, it allows the team not to be affected by the tough competition out there. But rather to have full focus on our own project. The high level of competition does not get to us and as a result every team member is happy and focused on his job.

However so, this problem has solutions to it. One of the many solutions to this problem is to encourage the team to strive to be the very best. To make use of this casual and laid-back attitude of ours to our advantage. Being the team leader I would want to motivate the team members to beat the best group out there. By doing this, it does not crank or jack up the stress level of the team and at the same time overcomes the problem. This is just one of the many possible solutions to the problem.

Having presented this problem, I would like to close with this. It is good to instill some urgency into the project group. To always keep the team on its toes and to be the best team out there. This is to prevent the team from taking this laid-back and casual approach to the other end of the highway.

Shawn Teo Chee Yong