Comprehensive Project Plan: Globex i-Crop Website and Application

This document presents a comprehensive project plan for the development of the i-Crop website and application for Globex. It begins by defining the Measurable Organizational Value (MOV), ranking the areas of impact (operational, strategy, financial, customer, and social), and identifying key organizational values like improved user experience and expanded reach. The plan outlines the project's scope, resource allocation, milestones, activities, and tasks, providing a detailed Work Breakdown Structure (WBS) and Gantt chart. It includes resource assignments for each activity, time estimates, and a project budget. Furthermore, the plan addresses potential assumptions, project risks, and a risk analysis, along with a quality management plan and project closure checklist. The document concludes with a project evaluation section and an annotated bibliography, offering a thorough overview of the project's execution and management.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student
Name of the University
Author Note

1
PROJECT MANAGEMENT
Table of Contents
1. Part One...........................................................................................................................3
2. Part Two...........................................................................................................................4
2.1. Scope and Scope management..................................................................................4
2.2. List of Resources......................................................................................................4
3. Part Three.........................................................................................................................5
3.1. Milestone..................................................................................................................5
3.2. Activities/tasks..........................................................................................................6
3.3. Resource Assignments..............................................................................................9
3.4. Estimates for Each Activity....................................................................................11
3.5. Project Budget........................................................................................................12
4. Part Four........................................................................................................................14
4.1. Assumptions...........................................................................................................14
4.2. Project Risks...........................................................................................................14
4.3. Risk Analysis..........................................................................................................15
5. Part Five: Quality Management Plan.............................................................................16
6. Part Six...........................................................................................................................16
6.2. Closure Checklist....................................................................................................16
6.3. Project Evaluation...................................................................................................17
References..........................................................................................................................18

2
PROJECT MANAGEMENT
Appendix............................................................................................................................20
Annotated Bibliography.................................................................................................20

3
PROJECT MANAGEMENT
1. Part One
The measurable organizational value helps in defining and measuring the objectives and
the goals of a project (Binder, 2016). It helps in defining the value the organization will bring to
the clients (Kerzner, 2018). Analysing the measurable organizational value of the project that
Virtucon will be delivering to the Globex is essential for project evaluation and to measure the
extension to which Virtucon is able to deliver the requirements as specified by Globex.
The desired area of impact of the project includes the financial, operations, strategy,
social and customer (Beringer, Jonas & Kock, 2013). The field of impact are ranked in order one
to five where one is the highest rank and five is the lowest, to understand the field in on which
this project will have a highest impact.
Rank 1 Operational
Rank 2 Strategy
Rank 3 Financial
Rank 4 Customer
Rank 5 Social
Apart from identifying the area of impact, it is essential to identify the values that the project will
bring on to Globex and Virtucon.
Better- The project aims in providing a better experience of dealing with the warehoused grains
in perspective of both the buyers and the sellers.
Do More- Globex wants to reach out to more buyers with the implementation of this smart phone
application.

4
PROJECT MANAGEMENT
After identification of the area of impact and the organizational values that this project is
going to provide, it is essential to identify appropriate metrics to measure the success of the
project. The metrics are as follows (Burke, 2013)-
1. The target of the project is to develop both the application and the website in an
inexpensive manner
2. The project is to be completed within a selected time frame
The time frame for achieving this should be no more than six months and work of the
project can only start after the approval of the project plan.
2. Part Two
2.1. Scope and Scope management
Prior to the project implementation, it is essential to identify the scope of the project, as it
gives an idea about what to expect from the project (Hwang & Ng, 2013). The project scope will
be managed by ensuring and enforcing appropriate project monitoring and control in the project
implementation phase (Kerzner & Kerzner, 2017). Furthermore, it is the responsibility of the
project manager to ensure that no scope creep occurs in the project (Turk, France & Rumpe,
2014). This can be achieved by allocating accurate resources to each of the project activities. The
resources associated with the project are discussed in the following section.
2.2. List of Resources
The List of resources associated with this project are as follows-
Resource Name Type Max. Units Std. Rate Cost/Use

5
PROJECT MANAGEMENT
Project Manager Work 100% $80.00/hr $0.00
Resource Manager Work 200% $40.00/hr $0.00
Functional Manager Work 200% $55.00/hr $0.00
Project Supervisor Work 100% $35.00/hr $0.00
Coders Work 600% $40.00/hr $0.00
Testers Work 400% $35.00/hr $0.00
Database Administrator Work 100% $25.00/hr $0.00
Software licensing Material $0.00 $75,000.00
Website Go Live Material $0.00 $50,000.00
Trainers Work 300% $25.00/hr $0.00
Archive Material $0.00 $5,000.00
Content writer Work 100% $20.00/hr $0.00
3. Part Three
3.1. Milestone
The deliverables and the milestone of the project are as follows-

6
PROJECT MANAGEMENT
M1:Successful Completion of Requirements Gathering
M2: sharing and Approval of Project Plan
M3: Completion of successful Coding
M4: Completion of Testing and Bug Fixing
M5: Successful Project Release
M6: Successful Project Closure
3.2. Activities/tasks
The Activities and the tasks that the project will deliver are as follows-
WBS Task Name
0 i-Crop Website and Application Development
1 Start of the Project
2 Initiation Phase
2.1 Requirements Identification and Gathering
2.2 Meeting with Globex to Understand the Requirements
2.3 Specification documentation
2.4 Sharing the documents with the Clients
2.5 M1:Successful Completion of Requirements Gathering
3 Planning Phase
3.1 Initiation of Project Plan development
3.2 Scheduling the Project
3.3 Estimating the cost and the Budget of Project
3.4 Resource Allocation
3.5 Documenting the Project Plan
3.6 M2: sharing and Approval of Project Plan
4 Execution Phase
4.1 Coding the application and the Website
4.2 Database Development
4.3 Linking the i-Crop Application to Database
4.4 Documentation
4.5 M3: Completion of successful Coding
5 Testing
5.1 Unit Testing

7
PROJECT MANAGEMENT
5.2 System testing
5.3 User acceptance testing
5.4 Bug Fixing (if any)
5.5 M4: Completion of Testing and Bug Fixing
6 Go Live and Training
6.1 Website and Application Demonstration
6.2 Training and Maintaianance
6.3 M5: Successful Project Release
7 Project Closure
7.1 Documentation
7.2 Record Archival
7.3 Resource Release
7.4 Payment Completion
7.5 Client Sign off
7.6 M6: Successful Project Closure
8 Project ends
The Gantt chart of the project is represented in the following-

8
PROJECT MANAGEMENT

9
PROJECT MANAGEMENT
Figure 1: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)
The work activities marked in red in the Gantt chart above depict the critical path of the project
The work breakdown structure of the project is as follows-
I-Crop Website and
Application
Development
Start of the Project Initiation Phase
Requirements
Identification and
Gathering
Meeting with Globex to
Understand the
Requirements
Specification
documentation
Sharing the documents
with the Clients
M1:Successful
Completion of
Requirements Gathering
Planning Phase
Initiation of Project Plan
development
Scheduling the Project
Estimating the cost and
the Budget of Project
Resource Allocation
Documenting the Project
Plan
M2: sharing and Approval
of Project Plan
Execution Phase
Coding the application
and the Website
Database Development
Linking the i-Crop
Application to Database
Documentation
M3: Completion of
successful Coding
Testing
Unit Testing
System testing
User acceptance testing
Bug Fixing (if
any)M4: Completion of Testing
and Bug Fixing
Go Live and
Training
Website and Application
Demonstration
Training and
Maintaianance
M5: Successful Project
Release
Project Closure
Documentation
Record Archival
Resource Release
Payment Completion
Client Sign off
M6: Successful Project
Closure
Project ends
Figure 2: Representing the Work Breakdown Structure of the Project
(Source: created by Author using MS schedule Pro)
3.3. Resource Assignments
The resources that has been allocated for each of the activities is represented in the table
below-
WBS Task Name Resource Names
0 i-Crop Website and Application
Development
1 Start of the Project Project Manager
2 Initiation Phase
2.1 Requirements Identification and
Gathering Project Manager, Functional Manager

10
PROJECT MANAGEMENT
2.2 Meeting with Globex to Understand
the Requirements Project Manager, Functional Manager
2.3 Specification documentation Archive[1],Content writer
2.4 Sharing the documents with the
Clients Project Manager
2.5 M1:Successful Completion of
Requirements Gathering
3 Planning Phase
3.1 Initiation of Project Plan
development Project Manager, Project Supervisor
3.2 Scheduling the Project Project Manager, Project Supervisor
3.3 Estimating the cost and the Budget of
Project Project Manager, Resource Manager
3.4 Resource Allocation Resource Manager
3.5 Documenting the Project Plan Resource Manager
3.6 M2: sharing and Approval of
Project Plan
4 Execution Phase
4.1 Coding the application and the
Website Coders, Website Go Live[1]
4.2 Database Development Coders, Software licensing[1],Database
Administrator
4.3 Linking the i-Crop Application to
Database Coders, Database Administrator
4.4 Documentation Archive[1],Content writer
4.5 M3: Completion of successful
Coding
5 Testing
5.1 Unit Testing Testers
5.2 System testing Testers
5.3 User acceptance testing Testers
5.4 Bug Fixing (if any) Testers
5.5 M4: Completion of Testing and
Bug Fixing
6 Go Live and Training
6.1 Website and Application
Demonstration Trainers, Functional Manager
6.2 Training and Maintenance Trainers, Functional Manager
6.3 M5: Successful Project Release
7 Project Closure
7.1 Documentation Archive[1],Content writer
7.2 Record Archival Archive[1]

11
PROJECT MANAGEMENT
7.3 Resource Release Project Manager
7.4 Payment Completion Functional Manager, Project Manager
7.5 Client Sign off Project Manager
7.6 M6: Successful Project Closure
8 Project ends Project Manager
3.4. Estimates for Each Activity
The time estimate for each of the activities of the project is represented in the following
table-
Task Name Duration Start Finish
i-Crop Website and Application
Development 137 days Wed 03-10-18 Thu 11-04-19
Start of the Project 0 days Wed 03-10-18 Wed 03-10-18
Initiation Phase 18 days Wed 03-10-18 Fri 26-10-18
Requirements Identification and
Gathering 5 days Wed 03-10-18 Tue 09-10-18
Meeting with Globex to
Understand the Requirements 10 days Wed 10-10-18 Tue 23-10-18
Specification documentation 2 days Wed 24-10-18 Thu 25-10-18
Sharing the documents with the
Clients 1 day Fri 26-10-18 Fri 26-10-18
M1:Successful Completion of
Requirements Gathering 0 days Fri 26-10-18 Fri 26-10-18
Planning Phase 14 days Mon 29-10-18 Thu 15-11-18
Initiation of Project Plan
development 7 days Mon 29-10-18 Tue 06-11-18
Scheduling the Project 2 days Wed 07-11-18 Thu 08-11-18
Estimating the cost and the Budget
of Project 7 days Wed 07-11-18 Thu 15-11-18
Resource Allocation 5 days Wed 07-11-18 Tue 13-11-18
Documenting the Project Plan 2 days Wed 14-11-18 Thu 15-11-18
M2: sharing and Approval of
Project Plan 0 days Thu 15-11-18 Thu 15-11-18
Execution Phase 47 days Fri 16-11-18 Mon 21-01-19
Coding the application and the
Website 15 days Fri 16-11-18 Thu 06-12-18
Database Development 30 days Fri 16-11-18 Thu 27-12-18