Project Management Report: I-Crop Case Scenario for Online Platform

This project management report analyzes the I-Crop case scenario, focusing on the development of an online platform for buying and selling crops. The report details the measurable organizational value, desired areas of impact, and involved stakeholders. It includes a comprehensive project schedule with a work breakdown structure (WBS), project milestones, and resource allocation. The report also covers scope management, risk assessment, and quality management plans, including team philosophy, verification, and validation activities. Additionally, it provides a project evaluation and closure checklist, along with an annotated bibliography of relevant research articles. The project aims to create an efficient and user-friendly online platform for Globex Corporation's I-Crop project.

Running head: PROJECT MANAGEMENT
Project Management: I-Crop case scenario
Nam of the student:
Name of the university:

1PROJECT MANAGEMENT
1. Measurable Organizational value
This report depicts the role of implementation of a successful website platform or the
online crop buyers and sellers. It is expected that this platform designed for I-Crop will allow
the clients to buy crop through online channel. The area of impact of ranking and the involved
stakeholders are also illustrated in this report.
1.1 Desired areas of impact
Area of Impact Rank (1 from 5)
Consumers: I-Crop consumers are the most
important individual assets who buy products
directly from the providers and avail services
also. It will successfully influence the
advertisement and marketing team members.
1
Operation: In order to successfully run the
applications the operations are to be
incorporated considering the basic needs of the
project.
2
Social: While operating the website proper
social support is mandatory for the success of
the project to significantly resolve the
administrative errors.
4
Strategy: Professional business strategies will
help the owners to gain high competitive
3

2PROJECT MANAGEMENT
advantages and commercial revenues as well.
Financial: The more technical advancement is
possible as much capital will be invested for
the project. It is defined that, the system will
successfully implemented if proper financial
support is incorporated to it.
5
1.2 Value of the project plan
1.3 Involved stakeholders to the project
Stakeholder Expectation
Project manager To complete the project within budget and
time
Finance manager Positive feasibility study
System developer Develop a secured and user friendly system
for the users
Tester Test the website for I-Crop before launching
1.4 Accurate project timeframe and metrics
The project should have to be completed within 8 months.
2. Scope management plan
2.1 Project scope
 Project objectives and goals understanding

3PROJECT MANAGEMENT
 The platform should have a feedback option for change management
 Affordable service should be avail by the project owners
 Online payment option should be possessed by the website platform.
2.2 Resource list
3. Project schedule and WBS
3.1 Project schedule
WBS Task Name Duration Start Finish Predecessors Resource
Names Cost
0 Project schedule
for I -Crop 163 days Fri
2/2/18
Tue
9/18/18 $79,128.00
1 Project
initiation phase 37 days Fri
2/2/18
Mon
3/26/18 $18,864.00
1.1 Requirements
gathering 5 days Fri
2/2/18
Thu
2/8/18
Resource
manager ,Projec
t
manager ,Mark
eting manager
$4,080.00
1.2 requirements
analysis 6 days Fri
2/9/18
Fri
2/16/18 2
Technical
trainers ,project
sponsors
$3,360.00

4PROJECT MANAGEMENT
1.3
Analyzing
current issues of
Virtucon
6 days Mon
2/19/18
Mon
2/26/18 3
Resource
manager ,applic
ation
programmer
$2,016.00
1.4 Setting project
goals 5 days Mon
2/19/18
Fri
2/23/18 3 Resource
manager $880.00
1.5
collecting
functional
requirements
9 days Tue
2/27/18
Fri
3/9/18 4 R &D team $2,448.00
1.6
Collecting non
functional
requirements
5 days Mon
3/12/18
Fri
3/16/18 5,6 Project
manager $2,000.00
1.7 Project
feasibility study 6 days Mon
3/19/18
Mon
3/26/18 7
Project
manager ,
Website
developer
$4,080.00
1.8
Milestone 1:
Completion of
project initial
documentation
0 days Mon
3/26/18
Mon
3/26/18 8
application
programmer ,
Operation
manager ,Proj
ect manager
$0.00
2 Project
planning phase 44 days Tue
3/27/18
Fri
5/25/18 $13,536.00
2.1 Web front end
design 3 days Tue
3/27/18
Thu
3/29/18 9
application
programmer ,Te
chnical
trainers ,Websit
e developer
$2,136.00
2.2
Website
specification
analysis
6 days Fri
3/30/18
Fri
4/6/18 11
Website
developer ,syste
m designer
$2,736.00
2.3
Developing
communication
planning
9 days Mon
4/9/18
Thu
4/19/18 12 HR manager $1,656.00
2.4 stakeholder
management plan 8 days Fri
4/20/18
Tue
5/1/18 13 Operation
manager $1,600.00
2.5 Procurement
planning 10 days Wed
5/2/18
Tue
5/15/18 14 Marketing
manager $2,400.00
2.6
Risk
management
program
8 days Wed
5/16/18
Fri
5/25/18 15
Operation
manager ,Resou
rce manager
$3,008.00
2.7 Milestone 2:
Completion of
project planning
0 days Fri
5/25/18
Fri
5/25/18
16 Operation
manager ,Mark
eting manager
$0.00

5PROJECT MANAGEMENT
phase
3
Project
development
phase
49 days Mon
5/28/18
Thu
8/2/18 $24,144.00
3.1 Prototype
outline design 10 days Mon
5/28/18
Fri
6/8/18 17
system designer
,application
programmer ,W
ebsite
developer
$6,160.00
3.2 Prototype
specification 12 days Mon
6/11/18
Tue
6/26/18 19
Website
developer ,syste
m designer
$5,472.00
3.3 Determining
other project ideas 12 days Mon
6/11/18
Tue
6/26/18 19 Project
manager $4,800.00
3.4 Web design
ideation 8 days Wed
6/27/18
Fri
7/6/18 20 application
programmer $1,280.00
3.5 Connectivity
with database 9 days Mon
7/9/18
Thu
7/19/18 22,21
Resource
manager ,Techn
ical trainers
$4,032.00
3.6
Details
function
verification
10 days Fri
7/20/18
Thu
8/2/18 23 Marketing
manager $2,400.00
3.7
Milestone 3:
Successful design
plan coding
0 days Thu
8/2/18
Thu
8/2/18 24
system
tester ,applicati
on
programmer ,Pr
oject manager
$0.00
4 Project testing
phase 21 days Fri
8/3/18
Fri
8/31/18 $10,296.00
4.1 Project unit
testing 6 days Fri
8/3/18
Fri
8/10/18 25 system designer
,system tester $3,456.00
4.2 Integrated
testing 6 days Mon
8/13/18
Mon
8/20/18 27 system
tester ,coder $3,600.00
4.3 Acceptance
testing 9 days Tue
8/21/18
Fri
8/31/18 27,28
application
programmer ,O
peration
manager
$3,240.00
4.4
Milestone 4:
Approval of the
prototype
0 days Fri
8/31/18
Fri
8/31/18 29
system
tester ,system
designer
$0.00
5 Closure phase 12 days Mon
9/3/18
Tue
9/18/18 $12,288.00
5.1 stakeholders
signoff
6 days Mon
9/3/18
Mon
9/10/18
30 HR manager,
Operation
$4,704.00

6PROJECT MANAGEMENT
manager ,Projec
t manager
5.2 Submitting
final report 6 days Tue
9/11/18
Tue
9/18/18 32
Technical
trainers ,R &D
team ,Marketin
g
manager ,Opera
tion
manager ,Websi
te developer
$7,584.00
5.3
Milestone 5:
Post maintenance
program
development
0 days Tue
9/18/18
Tue
9/18/18 33 Project
manager $0.00
3.2 Work Breakdown Structure (WBS)
Project schedule for
Icrop
Project initiation phase
Requirements
gathering
requirements
analysis
Analyzing current
issues of Virtucon
Setting project goals
collecting fucntional
requirements
Collecting nin
fucntional
requirements
Project feasibility
study
Milestone 1:
Completion of
project initial
documentation
Project planning phase
Web front end
design
Website
specification
analysis
Developing
communication
planning
stakeholder
management plan
Procurement
planning
Risk management
program
Milestone 2:
Completion of
project planning
phase
Project development
phase
Prototype outline
design
Prototype
specification
Determing other
project ideas
Web design ideation
Connectivity with
database
Details fucntion
verification
Milestone 3:
Successful design
plan coding
Project testing phase
Project unit testing
Integrated testing
Acceptance testing
Milestone 4:
Approval of the
prototype
Closure phase
stakeholders signoff
Submiting final
report
Milestone 5: Post
maintenance
program
development
Milestone 1:
Submission of initial
document
Milestone 2:
Submission of
planning details
Milestone 3:
submission of
prototype or testing
Milestone 4:
Approval of the
prototype
Milestone 5: post
maintenance program
submission
Figure 1: Work Breakdown Structure of I-Crop project

7PROJECT MANAGEMENT
(Source: Created by author)
3.3Milestones of the project
WBS Task Name Duration Start Finish Predecessors Resource Names
6
Milestone 1:
Submission of initial
document
0 days Mon
3/26/18
Mon
3/26/18 8 Operation
manager
7
Milestone 2:
Submission of
planning details
0 days Fri 5/25/18 Fri 5/25/18 16 Resource
manager
8
Milestone 3:
submission of
prototype or testing
0 days Thu 8/2/18 Thu 8/2/18 24 R &D team
9
Milestone 4:
Approval of the
prototype
0 days Fri 8/31/18 Fri 8/31/18 29 Marketing
manager
10
Milestone 5: post
maintenance
program submission
0 days Tue
9/18/18 Tue 9/18/18 33 Operation
manager
4. Project risk management plan
4.1 Assumptions
 To complete the project in 8 months
 To complete the project within the estimated budget of $80,000
4.2 Risk assessment
Risks Strategies
Resource over allocation I-Crop should focus on developing online crop
buying selling platform to the consumers.
Based on the project specifications the project
manager should assign the project resources at

8PROJECT MANAGEMENT
the project initiation phase.
Distributed project team Due to the distributed project team internal
conflict may occur and that can be resolved is
the project team members follow open
communication approach.
Lack of technical experienced members Proper technical and development program
5. Quality management plan
5.1 Team philosophy
The aim of Globex is to deliver an affordable, user friendly as well as business effective
crop selling buying online platform to the consumers of I-Crop.
5.2 Set of verification activity
Verification Activity When?
Software and hardware
verification
Initiation
Feasibility study Initiation
Project management practice
adoption
Planning
5.3 Set of validation activity
Validation Activity When?

9PROJECT MANAGEMENT
Prototype testing Testing
Experimental trial Execution
Review documents Monitoring phase
Considering proper project
practices
Initiation phase
6. Project evaluation and closure checklist
6.1 Annotated bibliography
Heravi, A., Coffey, V., & Trigunarsyah, B. (2015). Evaluating the level of
stakeholder involvement during the project planning processes of building
projects. International Journal of Project Management, 33(5), 985-997.
This article portrays the importance of stakeholder’s involvement to a project for its
successful implementation. Tough, for this project the specifications are nominated for building
projects. It is determined that, with different groups of project phases different stakeholders are
associated (Heravi, Coffey & Trigunarsyah, 2015). This successful incorporation can be add on
to the services based on the complexity of the activities and the skills and knowledge of the
project stakeholders. It s examined that the level of involvement for this project is possibly
mentioned for four group of stakeholders. In each of the phase their involvement plays key role.
The article also reviewed that highest involvement with the project is served by the project
manager whereas contractors have a lowest rate of engagement to the panning process of the
projects. It also defines that the involvement of the stakeholders can improve the business

10PROJECT MANAGEMENT
effectiveness during the project initiation up to the project planning phase. How by controlling
the interaction a project can be completed with the support of the stakeholders is also elaborated
in this article.
Batselier, J., & Vanhoucke, M. (2016). Practical application and empirical
evaluation of reference class forecasting for project management. Project Management
Journal, 47(5), 36-51.
This journal reflects the details of practical application as well as empirical evaluation of
the reference for project management forecasting. It is defined that with the successful
implementation of practical implementation the ideas of project manager will grow at a higher
rate. The difference between the traditional project managers and the current project managers
are also illustrated here considering the identification of the reference classes, probability
distribution and class distribution (Batselier & Vanhoucke, 2016). How an empirical database
management system can restrict the data flow control in a project is also illustrated in this
journal. In addition to this, for selecting the reference class how the probability distribution
approach is beneficial are ate illustrated here. Not only this but also, the details application of
the RFC method and their 3 steps implementation process are also illustrated in this journal.
Even for multiple experimental study also this approach is very much beneficial that is also
elaborated here considering Monte Carlo Simulation approach.
Lappe, M., & Spang, K. (2014). Investments in project management are profitable:
A case study-based analysis of the relationship between the costs and benefits of project
management. International Journal of Project Management, 32(4), 603-612.

11PROJECT MANAGEMENT
According to Lappe and Spang (2014), any company will be able to obtain commercial profit
from the competitive market if it invests lot in project management. Considering the relationship
between the costs and project management profits are all elaborated in this report. How mostly
the business organizations gain commercial profit from their application are also elaborated
considering both the qualitative and quantitative profits. In addition to this, the different
evolutionary stages are also illustrated in this journal. There must be an accurate balance
between the investment and the profit that could have gained from the project management
prcatices are also mentioned here. In order to accomplish any project how the estimated cost can
be structured is calculated considering the Return in Investment (ROI) cost benefit analysis
approach.
6.2 Closure checklist
The testing phase of the online platform development project of ICrop has been
successfully completed
 The challenges are all resolved with the risk mitigation strategies
 Final project report is also being hand over to the sponsors