Sandbox‎ > ‎Archive‎ > ‎IPT 2008-09‎ > ‎Ria's Page‎ > ‎

4 Nov 08

Advantages of teamwork

Increased productivity. 
When a group is given the same amount of work that an individual may be required to do, time is a major factor that is saved which can also result in minimal use of resources over a shorter time, resulting in a smaller bill. Allocating specific parts to the members of a team, drawing on both their strengths and weaknesses allows also the quality of the work produced to be at a higher level. This will also meantally effect the members of the team, giving them confidence within themselves and with their peers, building working relationships.
An example would be Mr. Woo allocating people into specific groups in THE SYLLABUS PROJECT, though using mathematical tricks, Mr. Woo made groups based on the bulk of the work, making it more time efficient. The Content Team was significantly larger than the Proofing Team, this was due to the larger amount of work and time that needed to be spent to evaluate the contents.
 Enhanced job satisfaction. 
As mentioned before, working in a team not only increases effciency in everyway but allows each member of a team to feel satisified with their work and the overall team's work. This also provides each member of the team to experience other ideas put forward by different members of the team and see things though a different perspective, growing in confidence and as a future servant of the workforce. It allows you to experience a system that is much greater than one person but able to cater to the needs of everbody.
An example would be the projects that were given to us last term that asked us to create our own information system within a company or shop, working with Parth and Lakmitha allowed me to experience and understand the definite proceedings in order the establish a tea company and sustain it.

The development of a quality system. 
A system is a collection of different parts that work together to achieve a common purpose or goal. In a team. the normal practice to seperate a project into subsets that are divided and carried out by the members of the team. Working in a team rather than working as an indivivdual tests tha boundaries and success rates of different people doing different parts of a job for the same outcome. It allows the individuals to experience first-hand the creation of a system and ways in which to approach certain aspects of a project. If problems do arise, the collaboration of the team can reach far better conclusions than that thought of by one person. Providing a quality system as an end result, the different perspectives of the members and the unique conclusions that can be made allow the system to be iconic and be embraced by all types of end users.
An  example would again be THE SYLLABUS PROJECT which was divided between the IPT class, incorporating different peopple so that differnt approaches could be taken to certain activities, trsting which would be most effective in reaching the goal. The Content Team may have sort out their work ina way that they found to be efficient and when it is passed onto the Proofing Team, it may be interpretated differently. The finished project may slightly vary from the ideas of each of the members, but it must be considered that it is a collective project. 

Social & ethical issues

Individual privacy. 
Working in a team allows the details of a particular member to be more vulnerable, as it is available to more than one person. This increases the chance of information about a particular person to be leaked out and used for other purposes than what was initially meant, eg. used by phnoe companies.
Data security. 
The data that is produced can be accessed very easily by any member, at any stage of the process and any time of the day. Data which is not secured through encryption, archiving or any other means is susceptible to "exposure" and manipulation.
Need for complete documentation. 
The documentation of the process of the system is a vital part that adds creditation and reference to the information, giving the end user a reliance that the information is correct and can be trusted in use for their purposes. Anither reason why continual documentation is very important is because it allows end users to refernce the information that you used and evaluate any concerns that may have arisen. The information produced normally comes from thorough research, people using the system should be assured that all information is right and trustworthy.
Think of additional issues (I can think of at least three more major issues - you should be able to think of even more!), and explain each.
Information in a system can be altered both intentionally, to produce misleading results and untrustwothy research but it can also be accidental, this cann occur if a survey carried out did not ask questions directly related to the project or an interviewer asked the wrong questions. Whatever may be the intention, bais information can have devastating impacts on the project, making it untrustworthy and useless to end users.