Team work is an interesting topic in the realm of Software
Development. It is often a sticking point for most projects due to team work
issues and can be difficult to change your perspective on a project if you have
been working on the team for a while. Quickly I have found I can add labels to
certain team members early on. Most of my experience working in a team has been
through University, which I have always considered not a realistic
representation of a team. I say this because each student has different
aspirations and wants a certain grade. They often will do the amount of work
required to get that grade.
Becoming The Work
Horse
Some of the problems I have faced with the group projects I have been on in the past is that I tend to take on the bulk of the workload. This is generally my own fault. I have a tendency to ensure the project is completed in ample amount of time before the deadline therefore the core functionality of the product is completed early on. However sometimes this has resulted in doing a lot of work for myself instead of helping other team members out in their problems and difficulties with their code. This has led to situations where it is clear in the group who is doing all the work which can cause a divide. Moving towards the future I would like to spend time helping other team members in a goal to making the team more productive.
Some of the problems I have faced with the group projects I have been on in the past is that I tend to take on the bulk of the workload. This is generally my own fault. I have a tendency to ensure the project is completed in ample amount of time before the deadline therefore the core functionality of the product is completed early on. However sometimes this has resulted in doing a lot of work for myself instead of helping other team members out in their problems and difficulties with their code. This has led to situations where it is clear in the group who is doing all the work which can cause a divide. Moving towards the future I would like to spend time helping other team members in a goal to making the team more productive.
The Know It All
Another reflection I have made from my experience in working with teams is that I sometimes don’t deal well with loud, brash, abrasive members of the group. I wouldn’t get in to conflict with them but I would instead reject their ideas and opinions rather than listen to them. I tend to find it frustrating when someone appears to know every single way to approach a problem, “We should do it this way. We should use this software. Why should model it that way”. To be fair most members of the group would agree this person was ignorant and difficult to work with. However on hindsight I should have possibly said to this team member that I appreciate their wide range of knowledge but the way they communicate their ideas across to the team can come across obnoxious. Forbes released a great article on dealing with these kinds of people.
Another reflection I have made from my experience in working with teams is that I sometimes don’t deal well with loud, brash, abrasive members of the group. I wouldn’t get in to conflict with them but I would instead reject their ideas and opinions rather than listen to them. I tend to find it frustrating when someone appears to know every single way to approach a problem, “We should do it this way. We should use this software. Why should model it that way”. To be fair most members of the group would agree this person was ignorant and difficult to work with. However on hindsight I should have possibly said to this team member that I appreciate their wide range of knowledge but the way they communicate their ideas across to the team can come across obnoxious. Forbes released a great article on dealing with these kinds of people.
The Quiet One
Another team member you all may be familiar with is the quiet one. It is frustrating to see someone attend meetings consistently but have no input. For someone like myself who is quite social, I try my best to interact with this team member by asking them direct questions and trying to keep the conversation as open as possible so they feel comfortable in talking. However still you wish they could contribute more and help the team progress. In the future I could perhaps enforce going round in a circle asking everyone the same question about what is the latest they have developed. Like a scrum meeting. The great thing about this person is that they listen loads but you wish they could digress some of their opinions on how to approach problems and move the project forward.
Another team member you all may be familiar with is the quiet one. It is frustrating to see someone attend meetings consistently but have no input. For someone like myself who is quite social, I try my best to interact with this team member by asking them direct questions and trying to keep the conversation as open as possible so they feel comfortable in talking. However still you wish they could contribute more and help the team progress. In the future I could perhaps enforce going round in a circle asking everyone the same question about what is the latest they have developed. Like a scrum meeting. The great thing about this person is that they listen loads but you wish they could digress some of their opinions on how to approach problems and move the project forward.
The Procrastinator
The final team member I have come across that I haven’t particularly had problems with but wish they worked in a different manner. The procrastinator often is happy to help and does show interest in the work at hand however they choose to leave everything to the last minute and always have an excuse. Again everyone works differently and that’s ok however pushing a change to Git, minutes before a demo can give everyone a heart attack. In future I could create group deadlines and try enforce that team member to adhere to those. Previously I had tried consistently messaging the person about the feature they said there were going to add which seemed to have no progress.
The final team member I have come across that I haven’t particularly had problems with but wish they worked in a different manner. The procrastinator often is happy to help and does show interest in the work at hand however they choose to leave everything to the last minute and always have an excuse. Again everyone works differently and that’s ok however pushing a change to Git, minutes before a demo can give everyone a heart attack. In future I could create group deadlines and try enforce that team member to adhere to those. Previously I had tried consistently messaging the person about the feature they said there were going to add which seemed to have no progress.
In conclusion I think it is good to reflect on problems you
have associated when working in teams to allow yourself to improve for the
future. Of course there have been plenty of times I have contributed effectively
towards the team but this isn’t what this blog is about. Again these problems
have all occurred in a University environment which is almost like a simulated
reality of teams in the work place were individual consequences are more
severe. The saying you can bring a horse to water but you can’t make it drink comes
to mind when I think of some of my University projects. However I do believe it
is good to reflect.
CasinoDaddy.com: Don't forget to follow the
ReplyDeleteCasinoDaddy.com: Don't 김해 출장마사지 forget to follow the 문경 출장안마 latest developments. CasinoDaddy.com, 성남 출장샵 the best place to connect 원주 출장샵 and 대전광역 출장샵 support one another.