Detailed ICT Project Management Plan for iCrop Application Project

This document presents a comprehensive ICT project management plan for the development and implementation of an iCrop application. It begins by defining the measurable organizational value (MOV) and ranking the areas of impact, emphasizing operations, strategy, customers, and financial aspects. The project scope focuses on creating a website and i-Crop application in-house, adhering to Globex's requirements. The plan details resource allocation, major milestones, activities/tasks, resource assignments, and time estimates for each activity, visualized through a Gantt chart and work breakdown structure. A project budget is outlined, followed by assumptions and risk analysis, including budget, technical, scheduling, and resource shortage risks. The document concludes with a quality management plan and a project closure checklist, ensuring thorough evaluation and sign-off. Desklib offers this and many other solved assignments for students.

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

1
ICT 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..............................................................................................7
3.4. Estimates for Each Activity......................................................................................8
3.5. Project Budget........................................................................................................11
4. Part Four........................................................................................................................13
4.1. Assumptions...........................................................................................................13
4.2. Project Risks...........................................................................................................13
4.3. Risk Analysis..........................................................................................................14
5. Part Five: Quality Management Plan.............................................................................15
6. Part Six...........................................................................................................................15
6.1. Closure Checklist....................................................................................................15
6.2. Project Evaluation...................................................................................................16
References..........................................................................................................................17

2
ICT PROJECT MANAGEMENT
Appendix............................................................................................................................19
Annotated Bibliography.................................................................................................19

3
ICT PROJECT MANAGEMENT
1. Part One
Measurable organizational value in important for defining the goals of the project.
According to the measurable organizational value, every project that is undertaken by the
organization should align with the vision mission and the strategy of an organization (Kerzner &
Kerzner, 2017). The project is expected to have an impact on the different areas which includes
Customer, financial, operation and strategy (Marchewka, 2014). The ranking of these area of
impact in the order of their importance are indicated in the following table (Larson, Gray,
Danlin, Honig & Bacarini, 2014)-
Areas of Impact Rank
Operations 1
Strategy 2
Customers 3
Financial 4
The values that the project will bring to the company are as follows (Harrison & Lock,
2017)-
1. Better: The project will ensure increase in the transparency in the transactions
associated with the buying and selling of the crops and therefore it is for betterment of the
company.
2. Faster: The processing of the transaction is faster since the growers are able to directly
communicate with the buyers.

4
ICT PROJECT MANAGEMENT
The metrics that will help in easier measurement of the MOV of the organization related
to the expectations of the stakeholders.
1. The project should be completed as soon as possible.
2. The project should be implemented in an inexpensive manner as possible
2. Part Two
2.1. Scope and Scope management
It is essential to identify the scope of the project for easier formulation of the project plan.
The scope of this project is to implement a website and i-Crop application in house and in as
inexpensive manner as possible. The scope will be managed by following certain steps which are
as follows (Heagney, 2016)-
1. The project will follow the requirements specified by Globex and therefore no new
requirements can be added in the implementation phase.
2. The Resource allocation in the project should be completed in the implementation
stage.
2.2. List of Resources
The resources allocated for the project are as follows-
Resource Name Max. Units Std. Rate Ovt. Rate Cost/Use
Project Manager 100% $80.00/hr $0.00/hr $0.00

5
ICT PROJECT MANAGEMENT
Resource Manager 100% $40.00/hr $0.00/hr $0.00
Project Supervisor 100% $30.00/hr $0.00/hr $0.00
Coding Team 600% $40.00/hr $0.00/hr $0.00
Testing Team 300% $50.00/hr $0.00/hr $0.00
Database Administrator 100% $20.00/hr $0.00/hr $0.00
Software licensing cost $0.00 $75,000.00
Training Team 300% $30.00/hr $0.00/hr $0.00
Archive $0.00 $5,000.00
Documentation $1,000.00 $0.00
3. Part Three
3.1. Milestone
The Major Milestones of the project are as follows-
M1: Project Initiated
M2: Development of Project Plan
M3: Completion of Development of application and website

6
ICT PROJECT MANAGEMENT
M4: Completion of Testing Phase
M5: Completion of project release
M6: Project Closure
3.2. Activities/tasks
The activities the project will be following are represented in the following table-
WBS Task Name Duration
0 iCrop 121 days
1 Project Starts 0 days
2 Project Initiation 18 days
2.1 Requirements Gathering 6 days
2.2 Meeting with Client 7 days
2.3 Documenting the Requirements 3 days
2.4 Documentation 2 days
2.5 M1:Project Initiated 0 days
3 Project Planning 17 days
3.1 Project Scheduling 5 days
3.2 Resource Estimation 3 days
3.3 Budget Identification 5 days
3.4 Resource Allocation 6 days
3.5 Documentation 1 day
3.6 M2: Development of Project Plan 0 days
4 Project Execution 28 days
4.1 Coding 20 days
4.2 Database Coding 15 days
4.3 Linking the i-Crop Application to Database 10 days
4.4 Documenting the activities 3 days
4.5 M3: Completion of Development of
application and website 0 days
5 Testing 35 days
5.1 Unit Testing 15 days
5.2 System testing 7 days
5.3 User acceptance testing 6 days
5.4 Bug Fixing (if any) 7 days
5.5 M4: Completion of Testing Phase 0 days

7
ICT PROJECT MANAGEMENT
6 Launch 12 days
6.1 Website Launch 2 days
6.2 Training 10 days
6.3 M5: Completion of project release 0 days
7 Project Closure 11 days
7.1 Project Evaluation 5 days
7.2 Report Generation 3 days
7.3 Payment Completion 2 days
7.4 Client Sign off 1 day
7.5 M6: Project Closure 0 days
8 Project ends 0 days
3.3. Resource Assignments
The Resource assignment with each task is as follows-
Task Name Duration Resource Names
iCrop 121 days
Project Starts 0 days Project Manager
Project Initiation 18 days
Requirements Gathering 6 days Project Manager, Resource Manager
Meeting with Client 7 days Project Manager
Documenting the
Requirements 3 days Archive[1],Documentation[1]
Documentation 2 days Project Manager
M1:Project Initiated 0 days
Project Planning 17 days
Project Scheduling 5 days Project Manager, Project Supervisor
Resource Estimation 3 days Project Manager, Project Supervisor
Budget Identification 5 days Project Manager, Resource Manager
Resource Allocation 6 days Resource Manager
Documentation 1 day Resource Manager
M2: Development of Project
Plan 0 days
Project Execution 28 days
Coding 20 days Coding Team
Database Coding 15 days Coding Team, Software licensing cost[1]
Linking the i-Crop
Application to Database 10 days Coding Team, Database Administrator

8
ICT PROJECT MANAGEMENT
Documenting the activities 3 days Archive[1],Documentation[1]
M3: Completion of
Development of application and
website
0 days
Testing 35 days
Unit Testing 15 days Testing Team
System testing 7 days Testing Team
User acceptance testing 6 days Testing Team
Bug Fixing (if any) 7 days Testing Team
M4: Completion of Testing
Phase 0 days
Launch 12 days
Website Launch 2 days Training Team
Training 10 days Training Team
M5: Completion of project
release 0 days
Project Closure 11 days
Project Evaluation 5 days Archive[1],Documentation[1]
Report Generation 3 days Archive[1]
Payment Completion 2 days Project Manager
Client Sign off 1 day Project Manager
M6: Project Closure 0 days
Project ends 0 days Project Manager
3.4. Estimates for Each Activity
The time estimates for each activities are as follows-
WBS Task Name Duration Start Finish
0 iCrop 121 days Tue 02-10-18 Tue 19-03-19
1 Project Starts 0 days Tue 02-10-18 Tue 02-10-18
2 Project Initiation 18 days Tue 02-10-18 Thu 25-10-18
2.1 Requirements Gathering 6 days Tue 02-10-18 Tue 09-10-18
2.2 Meeting with Client 7 days Wed 10-10-18 Thu 18-10-18
2.3 Documenting the
Requirements 3 days Fri 19-10-18 Tue 23-10-18
2.4 Documentation 2 days Wed 24-10-18 Thu 25-10-18
2.5 M1:Project Initiated 0 days Thu 25-10-18 Thu 25-10-18
3 Project Planning 17 days Fri 26-10-18 Mon 19-11-18

9
ICT PROJECT MANAGEMENT
3.1 Project Scheduling 5 days Fri 26-10-18 Thu 01-11-18
3.2 Resource Estimation 3 days Fri 02-11-18 Tue 06-11-18
3.3 Budget Identification 5 days Fri 02-11-18 Thu 08-11-18
3.4 Resource Allocation 6 days Fri 09-11-18 Fri 16-11-18
3.5 Documentation 1 day Mon 19-11-18 Mon 19-11-18
3.6 M2: Development of
Project Plan 0 days Mon 19-11-18 Mon 19-11-18
4 Project Execution 28 days Tue 20-11-18 Thu 27-12-18
4.1 Coding 20 days Tue 20-11-18 Mon 17-12-18
4.2 Database Coding 15 days Tue 20-11-18 Mon 10-12-18
4.3 Linking the i-Crop
Application to Database 10 days Tue 11-12-18 Mon 24-12-18
4.4 Documenting the activities 3 days Tue 25-12-18 Thu 27-12-18
4.5
M3: Completion of
Development of application
and website
0 days Thu 27-12-18 Thu 27-12-18
5 Testing 35 days Fri 28-12-18 Thu 14-02-19
5.1 Unit Testing 15 days Fri 28-12-18 Thu 17-01-19
5.2 System testing 7 days Fri 18-01-19 Mon 28-01-19
5.3 User acceptance testing 6 days Tue 29-01-19 Tue 05-02-19
5.4 Bug Fixing (if any) 7 days Wed 06-02-19 Thu 14-02-19
5.5 M4: Completion of Testing
Phase 0 days Thu 14-02-19 Thu 14-02-19
6 Launch 12 days Fri 15-02-19 Mon 04-03-19
6.1 Website Launch 2 days Fri 15-02-19 Mon 18-02-19
6.2 Training 10 days Tue 19-02-19 Mon 04-03-19
6.3 M5: Completion of project
release 0 days Mon 04-03-19 Mon 04-03-19
7 Project Closure 11 days Tue 05-03-19 Tue 19-03-19
7.1 Project Evaluation 5 days Tue 05-03-19 Mon 11-03-19
7.2 Report Generation 3 days Tue 12-03-19 Thu 14-03-19
7.3 Payment Completion 2 days Fri 15-03-19 Mon 18-03-19
7.4 Client Sign off 1 day Tue 19-03-19 Tue 19-03-19
7.5 M6: Project Closure 0 days Tue 19-03-19 Tue 19-03-19
8 Project ends 0 days Tue 19-03-19 Tue 19-03-19
The Gantt chart of the project is represented in the picture below-

10
ICT PROJECT MANAGEMENT

11
ICT 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 break structure of the project is as follows-
iCrop
Project Starts Project Initiation
Requirements Gathering
Meeting with Client
Documenting the
Requirements
Documentation
M1:Project Initiated
Project Planning
Project Scheduling
Resource Estimation
Budget Identification
Resource Allocation
Documention
M2: Development of
Project Plan
Project Execution
Coding
Database Coding
Linking the i-Crop
Application to Database
Documenting the
activitiesM3: Completion of
Development of
application and website
Testing
Unit Testing
System testing
User acceptance testing
Bug Fixing (if
any)M4: Completion of Testing
Phase
Launch
Website Launch
Training
M5: Completion of project
release
Project Closure
Project Evaluation
Report Generation
Payment Completion
Client Sign off
M6: Project Closure
Project ends
Figure 2: Representing the Work breakdown structure of the project
(Source: Generated by author using MS schedule Pro)
3.5. Project Budget
Task Name Duration Resource Names Cost
iCrop 121 days $158,400.00
Project Starts 0 days Project Manager $0.00
Project Initiation 18 days $17,520.00
Requirements
Gathering 6 days Project Manager, Resource Manager $5,760.00
Meeting with Client 7 days Project Manager $4,480.00
Documenting the
Requirements 3 days Archive[1],Documentation[1] $6,000.00
Documentation 2 days Project Manager $1,280.00
M1:Project
Initiated 0 days $0.00