ICT Project Management

This article discusses the project management plan for iCrop, an online platform for crop growers and buyers. It covers the scope, resources, milestones, activities, estimates, and metrics for the project. The article also highlights the impact of the project on financial, customer, strategy, operational, and social groups.

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..............................................................................................9
3.4. Estimates for Each Activity....................................................................................10
3.5. Project Budget........................................................................................................12
4. Part Four........................................................................................................................13
4.1. Assumptions...........................................................................................................13
4.2. Risks.......................................................................................................................13
4.3. Risk Analysis..........................................................................................................14
5. Part Five: Quality Management Plan.............................................................................15
6. Part Six...........................................................................................................................16
6.1. Annotated Bibliography..........................................................................................16
6.2. Closure Checklist....................................................................................................18
6.3. Project Evaluation...................................................................................................18

2
ICT PROJECT MANAGEMENT
Bibliography......................................................................................................................20

3
ICT PROJECT MANAGEMENT
1. Part One
The aim of the project is to develop and online website and an application called iCrop
that will help the crop growers and buyers to directly communicate with each other regarding
business. The desired area of impact for the project is to bring in transparency in the process of
managing and selling of the warehouse grains. The project is expected to have a large impact on
strategy, financial, operational and social groups. The ranking of these areas in terms of
importance is represented in the following table-
Rank 1 is of highest importance while rank 5 is the smallest
Area of Impact Rank
Financial 1- Since it will improve the financial condition of
the crop growers
Customer 2- It will increase the transparency in the process of
dealing with the warehoused grains
Strategy 3- This strategy will help in business improvements
Operational 4- It aims in eliminating the operational issues
Social 5- No such impact in social sector.
The values the project will enforce are as follows-
Faster Dealing with the crops will be faster mainly
because the bidding will be done in an online
platform
Better The process of dealing with the warehoused grains
will be better by this project as it will increase the

4
ICT PROJECT MANAGEMENT
transparency.
The metric developed for this project associated with the expectations of the stakeholders are-
1. Completion of project within the schedule time
2. Completion of the project in as much less cost as possible
3. Increase in the business value
The target metrics are needed to be achieved by the end of project closure phase.
2. Part Two
2.1. Scope and Scope management
The project scope incorporates implementation of i-Crop Website and application by
Virtucon in as much less cost as possible. A scope management plan is generally developed in
order to define and manage the processes of the project. As a part of the scope management plan,
the resources and the activities of the project, is identified. The scope of the project will be
managed by developing a scope management plan and by ensuring that the resources of the
project are properly allocation. The following section gives an idea of the major resources
associated with this project.
2.2. List of Resources
The list of resources associated with this project and their standard rates is represented in
the following table-

5
ICT PROJECT MANAGEMENT
Resource Name Type Max. Units Std. Rate Cost/Use
Project Manager Work 100% $70.00/hr $0.00
Resource Manager Work 200% $50.00/hr $0.00
Project Supervisor Work 100% $40.00/hr $0.00
Coders Work 500% $35.00/hr $0.00
Testers Work 500% $38.00/hr $0.00
Database Administrator Work 200% $30.00/hr $0.00
Software licensing cost Material $0.00 $75,000.00
Website Upload Cost Material $0.00 $50,000.00
Trainers Work 200% $25.00/hr $0.00
Archieve Material $0.00 $5,000.00
Content writer Work 200% $20.00/hr $0.00
3. Part Three
3.1. Milestone
The major milestones of the project are as follows-
M1: Completion of Requirements Gathering

6
ICT PROJECT MANAGEMENT
M2: Development and Approval of Project Plan
M3: Completion of Development of application and website
M4: Completion of Testing
M5: Completion of Users' Training
M6: Successful Project Closure
3.2. Activities/tasks
The activities that will be followed while implementation of the i-Crop software and
website is represented in the following table-
WBS Task Name
0 Development of i-Crop Application
1 Project Starts
2 Project Initiation
2.1 Understanding the Requirements of the Project
2.2 Understanding the specifications of the Website and the
Application to be developed
2.3 Documenting the Requirements
2.4 Sharing it with the Clients
2.5 M1: Completion of Requirements Gathering
3 Project Planning
3.1 Planning the Implementation
3.2 Scheduling
3.3 Budget estimation
3.4 Resource Requirement
3.5 Resource Allocation
3.6 M2: Development and Approval of Project Plan
4 Project Execution
4.1 Coding the Website
4.2 Coding the iCrop Application
4.3 Linking the i-Crop Application to Database
4.4 Documenting the activities

7
ICT PROJECT MANAGEMENT
4.5 M3: Completion of Development of application and website
5 Testing
5.1 Unit Testing
5.2 System testing
5.3 User acceptance testing
5.4 Bug Fixing (if any)
5.5 M4: Completion of Testing
6 Training
6.1 Developing training manuals
6.2 Imparting training
6.3 M5: Completion of Users' Training
7 Project Closure
7.1 Completion of documenting
7.2 Record Archival
7.3 Resource Release
7.4 Client Sign off
7.5 M6: Successful Project Closure
8 Project ends
Successful completion of each of these tasks will ensure success of the project. The
projects are needed to be completed within the estimated schedule and budget.
The Gantt chart and the WBS of the project in represented in the following pictures-

8
ICT PROJECT MANAGEMENT

9
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 breakdown structure of the project is represented in the following picture-
Development of i-Crop
Application
Project Starts Project Initiation
Understanding the
Requirements of the
Project
Understanding the
specifications of the
Website and the
Applictaion to be
developed
Documenting the
Requirements
Sharing it with the Clients
M1: Completion of
Requirements Gathering
Project Planning
Planning the
Implementation
Scheduling
Budget estimation
Resource Requirement
Resource Allocation
M2: Development and
Approval of Project Plan
Project Execution
Coding the Website
Coding the iCrop
Application
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
Training
Developing training
manuals
Imparting training
M5: Completion of Users'
Training
Project Closure
Completion of
documenting
Record Archival
Resource Release
Client Sign off
M6: Successful Project
Closure
Project ends
Figure 2: Representing the Work Breakdown Structure of the Project
(Source: Generated by Author using MS Schedule Pro)
3.3. Resource Assignments
The resource estimated and the allocated resources of each of the tasks is represented in
the following table-
Task Name Resource Names
Development of i-Crop Application
Project Starts Project Manager
Project Initiation
Understanding the Requirements of the Project Project Manager, Resource Manager
Understanding the specifications of the Website
and the Application to be developed Project Manager
Documenting the Requirements Archieve [1],Content writer
Sharing it with the Clients Project Manager

10
ICT PROJECT MANAGEMENT
M1: Completion of Requirements Gathering
Project Planning
Planning the Implementation Project Manager, Project Supervisor
Scheduling Project Manager, Project Supervisor
Budget estimation Project Manager, Resource Manager
Resource Requirement Resource Manager
Resource Allocation Resource Manager
M2: Development and Approval of Project Plan
Project Execution
Coding the Website Coders, Website Upload Cost[1]
Coding the iCrop Application Coders, Software licensing cost[1]
Linking the i-Crop Application to Database Coders, Database Administrator
Documenting the activities Archieve [1],Content writer
M3: Completion of Development of application
and website
Testing
Unit Testing Testers
System testing Testers
User acceptance testing Testers
Bug Fixing (if any) Testers
M4: Completion of Testing
Training
Developing training manuals Trainers
Imparting training Trainers
M5: Completion of Users' Training
Project Closure
Completion of documenting Archieve [1],Content writer
Record Archival Archieve [1]
Resource Release Project Manager
Client Sign off Project Manager
M6: Successful Project Closure
Project ends Project Manager
3.4. Estimates for Each Activity
The estimated duration for each of the activities of the project is represented in the
following table-

11
ICT PROJECT MANAGEMENT
Task Name Duration Start Finish

12
ICT PROJECT MANAGEMENT
Development of i-Crop Application 132 days Mon 01-10-18 Tue 02-04-19
Project Starts 0 days Mon 01-10-18 Mon 01-10-18
Project Initiation 18 days Mon 01-10-18 Wed 24-10-18
Understanding the Requirements
of the Project 5 days Mon 01-10-18 Fri 05-10-18
Understanding the specifications
of the Website and the Application to
be developed
10 days Mon 08-10-18 Fri 19-10-18
Documenting the Requirements 2 days Mon 22-10-18 Tue 23-10-18
Sharing it with the Clients 1 day Wed 24-10-18 Wed 24-10-18
M1: Completion of
Requirements Gathering 0 days Wed 24-10-18 Wed 24-10-18
Project Planning 14 days Thu 25-10-18 Tue 13-11-18
Planning the Implementation 7 days Thu 25-10-18 Fri 02-11-18
Scheduling 2 days Mon 05-11-18 Tue 06-11-18
Budget estimation 7 days Mon 05-11-18 Tue 13-11-18
Resource Requirement 5 days Mon 05-11-18 Fri 09-11-18
Resource Allocation 2 days Mon 12-11-18 Tue 13-11-18
M2: Development and Approval
of Project Plan 0 days Tue 13-11-18 Tue 13-11-18
Project Execution 47 days Wed 14-11-18 Thu 17-01-19
Coding the Website 15 days Wed 14-11-18 Tue 04-12-18
Coding the iCrop Application 30 days Wed 14-11-18 Tue 25-12-18
Linking the i-Crop Application to
Database 15 days Wed 26-12-18 Tue 15-01-19
Documenting the activities 2 days Wed 16-01-19 Thu 17-01-19
M3: Completion of Development
of application and website 0 days Thu 17-01-19 Thu 17-01-19
Testing 34 days Fri 18-01-19 Wed 06-03-19
Unit Testing 10 days Fri 18-01-19 Thu 31-01-19
System testing 7 days Fri 01-02-19 Mon 11-02-19
User acceptance testing 12 days Tue 12-02-19 Wed 27-02-19
Bug Fixing (if any) 5 days Thu 28-02-19 Wed 06-03-19
M4: Completion of Testing 0 days Wed 06-03-19 Wed 06-03-19
Training 12 days Thu 07-03-19 Fri 22-03-19
Developing training manuals 5 days Thu 07-03-19 Wed 13-03-19
Imparting training 7 days Thu 14-03-19 Fri 22-03-19
M5: Completion of Users'
Training 0 days Fri 22-03-19 Fri 22-03-19
Project Closure 7 days Mon 25-03-19 Tue 02-04-19
Completion of documenting 2 days Mon 25-03-19 Tue 26-03-19

13
ICT PROJECT MANAGEMENT
Record Archival 2 days Wed 27-03-19 Thu 28-03-19
Resource Release 1 day Fri 29-03-19 Fri 29-03-19
Client Sign off 2 days Mon 01-04-19 Tue 02-04-19
M6: Successful Project Closure 0 days Tue 02-04-19 Tue 02-04-19
Project ends 0 days Tue 02-04-19 Tue 02-04-19
3.5. Project Budget
The estimated cost and budget for each activity in the project are represented in the
following table-
Task Name Duration Cost
Development of i-Crop Application 132 days $209,176.00
Project Starts 0 days $0.00
Project Initiation 18 days $16,280.00
Understanding the Requirements of
the Project 5 days $4,800.00
Understanding the specifications of
the Website and the Application to be
developed
10 days $5,600.00
Documenting the Requirements 2 days $5,320.00
Sharing it with the Clients 1 day $560.00
M1: Completion of Requirements
Gathering 0 days $0.00
Project Planning 14 days $17,440.00
Planning the Implementation 7 days $6,160.00
Scheduling 2 days $1,760.00
Budget estimation 7 days $6,720.00
Resource Requirement 5 days $2,000.00
Resource Allocation 2 days $800.00
M2: Development and Approval of
Project Plan 0 days $0.00
Project Execution 47 days $150,720.00
Coding the Website 15 days $54,200.00
Coding the iCrop Application 30 days $83,400.00
Linking the i-Crop Application to
Database 15 days $7,800.00
Documenting the activities 2 days $5,320.00

14
ICT PROJECT MANAGEMENT
M3: Completion of Development of
application and website 0 days $0.00
Testing 34 days $10,336.00
Unit Testing 10 days $3,040.00
System testing 7 days $2,128.00
User acceptance testing 12 days $3,648.00
Bug Fixing (if any) 5 days $1,520.00
M4: Completion of Testing 0 days $0.00
Training 12 days $2,400.00
Developing training manuals 5 days $1,000.00
Imparting training 7 days $1,400.00
M5: Completion of Users' Training 0 days $0.00
Project Closure 7 days $12,000.00
Completion of documenting 2 days $5,320.00
Record Archival 2 days $5,000.00
Resource Release 1 day $560.00
Client Sign off 2 days $1,120.00
M6: Successful Project Closure 0 days $0.00
Project ends 0 days $0.00
4. Part Four
4.1. Assumptions
The assumptions that are made in this project are as follows-
1. It is assumed that the crop growers and the buyers will be comfortable in making use
of the application for their business purpose.
2. It is assumed that the project will be completed in the estimated schedule and budget.
3. It is assumed that the resource cost will not be increasing in the next six months
4. It is assumed that the project plan will be approved by Globex.
4.2. Risks

15
ICT PROJECT MANAGEMENT
The five major risks associated with each of phases of project methodology are as
follows-
1. Incorrect requirement analysis in the initiation phase
2. Non-approval of the Project plan due to issues in the implementation plan in the
planning phase
3. Incorrect project coding resulting in delays in the project execution phase
4. Failure in user acceptance testing in the Testing phase.
5. Issues with project evaluation in the project closure phase.
4.3. Risk Analysis
The analysing of the identified risks are discussed in the following table-
Risks Risk Responsibility Strategy
Incorrect Requirement Analysis Project Manager Project work will initiate only
after approval from Globex and
all the requirements outlined by
Globex should be documented
Project Plan Un approval Project Team The project pan will be made
according to the requirmenets
outlined by Globex
Incorrect Coding Coding Team Coding phase should be
monitored
Failure of user acceptance Testing team Project will not be released if the

16
ICT PROJECT MANAGEMENT
user acceptance fails
Issues in project Evaluation Project Manager and Project
Team
Project evaluation phase is
needed to be completed before
the project release and should be
supervised by the project
manager.
5. Part Five: Quality Management Plan
Quality management is important for ensuring that the project of right standard is
delivered. User acceptance test will therefore be performed that will help in checking whether
the objectives set by Globex have been fulfilled.
Apart from that, accurate monitoring of the project is essential in order to ensure that the
accurate quality standard of the project is achieved. The set of verification activities that are
identified for the project are as follows-
1. Requirement based testing is to be followed
2. Specification review of the project is to be carried out.
3. Code review will executed
The set of validation activities are as follows-
1. The project evaluation report will be generated.
2. Post implementation maintenance activities will be performed.

17
ICT PROJECT MANAGEMENT
6. Part Six
6.1. Annotated Bibliography
Turk, D., France, R., & Rumpe, B. (2014). Limitations of agile software processes. arXiv
preprint arXiv:1409.6600.
According to Turk, France and Rumpe (2014), project evaluation is one of the important
characteristic of management of project. One of project evaluation process in software
development includes rigorous evaluation of the software artifacts that ensure successful
completion of the project. Project evaluation is a process of systematic and objective assessment
of the ongoing or completed projects. Project evaluation helps in determining the relevance to
which the project has been successful in achieving the objectives of the project. Thus this is an
integral process of the project management and will ensure that the project fulfils the required
objectives. The process is lengthy as it involves collection and analysis of the vital activities,
characteristics and the outcomes of the project. Project evaluation is important mainly because it
improves the effectiveness of the project that is being implemented. Project evaluation is mainly
important for projects that are associated with software developing. This is because this method
helps in identification of the bugs and the issues in the project and further helps in its successful
elimination. Thus, it is clear that project evaluation is one of the vital characteristics of project
management.
Willcocks, L. P. (2013). 9 Evaluating the Outcomes of Information Systems Plans
Managing information technology evaluation—techniques and processes". Strategic
Information Management, 239.

18
ICT PROJECT MANAGEMENT
According to Willcocks (2013), Information technology project are important mainly
because IT represents substantial financial investments. Thus, accurate and appropriate
monitoring of this type of projects is essential. Inappropriate measures taken for project
evaluation can lead to project failure. The process of project evaluation is complex mainly
because of the fact that this phase of project management needs to analyse each and every
activities of the project to ensure that the project has been implemented according to the
objectives of the project and that all the objectives and the deliverables of the project has been
successfully met. However, it is often seen that in the process of managing and implementation
of a project, the phase of project evaluation is often neglected. If the project has been
implemented according to the objectives, there will not be any issue if this phase is skipped.
However, the main objective of project evaluation is to check whether the project has met its
expectations and the said objectives. IT evaluation therefore, should not be separated from the
business needs and this should be one of the vital stages of project management.
Agyei, W. (2015). Project planning and scheduling using PERT and CPM techniques with
linear programming: case study. International Journal of Scientific & Technology
Research, 4(8), 222-227.
According to Agyei (2015), one of the most widely used project evaluation technique is
making use of PERT, which is a tool for project evaluation. The Project Evaluation and Review
technique is widely adopted by the project management organizations with an aim of analysing
each of the activities associated with a project. It helps in analysing the flow of events and
further helps in estimating the actual time that is required to complete each task. The project will
only be successful only if the deliverables of the project are met within the time allocated for the
project. The method of PERT is quite similar to the critical path process and can be used for

19
ICT PROJECT MANAGEMENT
visualizing the project progress. Thus it is one of the most effective tools for project
management. PERT and CPM were developed in a similar time. It is seen that the project
managers often encounters problems in sequencing and estimating the works and the time
required and therefore this method can be used for easier management of all the tasks and the
activities associated with a project. Thus this method of project evaluation is quite effective and
hence used in projects of all types and sizes.
6.2. Closure Checklist
The project closure checklists are as follows-
Deliverables are handed off 
Documents are organised 
Payment Completion 
Finalizing and documenting the project reports 
Resource Release 
Project sign Off 
6.3. Project Evaluation
The measurable organizational Value will be calculated by evaluating the following
stages-
1. It will be checked whether the set deliverables of the project are met.
2. It will be checked whether the application is accepted by the client

20
ICT PROJECT MANAGEMENT
3. It will be checked whether the application is able to fulfil all the set criteria and the
requirements of Globex.
Thus project evaluation is an important phase for ensuring success in the project and is
important for evaluation of the measurable organizational values as well.

21
ICT PROJECT MANAGEMENT
Bibliography
Agyei, W. (2015). Project planning and scheduling using PERT and CPM techniques with linear
programming: case study. International Journal of Scientific & Technology
Research, 4(8), 222-227.
Beringer, C., Jonas, D., & Kock, A. (2013). Behavior of internal stakeholders in project portfolio
management and its impact on success. International Journal of Project
Management, 31(6), 830-846.
Binder, J. (2016). Global project management: communication, collaboration and management
across borders. Routledge.
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Heagney, J. (2016). Fundamentals of project management. Amacom.
Hwang, B. G., & Ng, W. J. (2013). Project management knowledge and skills for green
construction: Overcoming challenges. International Journal of Project
Management, 31(2), 272-284.
Kerzner, H. (2018). Project management best practices: Achieving global excellence. John
Wiley & Sons.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Larson, E. W., Gray, C. F., Danlin, U., Honig, B., & Bacarini, D. (2014). Project management:
The managerial process (Vol. 6). Grandview Heights, OH: McGraw-Hill Education.

22
ICT PROJECT MANAGEMENT
Leach, L. P. (2014). Critical chain project management. Artech House.
Marchewka, J. T. (2014). Information technology project management. John Wiley & Sons.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking
project management performance and project success. International journal of project
management, 32(2), 202-217.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Turk, D., France, R., & Rumpe, B. (2014). Limitations of agile software processes. arXiv
preprint arXiv:1409.6600.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Willcocks, L. P. (2013). 9 Evaluating the Outcomes of Information Systems Plans Managing
information technology evaluation—techniques and processes". Strategic Information
Management, 239.