Mango team was randomly allocated to their group and was dispersed across four states. The task was to complete a group project that answered the question with reference to a major internet business “What is the fundamental basis of internet commerce?”
Processes, Tasks and Goals
Initially the project involved members meeting online, identifying strengths and weaknesses and determining availability. Assignment 1 provided the focus for the tasks which included:
• reviewing collaborative tools;
• trialling alternatives;
• polishing collaborative skills and
• developing team cohesion.
As the team moved into Assignment 2 they established clear objectives, identified goals and established the key milestones to be achieved. After some preliminary research and discussion the team came to a consensus about the:
• collaborative tool: Tikiwiki http://info.tikiwiki.org/tiki-index.php
• case study to be researched: Amazon.com
The team used the mind mapping program Freemind [http://freemind.en.softonic.com/] to brainstorm the tasks.
During the project members:
• researched;
• shared and analysed findings;
• provided feedback, support and motivation to other team members;
• collaborated on the wiki;
• analysed the feedback on the draft project;
• made decisions about the presentation;
• communicated online: asychronously via blackboard, e-mails, forums and discussion boards within the Tikiwiki and synchronously during bi-weekly Skype meetings and web conferences (Go-To-Meetings) http://www3.gotomeeting.com.au/?c_name=google&c_mark=all_keywords&c_prod=g2m.
Effective handling of scheduling, fulfillment of tasks, meeting and readjustment of milestone.
The Mindmap created a flow chart of activities and timelines in a systematic fashion giving direction to members as they undertook research throughout the assignment's duration.
Bi-weekly meetings online via Skype were where most ideas and scheduling took place in a coherent manner as we could collaborate in realtime about the focus of our project.
Reviewing the Mindmap and other visual representations via Gotomeeeting.com during our Skype meetings enabled the team to reflect upon its direction and fulfillment of tasks.
We were able to monitor the progress of the project by viewing additions and updates to the Tikiwiki. We were also able to pass on any relevant feedback and advice via that channel.
There were naturally some re-adjustments to what we considered our milestones and these were generally communicated via email (flagged as urgent) or discussed during the Skype Meetings. These only occurred if we felt that there was no argument compelling enough, a lack of references, unoriginal etc.
Effective decision making processes, critical meetings and dialogues
Mangoes project team manifested effective decision making processes throughout project stages. Project team explored feasible project options and defined the project’s objective. The team also collected project relevant information and evaluated implemented project inputs. A team approach was put into a good practice when converging on a solution required for the project’s progress. Some project’s stages required more attention due to complexity of the tasks. This was demonstrated by spending more time at the meeting or arranging extra meetings addressing project’s critical tasks. Project team members were based in different time zones; however, it did not place an obstacle in project team communication and project deliverables. Being in the same time zone would be more beneficial in synchronizing team members’ availability. Project team member’s flexibility and commitment enabled the project to move forward using constructive communication through Skype and e-mail.
Effective management of different views and setbacks
Project team communication through Skype and e-mail was conducted effectively. Each member was given an opportunity to express her/his views, ideas and suggestions during meetings or through e-mail. There was enough space for individual contributions on Project Mangoes website communication links e.g. reference material contribution, journals, comments etc. Different views were accepted as part of the project participation and were managed very well by the whole team.
Thet team experienced occasional setbacks that were managed very well by the project team members. One of the setbacks was an absence of appointed project website administrator that occurred during final stages of the project work draft presentation. There was some technicality that needed to be resolved on the website. Another setback was experienced during meetings that went ahead despite insufficient number of project members in attendance affecting project milestones progress. However, loss of time was usually recovered through team’s innovative and productive input at the following meetings.
Collective Response
The project is a collective response where each member:
• participated in the communication processes by contributing ideas, engaging in discussions, seeking clarification and directions and providing positive support for each other
• undertook research and shared findings on the wiki and provided feedback on the information collected and future directions of the project
• edited and refined the responses for final presentation.
The team demonstrated strong loyalty, cohesiveness and harmony throughout the project.
Closure
The project was an excellent opportunity in gaining new valuable communication skills in team environment and how to use modern technology effectively through distance communication. Team displayed incredible amount of flexibility and initiative during relocating the project content from tikiwiki to wikidot. This occured during final days leading to project work submission.
