Project Management: Scope, Resources, Milestones, and Quality Plan

This article discusses project management for i-Crop Website and Application Development. It covers the scope, resources, milestones, and quality plan, including measurable organizational value, area of impact, and metrics for success. It also explains the work breakdown structure, resource assignments, and estimates for each activity.

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

12
PROJECT MANAGEMENT
Linking the i-Crop Application to
Database 15 days Fri 28-12-18 Thu 17-01-19
Documentation 2 days Fri 18-01-19 Mon 21-01-19
M3: Completion of successful
Coding 0 days Mon 21-01-19 Mon 21-01-19
Testing 34 days Tue 22-01-19 Fri 08-03-19
Unit Testing 10 days Tue 22-01-19 Mon 04-02-19
System testing 7 days Tue 05-02-19 Wed 13-02-19
User acceptance testing 12 days Thu 14-02-19 Fri 01-03-19
Bug Fixing (if any) 5 days Mon 04-03-19 Fri 08-03-19
M4: Completion of Testing and
Bug Fixing 0 days Fri 08-03-19 Fri 08-03-19
Go Live and Training 12 days Mon 11-03-19 Tue 26-03-19
Website and Application
Demonstration 5 days Mon 11-03-19 Fri 15-03-19
Training and Maintenance 7 days Mon 18-03-19 Tue 26-03-19
M5: Successful Project Release 0 days Tue 26-03-19 Tue 26-03-19
Project Closure 12 days Wed 27-03-19 Thu 11-04-19
Documentation 2 days Wed 27-03-19 Thu 28-03-19
Record Archival 2 days Fri 29-03-19 Mon 01-04-19
Resource Release 1 day Tue 02-04-19 Tue 02-04-19
Payment Completion 7 days Wed 03-04-19 Thu 11-04-19
Client Sign off 2 days Wed 03-04-19 Thu 04-04-19
M6: Successful Project Closure 0 days Thu 04-04-19 Thu 04-04-19
Project ends 0 days Thu 04-04-19 Thu 04-04-19
3.5. Project Budget
The set budget of the project related to each activities in the project is represented in the
following table-
Task Name Duration Resource Names Cost
i-Crop Website and
Application Development 137 days $234,920.00
Start of the Project 0 days Project Manager $0.00
Initiation Phase 18 days $22,160.00
Requirements
Identification and
5 days Project Manager, Functional
Manager
$5,400.00

13
PROJECT MANAGEMENT
Gathering
Meeting with Globex to
Understand the
Requirements
10 days Project Manager, Functional
Manager $10,800.00
Specification
documentation 2 days Archive[1],Content writer $5,320.00
Sharing the documents
with the Clients 1 day Project Manager $640.00
M1:Successful
Completion of
Requirements Gathering
0 days $0.00
Planning Phase 14 days $17,240.00
Initiation of Project
Plan development 7 days Project Manager, Project
Supervisor $6,440.00
Scheduling the Project 2 days Project Manager, Project
Supervisor $1,840.00
Estimating the cost and
the Budget of Project 7 days Project Manager, Resource
Manager $6,720.00
Resource Allocation 5 days Resource Manager $1,600.00
Documenting the
Project Plan 2 days Resource Manager $640.00
M2: sharing and
Approval of Project Plan 0 days $0.00
Execution Phase 47 days $158,520.00
Coding the application
and the Website 15 days Coders, Website Go Live[1] $54,800.00
Database Development 30 days
Coders, Software
licensing[1],Database
Administrator
$90,600.00
Linking the i-Crop
Application to Database 15 days Coders, Database
Administrator $7,800.00
Documentation 2 days Archive[1],Content writer $5,320.00
M3: Completion of
successful Coding 0 days $0.00
Testing 34 days $9,520.00
Unit Testing 10 days Testers $2,800.00
System testing 7 days Testers $1,960.00
User acceptance testing 12 days Testers $3,360.00
Bug Fixing (if any) 5 days Testers $1,400.00
M4: Completion of
Testing and Bug Fixing 0 days $0.00
Go Live and Training 12 days $7,680.00
Website and 5 days Trainers, Functional Manager $3,200.00

14
PROJECT MANAGEMENT
Application Demonstration
Training and
Maintaianance 7 days Trainers, Functional Manager $4,480.00
M5: Successful Project
Release 0 days $0.00
Project Closure 12 days $19,800.00
Documentation 2 days Archive[1],Content writer $5,320.00
Record Archival 2 days Archive[1] $5,000.00
Resource Release 1 day Project Manager $640.00
Payment Completion 7 days Functional Manager, Project
Manager $7,560.00
Client Sign off 2 days Project Manager $1,280.00
M6: Successful Project
Closure 0 days $0.00
Project ends 0 days Project Manager $0.00
4. Part Four
4.1. Assumptions
The project undertaken by Virtucon incorporates certain assumptions, which are as
follows-
1. It has been assumed that the resource estimation of the project is accurate (Verzuh,
2015)
2. It has been assumed that the entire project can be completed in the set schedule.
3. It has been assumed that resources will remain available throughout the project
implementation phase.
4.2. Project Risks

15
PROJECT MANAGEMENT
There are certain issues and risk that are associated with this project. These are as
follows-
1. Budget Risk
2. Scheduling Risks
3. Resource shortages
4. Technical Risks
5. Operational Risks
4.3. Risk Analysis
The risks responsibility and the mitigation approaches of each of the identified risks are
as follows (Heagney, 2016)-
Risk Responsibility Mitigation
Budget Risk Project Manager Accurate Budget estimation in
the initiation stage
Scheduling Risks Project Manager Accurate project scheduling in
the initiation stage
Resource shortages Resource manager Responsibility of resource
manager to ensure continuous
resource flow
Technical Risks The Coders and Testers Can be mitigated by accurate
project monitoring and control
Operational Risks Functional Mangers Can be mitigated by

16
PROJECT MANAGEMENT
implementing the project
following the project
management plan.
5. Part Five: Quality Management Plan
Quality Management is important in project management particularly because it helps the
project manager to ascertain that the required project quality has been achieved (Leach, 2014).
As a part of the project implementation plan, the project team can design a set of verification and
validation activities (Marchewka, 2014). The verification activities are as follows-
1. Requirement Based testing of the software
2. Reviewing the test Specifications
The validation activities are as follows-
1. Reviewing the code
2. Review of the specification of the software
6. Part Six
6.2. Closure Checklist
The activities that will be verified prior to the project closure are as follows (Mir &
Pinnington, 2014)-
Handing of the Project Deliverables 

17
PROJECT MANAGEMENT
Payment Completion 
Completion of the documentation 
Resource Release 
6.3. Project Evaluation
Project evaluation is an important phase of project management (refer to appendix). The
MOV of the project will be measured in the project evaluation phase (Schwalbe, 2015). The
project evaluation phase will consist of following activities-
1. Requirements and Specifications rechecking
2. Checking if the objectives and goals are achieved
3. Collection of Feedbacks from the Client.

18
PROJECT MANAGEMENT
References
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.
Kiliç, M., & Kaya, İ. (2015). Investment project evaluation by a decision making methodology
based on type-2 fuzzy sets. Applied Soft Computing, 27, 399-410.

19
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.
Mohagheghi, V., Mousavi, S. M., Vahdani, B., & Shahriari, M. R. (2017). R&D project
evaluation and project portfolio selection by a new interval type-2 fuzzy optimization
approach. Neural Computing and Applications, 28(12), 3869-3888.
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

20
PROJECT MANAGEMENT
Appendix
Annotated 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.
According to Agyei (2015), the process of project evaluation can be related to a
systematic overview and assessment of a project that has been already completed in order to
analyse whether the project has been able to meet its objectives or not. PERT is a technique or
scheduling tool that is used in project management. PERT helps in easier identification of the
activities and the time required to complete each activity in the project. Project evaluations an
important part of project management and is widely used in information technology projects
(Agyei, 2015). PERT helps in identification of the major activities of the project quite easily and
therefore it is one of the most important tools for project management (Agyei, 2015). Another
similar tool that is used in management of the project includes the use of CPM. However, it is
more of a scheduling tool that a project evaluation tool (Agyei, 2015). There are other tools for
project evaluation, however, the use of PERT and CPM is most significant among them (Agyei,
2015). Project evaluation or post project evaluation is important for delivering the clients with
the project that they have specified for and thus this phase of the project is one of the most
important phases of project management.
Kiliç, M., & Kaya, İ. (2015). Investment project evaluation by a decision making
methodology based on type-2 fuzzy sets. Applied Soft Computing, 27, 399-410.

21
PROJECT MANAGEMENT
According to Kiliç & Kaya (2015), Project evaluation is important for a project
irrespective of which type of project it is. This is mainly because the process of project
evaluation helps in identification of the bugs and the issues associated with a project. The project
evaluation phase can be divided into a number of sub-phases. At first it is essential to identify the
criteria based on which the project will be evaluated. In most of the cases this criteria includes
the objectives and the goals of the project (Kiliç & Kaya, 2015). Different evaluation techniques
are followed in the evaluation while common one for most of the phases incorporates checking
whether the project is able to successfully achieve its target (Kiliç & Kaya, 2015). Followed by
that, it is checked whether the project is able to complete within the set schedule or not. It is
essential to complete the project within the set time as it is an important criterion for successful
project implementation. Apart from that, it is essential to ensure that set specifications of the
project are met prior to its implementation.
Mohagheghi, V., Mousavi, S. M., Vahdani, B., & Shahriari, M. R. (2017). R&D project
evaluation and project portfolio selection by a new interval type-2 fuzzy
optimization approach. Neural Computing and Applications, 28(12), 3869-3888.
According to Mohagheghi, Mousavi, Vahdani and Shahriari (2017), project evaluation is
important both for project and program management. Release of a project without the project
evaluation phase is considered as risky. This is because the project evaluation phase helps in
easier identification and rectifications of the bugs and the issues associated with a project. Thus
ensuring accurate project evaluation is important for a project and thus is considered to be one of
the most crucial phases of project management. Different models of project evaluation are
designed in order to ensure that the evaluation process of a project meets the desired
requirements (Mohagheghi et al., 2017). The project evaluation is information technology project

22
PROJECT MANAGEMENT
analyses and critically examines a program or a project as a whole. This phase gives an idea of
the program activities and the characteristics of a project. Thus it is essential for any project to
consider the project evaluation phase before the product or project release.