I-Crop Project: Teamwork, Communication, and Reflection Report

Verified

Added on 2024/07/01

AI Summary

This report details the teamwork, communication strategies, and reflection involved in the i-Crop project, an online cash marketplace platform developed by Virtucon and Globex Foundation. The project aims to create a digital platform for grain sellers and buyers, enhancing crop export and purchase. The report outlines the team structure, roles, and responsibilities, including the necessary skills for each role, such as project director, web developer, and finance manager. It describes meeting schedules, communication methods, and rules for the project team, emphasizing user requirements, active participation, and ethical conduct. The report also includes a communication plan for stakeholders and personal reflections on the teamwork experience. The project seeks to address issues like unstable internet connectivity and provide a user-friendly interface accessible via both website and app.

Teamwork and reflection

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Contents
Introduction.................................................................................................................................................3
Part one: Description of project.................................................................................................................. 4
Description of the Project:................................................................................................................... 4
Team character:................................................................................................................................... 5
Team communication:......................................................................................................................... 8
Part two: Learning Cycles.......................................................................................................................... 11
Meeting structure and outcomes..........................................................................................................11
Part three: communication plan................................................................................................................ 14
Stakeholders.......................................................................................................................................... 14
Communication plan for i-Corp............................................................................................................. 14
Part four: Reflection.................................................................................................................................. 16
Experience of teamwork........................................................................................................................ 16
Conclusion:................................................................................................................................................ 17
Reference list:............................................................................................................................................ 18

Introduction
Globex foundation was initiated by the merger of two big organizations known by the names of Riverina
Precision Farming and B T & Sons Farming Equipment. In the year 2013, these two organizations merged
together to form the Globex foundation and are situated in the Riverina Region of NSW and also has
three more locations in Albury, Griffith, and Wagga Wagga. Globex foundation is a very old working
partner or client of the Virtucon and with Virtucon Globex foundation is working on a project
management to develop an online cash marketplace platform- i-Crop. this new system that will be
developed by both Virtucon and Globex foundation will be a new platform to promote the growers and
buyers and bring them on the same platform, this is a new kind of platform as there is no other platform
for the sellers and buyers of the crops.

Part one: Description of project
Description of the Project:
Subject Description of subjects
Name of Project Online cash marketplace platform-i-Crop
Show Name
Company Associated 1
Company Associated 2
Location
Project Branch
Team Name: XYZ
Team Details
S.No. Members Name Phone Number
1. Member 1
2. Member 2

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

3. Member 3
4. Member 4
Project Brief:
Globex foundation and Virtucon are the long-standing work partners; Globex has been the client of the
Virtucon for a long time. Together these two organizations have now decided to develop an online cask
marketplace platform that will be known as the i-Crop. i-Crop is a completely new project of its kind and
it replaces no existing project. I-Crop is a platform for the people who either grow grain crops or buy the
same. This is a platform that will bring both grain seller and buyer at the same place and will help in
managing the sales of the warehouse grain crops. The Platform will be available on both the website and
app form, it will make it easy for the sellers and buyers to access the interface from anywhere and
anytime. Also, the interface of the system will be user-friendly and it will be according to the needs of
the sellers and buyers. This will increase the export of the crops as the access to the platform will be
available from both mobile application and websites. Also the problem of unstable locations of clients
having either the best or the worst internet connectivity, Globex wants i-Crop to have a solution for the
transactional issues that can occur due to the internet problems. Globex i-Crop will have many other
features besides the feature of transactions.
Project Objective:
The objective of this project is very simple and user based. The company wants to provide a digital
platform to the sellers or buyers of the grains. Generally, when a farmer grows crop it is either sold to
the local vendor of the crop or to the big stakeholders of grain business. This kind of practice generally
causes a major loss to the farmer family as the price paid is very low or approximately null. Also, there is
one more problem with grain, the storage problem. The storage of grain requires too many precautions
and a big area, which is not available with the farmer. So selling the crop to the vendors/businessman is
the only option they are left with. But, if i-Crop comes into action, the farmer will be able to sell its crop
to anyone he wants just by displaying the price of the grains. Not only grains but i-Crop will become a
platform for the sale of any seasonal crop and will open the gates of the national/international market
for the farmer without going anywhere. This will bring a revolution in the field of crop export and
purchase (Kerzner, & Kerzner, 2017).
Team character:
Knowledge required and skills:

S.No. Responsibility Skills and knowledge required
1. Project director  Should know how to manage and lead the
team
 Should have the skills of work
management
 Should have the best communication skills
and negotiation skills
 Should have the ability to manage and
take risks
2. Web developer  Should have the skills of managing the web
environment
 Should be a master of HTML and CSS
 Should understand the client requirements
and interface needs
 Should be able to convert the codes into a
working website
3. Application developer  Should be a master of Android/IOS
development and XML
 Should have the ability to merge complex
functions into the simple environment
 Should have the ability of understanding
user needs
 Should be able to convert the code into the
working application
 Should also have the knowledge of the
Java core and advanced
4. Business analysis in charge  Should completely understand the user
needs and be able to provide a solution to
user problem
 Should have the marketing skills which will
help grow business for the company
 Should have the skills of project
negotiation
 Should have good communication skills
5. Finance manager  Should be able to manage the capital and
resources
 Should be able to make proper project-
related decisions and ensures quality
 Should be able to manage the flow of
capital during project development
6. Documentation in charge  Have the ability to manage the documents
throughout the project development
 Should be able to frame all the project
related terms and conditions properly
 Should know how to manage the
document flow

7. Testing head  Should have the knowledge of HTML, CSS,
Android, IOS, and other languages that are
used during the project development
 Should know how to remove and handle
the bugs and problems of the project
 Should know how to troubleshoot the
problem
8. Maintenance head  Should have the skills of handling the
problems in worst conditions
 Should know when and how to manage
the maintenance programs
 Should have the basic technical knowledge
of hardware and software
9. Web designer  Should have the knowledge of CSS, PHP,
HTML, Javascript, ASP, Perl, Java, Python
and C++.
 Should know how to work with web
servers and SEO
 Must know the designing strategies in
details and should know the user
requirement and work accordingly
(Carson, Tesluk, & Marrone, (2007).
Distribution of roles and responsibilities:
S.No. Roles and responsibility Team member
1. Project director Member 1
2. Web developer Member 1 and 2
3. Application developer Member 2
4. Business analysis in charge Member 3
5. Finance manager Member 4
6. Documentation in charge Member 3 and 4
7. Testing head Member 2
8. Maintenance head Member 1

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

9. Web designer Member 1 and 2
Team communication:
Meetings schedules and details:
First Team Meeting
Topic of discussion Timing of meeting Actions after meeting Team members
opinion
(agree/disagree)
Discussion of the
project plan,
scheduling, and
solutions to project
scenario
09:00 AM to 12:30 PM  Solution
implementation
 Designing of web
and application
 Approval from the
user side
 Documentation
initiation
Member 1- Agree
Member 2- Agree
Member 3- Agree
Member 4- Agree
Second Meeting Schedule
Topic of discussion Timing of meeting Actions after meeting Team members opinion
(agree/disagree)
Explanation of web and
application design and
overview of scheduling
strategy
03:00 PM to 06:30 PM  Approval of client
 Crosschecking of
client
requirements
 Design overview
 Approval to
scheduling
 Distribution of
capital and
resources
Member 1- Agree
Member 2- Agree
Member 3- Agree
Member 4- Not Agree
Third meeting schedule
Topic of discussion Timing of meeting Actions after meeting Team members

opinion
(agree/disagree)
Coding and
implementation of
web design and
application design
10:00 AM to 01:30
PM
 Design and code
implementation
 Modules
integration
 Final testing
 Troubleshooting
techniques
Member 1- Agree
Member 2- Agree
Member 3- Agree
Member 4- Agree
Different ways of team communication and information sharing:
1. Regular meetings of the team members.
2. Regular update of project details.
3. Regular sessions of discussion relate to project and work.
4. Fun day of work where employees can choose the theme and wear in according to the theme.
This will improve the environment and release the stress among employees.
5. Drafting all the conclusions and discussions made in every meeting and session and forwarding it
to the whole team.
6. Regular consultation with the team about the project problems and progress.
7. Freedom of expressing the idea of a solution (De Vries, Van den Hooff, & de Ridder, (2006).
Details of meetings:
Title Meeting details
First Meeting Second Meeting Third Meeting
Topic of
discussion
Discussion of the project
plan, scheduling, and
solutions to project
scenario
Explanation of web and
application design and
overview of scheduling
strategy
Coding and
implementation of web
design and application
design
Start timing of
meeting
09:00 AM 03:00 PM 10:00 AM
All-present/
absent
Present Present Present
Discussion
points
 Project problem
 Project problem
analysis
 Solution to
 Web design
 Application
design
 User needs
 Web coding
 Application
building
 Problems with the

problem
 Schedule of
project
 Interface priority code
 Updates and
maintenance
strategy
Questions
raised
 What is the
problem?
 What is new that
can be provided?
 What is the
strategy of
solution
implementation?
 What design
strategy can be
used?
 What will be the
problems during
designing?
 Points of focus in
designing?
 What kind of policy
in coding should be
used?
 What is the
strategy of
integration of
application and
web data?
 Security issues?
Resources
required
 Writing pads and
pens for notes
 Projection screen
for presentation
 Detail data from
the targeted
audience
 Designing a
platform
 Projection screen
for presentation
related to design
 Project design
displaying charts
and sheets
 Computers with
developing
environment
enabled the
platform
 Antivirus software
 Testing tools
End time of
meeting
12:30 PM 06:30 PM 01:30 PM
Actions after
meeting
 Solution
implementation
 Designing of web
and application
 Approval from the
user side
 Documentation
initiation
 Approval of
client
 Crosschecking of
client
requirements
 Design overview
 Approval to
scheduling
 Distribution of
capital and
resources
 Design and code
implementation
 Modules
integration
 Final testing
 Troubleshooting
techniques
Rules of the project team and expectations:
Following rules will be followed in the project team for the successful implementation of project plan:
1. Dress code should be followed- proper formal wears
2. Daily reports should be sent to the reporting authority.
3. Always be on time.
4. Keep the project details to the project team only. No one shall share the documents with
anyone outside the team.

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

5. Always inform the team head before any changes in the project and before the start of new
modules.
6. Project modules should be developed individually.
7. Everyone should follow their given duties and respect the same of others.
8. No communication with the client should be made without informing the team head in prior.
9. Development timeline and the budget should be followed in every part of the development.
10. Timelines of development of different modules should be followed strictly (Pinto, & Slevin,
(1988).
Expectations from the project team:
1. The team should always be on time.
2. User requirements should be considered above anything.
3. Active participation in all project meetings.
4. Presence of all members in all team meetings.
5. Regular update of work related to project.
6. Working in the boundary of professional and moral ethics.
7. No sharing of data with anyone other than the project team.
8. Meeting all the user requirements.
9. Working in the scopes of the financial limits and time limits.
10. Delivery of product on time (Thamhain, (2004).
Signature of team members:
S.No. Member name Signature
1. Member 1
2. Member 2
3. Member 3
4. Member 4
Part two: Learning Cycles
Meeting structure and outcomes
Meeting one

Meeting second:
Meeting third:
First Meeting
Solution
implementation
Designing of
web and
application
Approval from
user side
Documentation
initiation
Second
Meeting
Approval of
client
Crosschecking
of client
requirements
Design
overview
Approval to
scheduling
Distribution
of capital and
resources