Teamwork and Reflection: A Case Study of the i-Crop Project
VerifiedAdded on 2024/07/01
|18
|3874
|421
AI Summary
This report examines the teamwork and reflection aspects of the i-Crop project, a collaborative effort between Globex Foundation and Virtucon to develop an online cash marketplace platform for grain and seasonal crop sellers and buyers. The report details the project brief, team composition, communication plan, and the author's personal reflections on leadership and project management skills. It highlights the importance of effective communication, collaboration, and leadership in achieving project success.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Teamwork and reflection
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
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.................................................................................................................................................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.
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
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
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
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:
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
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
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
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
(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.
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.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
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
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
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
Assignment of roles before the coming meetings:
S.No. Topic of meeting Points of discussion Duties assigned
1. Explanation of web and
application design and
overview of scheduling
strategy.
Web design
Application design
User needs
Interface priority
Web design- member 1
Application design-
member 2
Needs analysis- member
3
Interface study- member
4
S.No. Topic of meeting Points of discussion Duties assigned
1. Coding and implementation of
web design and application
design.
Web coding
Application building
Problems with the code
Updates and
maintenance strategy
Web coding- member 1
Application building-
member 2
Problem analysis-
member 3
Update strategy- member
4
Third Meeting
Design and code
implementation
Modules
integration Final testing Troubleshooting
techniques
S.No. Topic of meeting Points of discussion Duties assigned
1. Explanation of web and
application design and
overview of scheduling
strategy.
Web design
Application design
User needs
Interface priority
Web design- member 1
Application design-
member 2
Needs analysis- member
3
Interface study- member
4
S.No. Topic of meeting Points of discussion Duties assigned
1. Coding and implementation of
web design and application
design.
Web coding
Application building
Problems with the code
Updates and
maintenance strategy
Web coding- member 1
Application building-
member 2
Problem analysis-
member 3
Update strategy- member
4
Third Meeting
Design and code
implementation
Modules
integration Final testing Troubleshooting
techniques
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Part three: communication plan
Stakeholders
According to the analysis of the current project plan and specifications, the following will be the
stakeholders of the project i-Crop:
S.No
.
Stakeholders list
1. Project director
2. Web developer
3. Application developer
4. Business analysis in charge
5. Finance manager
6. Documentation in charge
7. Testing head
8. Maintenance head
9. Web designer
10. Development experts
11. financer
12. Globex foundation
13. Virtucon
14. Farmers
15. Grain/crop warehouse owners
Communication plan for i-Corp
A communication plan is necessary to increase the communication between the stakeholders. It is
important to have an effective project plan in order to develop a transparent and healthy system of
development and leadership. The proper management is the result of the effective communication
Stakeholders
According to the analysis of the current project plan and specifications, the following will be the
stakeholders of the project i-Crop:
S.No
.
Stakeholders list
1. Project director
2. Web developer
3. Application developer
4. Business analysis in charge
5. Finance manager
6. Documentation in charge
7. Testing head
8. Maintenance head
9. Web designer
10. Development experts
11. financer
12. Globex foundation
13. Virtucon
14. Farmers
15. Grain/crop warehouse owners
Communication plan for i-Corp
A communication plan is necessary to increase the communication between the stakeholders. It is
important to have an effective project plan in order to develop a transparent and healthy system of
development and leadership. The proper management is the result of the effective communication
between the stakeholders. Communication improves the stakeholder involvement and team
involvement in the project development.
Main points of consideration for communication plan:
There is a need to consider the following points for the communication plan:
1. Staff: there should be enough people that can handle the project development.
2. Financial management: the budget allotted for the project development should be enough to
meet all the requirements related to the project.
3. The enterprise is needed to fully support all the executions of the project and the
communication planning.
Major parts of the plan:
1. Goal: to provide a platform that can help the crop growers and buyers to sell and purchase the
crops at the same place.
2. Target audience: people who buy the crops either for their individual, family or the warehouse
use and the farmers who grow grain and other seasonal crops.
3. Stock alert: alert messages are sending to the users about the available prices of the grains and
other crops, offers that are available at the current time, and the bids that are either placed or
accepted by the sellers.
4. Bid alert: if a buyer places any buying bid on any stock of crop, the user will be notified of the
bid acceptance or rejection and the seller will be notified of the bid placed on his stock.
5. The medium of communication: i-Corp can be promoted with the help of the Globex foundation
platform and the Virtucon platform and also by using the digital media resources. Different
sessions of i-Corp can be given to the targeting audience and some offers can be provided to
both seller and buyer for increasing the stakeholder interest.
6. Communication plan implementation: the communication plan can be implemented as follows:
S.No. Medium of communication Duration In charge of plan
1. Communication through Globex and
Virtucon platform
2 days Member 2
2. Flyers and newspapers 1 day Member 1
3. Sessions and presentations 5 days Member 3
4. Through social media 3 days Member 4
7. Plan verification: the plan is proofed before implementation and is changed and updated
according to the requirements (Welch, & Jackson, (2007).
involvement in the project development.
Main points of consideration for communication plan:
There is a need to consider the following points for the communication plan:
1. Staff: there should be enough people that can handle the project development.
2. Financial management: the budget allotted for the project development should be enough to
meet all the requirements related to the project.
3. The enterprise is needed to fully support all the executions of the project and the
communication planning.
Major parts of the plan:
1. Goal: to provide a platform that can help the crop growers and buyers to sell and purchase the
crops at the same place.
2. Target audience: people who buy the crops either for their individual, family or the warehouse
use and the farmers who grow grain and other seasonal crops.
3. Stock alert: alert messages are sending to the users about the available prices of the grains and
other crops, offers that are available at the current time, and the bids that are either placed or
accepted by the sellers.
4. Bid alert: if a buyer places any buying bid on any stock of crop, the user will be notified of the
bid acceptance or rejection and the seller will be notified of the bid placed on his stock.
5. The medium of communication: i-Corp can be promoted with the help of the Globex foundation
platform and the Virtucon platform and also by using the digital media resources. Different
sessions of i-Corp can be given to the targeting audience and some offers can be provided to
both seller and buyer for increasing the stakeholder interest.
6. Communication plan implementation: the communication plan can be implemented as follows:
S.No. Medium of communication Duration In charge of plan
1. Communication through Globex and
Virtucon platform
2 days Member 2
2. Flyers and newspapers 1 day Member 1
3. Sessions and presentations 5 days Member 3
4. Through social media 3 days Member 4
7. Plan verification: the plan is proofed before implementation and is changed and updated
according to the requirements (Welch, & Jackson, (2007).
Part four: Reflection
Experience of teamwork
How did your experience compare to your understanding of the leadership qualities required to
successfully lead a project?
My experience of the leadership quality played a very important role in the successful implementation
of the project requirements. I needed to implement the experiences along with my understandings to
successfully lead the project to the final stage. I understood that in comparison to the understanding
there is a need for more experience and leadership. Only the good leader can lead the project to
successful completion and achieve the project requirements. While working as a team manager I
learned exactly how to manage the project and how to work in schedules timelines in a team of people
with the enormous amount of skills and knowledge. I also learned that every person has a special skill
and there is need for improving that skill with the help of proper motivation and support. I also learned
that I, myself have many flaws which are needed to be worked out in order to gain the perfection sort of
skills. During this development of the i-Crop, the major focus of my concern was to help my team with
all their problems and to be a sort of example in all the qualities. I also focused on the part where I
needed to be strict and where I needed to be lenient with the team. I tried to provide every required
resource for the project and give my team the best of the results.
Based on your experience, what are the necessary techniques, skills, methods, and ICT project
manager requires in the IT profession?
Based on my experience of the ICT project management, any leader will need the following techniques,
skills, and methods to be a good and successful ICT project manager:
1. Good understanding of leadership responsibilities.
2. Ability to work as a team.
3. Understanding management techniques of the project.
4. Ability to handle the stress and workload.
5. Good knowledge of hardware and software and their integration.
6. Ability to understand the problems related to resources and handling techniques.
7. The ability to be a good team member.
8. A team leader should have good knowledge of all the fields in which the people with him are
working on.
9. Team lead should be able to communicate everything transparently within the team.
10. Good communication skills.
11. Financial management knowledge.
12. Risk-taking abilities and management quality (Munns, & Bjeirmi, (1996).
Experience of teamwork
How did your experience compare to your understanding of the leadership qualities required to
successfully lead a project?
My experience of the leadership quality played a very important role in the successful implementation
of the project requirements. I needed to implement the experiences along with my understandings to
successfully lead the project to the final stage. I understood that in comparison to the understanding
there is a need for more experience and leadership. Only the good leader can lead the project to
successful completion and achieve the project requirements. While working as a team manager I
learned exactly how to manage the project and how to work in schedules timelines in a team of people
with the enormous amount of skills and knowledge. I also learned that every person has a special skill
and there is need for improving that skill with the help of proper motivation and support. I also learned
that I, myself have many flaws which are needed to be worked out in order to gain the perfection sort of
skills. During this development of the i-Crop, the major focus of my concern was to help my team with
all their problems and to be a sort of example in all the qualities. I also focused on the part where I
needed to be strict and where I needed to be lenient with the team. I tried to provide every required
resource for the project and give my team the best of the results.
Based on your experience, what are the necessary techniques, skills, methods, and ICT project
manager requires in the IT profession?
Based on my experience of the ICT project management, any leader will need the following techniques,
skills, and methods to be a good and successful ICT project manager:
1. Good understanding of leadership responsibilities.
2. Ability to work as a team.
3. Understanding management techniques of the project.
4. Ability to handle the stress and workload.
5. Good knowledge of hardware and software and their integration.
6. Ability to understand the problems related to resources and handling techniques.
7. The ability to be a good team member.
8. A team leader should have good knowledge of all the fields in which the people with him are
working on.
9. Team lead should be able to communicate everything transparently within the team.
10. Good communication skills.
11. Financial management knowledge.
12. Risk-taking abilities and management quality (Munns, & Bjeirmi, (1996).
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Conclusion:
I have completed all the parts of the section Teamwork and reflection of ITC project management,
during the development of online cash marketplace platform-i-Crop, which is developed in the
partnership of both Globex Foundation and Virtucon. In part one I have explained the project brief and
objective and also the skills and knowledge required of the team members, the distribution of roles and
responsibility and the team meeting plans. In the second part I have explained the learning cycles of the
project where I have elaborated the team meeting structures and conclusions of meetings. Part three is
completely about the communication plan and the stakeholders where I have explained the stakeholder
list and the methods of communication with the stakeholder. And finally in last part of the teamwork
and reflection, I have mentioned my personal experience of the leadership in i-Crop project
development and I have also mentioned the skills and techniques that in my view are necessary for
every team leader.
I have completed all the parts of the section Teamwork and reflection of ITC project management,
during the development of online cash marketplace platform-i-Crop, which is developed in the
partnership of both Globex Foundation and Virtucon. In part one I have explained the project brief and
objective and also the skills and knowledge required of the team members, the distribution of roles and
responsibility and the team meeting plans. In the second part I have explained the learning cycles of the
project where I have elaborated the team meeting structures and conclusions of meetings. Part three is
completely about the communication plan and the stakeholders where I have explained the stakeholder
list and the methods of communication with the stakeholder. And finally in last part of the teamwork
and reflection, I have mentioned my personal experience of the leadership in i-Crop project
development and I have also mentioned the skills and techniques that in my view are necessary for
every team leader.
Reference list:
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Carson, J. B., Tesluk, P. E., & Marrone, J. A. (2007). Shared leadership in teams: An investigation
of antecedent conditions and performance. Academy of Management Journal, 50(5), 1217-1234.
De Vries, R. E., Van den Hooff, B., & de Ridder, J. A. (2006). Explaining knowledge sharing: The
role of team communication styles, job satisfaction, and performance beliefs. Communication
Research, 33(2), 115-135.
Pinto, J. K., & Slevin, D. P. (1988). Project success. Project management journal, 4, 67-72.
Munns, A. K., & Bjeirmi, B. F. (1996). The role of project management in achieving project
success. International journal of project management, 14(2), 81-87.
Welch, M., & Jackson, P. R. (2007). Rethinking internal communication: a stakeholder
approach. Corporate Communications: An International Journal, 12(2), 177-198.
Thamhain, H. J. (2004). Linkages of the project environment to performance: lessons for team
leadership. International Journal of Project Management, 22(7), 533-544.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Carson, J. B., Tesluk, P. E., & Marrone, J. A. (2007). Shared leadership in teams: An investigation
of antecedent conditions and performance. Academy of Management Journal, 50(5), 1217-1234.
De Vries, R. E., Van den Hooff, B., & de Ridder, J. A. (2006). Explaining knowledge sharing: The
role of team communication styles, job satisfaction, and performance beliefs. Communication
Research, 33(2), 115-135.
Pinto, J. K., & Slevin, D. P. (1988). Project success. Project management journal, 4, 67-72.
Munns, A. K., & Bjeirmi, B. F. (1996). The role of project management in achieving project
success. International journal of project management, 14(2), 81-87.
Welch, M., & Jackson, P. R. (2007). Rethinking internal communication: a stakeholder
approach. Corporate Communications: An International Journal, 12(2), 177-198.
Thamhain, H. J. (2004). Linkages of the project environment to performance: lessons for team
leadership. International Journal of Project Management, 22(7), 533-544.
1 out of 18
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.