Detailed Project Management Plan for i-Crop Application Development

This project management plan outlines the development of the i-Crop application, including a detailed scope definition encompassing an online website and a smartphone application. It identifies key resources such as project managers, coding teams, and testing teams, along with their associated costs and responsibilities. The plan defines project milestones, activities, and tasks, using a Work Breakdown Structure (WBS) to organize the project. It also includes resource assignments, time estimates, and a project budget. The document further addresses project assumptions, risks (schedule, resource, budget, scope creep, and management issues), and a risk analysis. A quality management plan ensures that the project deliverables meet the desired quality standards. Finally, the plan provides a closure checklist and a project evaluation framework to assess the project's success.

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...........................................................................................................................3
2.1. Scope and Scope management..................................................................................3
2.2. List of Resources......................................................................................................4
3. Part Three.........................................................................................................................5
3.1. Milestone..................................................................................................................5
3.2. Activities/tasks..........................................................................................................5
3.3. Resource Assignments..............................................................................................6
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..........................................................................................................13
5. Part Five: Quality Management Plan.............................................................................14
6. Part Six...........................................................................................................................14
6.1. Closure Checklist....................................................................................................14
6.2. Project Evaluation...................................................................................................15
References..........................................................................................................................16

2
PROJECT MANAGEMENT
Appendix............................................................................................................................17
Annotated Bibliography.................................................................................................17

3
PROJECT MANAGEMENT
1. Part One
The measurable organizational value helps in identifying whether a particular project or
task is able to achieve its desired goal or not (Kerzner & Kerzner, 2017). The project associated
with the development of i-Crop application focuses on a major area of impact. The area of
impact corresponding to their ranking is represented in the following table-
Rank 1 Customer
Rank 2 Financial
Rank 3 Operational
Rank 4 Strategy
Rank 5 Social
The values the project will bring to the organization are as follows (Marchewka, 2014)-
1. Faster: The application and website will ensure faster transaction
2. Better: The project will enhance the process of managing the warehoused grains.
The metrics for measuring the MOV of the project are as follows-
1. To check whether the requirements of the project is met
2. To check if the project is fulfilling the goals of the project.
2. Part Two
2.1. Scope and Scope management

4
PROJECT MANAGEMENT
One of the essential needs of project management is identification and management of
the scope of the project (Larson, Gray, Danlin, Honig & Bacarini, 2014). The scope of the
project is to implement a online website and a smartphone application. The scope management
plan would incorporate regular monitoring and control of the project (Harrison & Lock, 2017).
Furthermore, it is the responsibility of the project manager to ensure that the scope of the project
is not changed in the implementation phase.
2.2. List of Resources
The list of resources associated with the project is as follows (Heagney, 2016)-
Resource Name Type Max. Units Std. Rate Ovt. Rate Cost/Use
Project Manager Work 100% $80.00/hr $0.00/hr $0.00
Resource Manager Work 200% $50.00/hr $0.00/hr $0.00
Functional Manager Work 200% $50.00/hr $0.00/hr $0.00
Coding team of
Virtucon
Work 800% $40.00/hr $0.00/hr $0.00
Testing Team of
Virtucon
Work 300% $40.00/hr $0.00/hr $0.00
Database Administrator Work 200% $6.00/hr $0.00/hr $0.00

5
PROJECT MANAGEMENT
Website and
Application Launch
Material $0.00 $50,000.00
Training Team by
Virtucon
Work 500% $35.00/hr $0.00/hr $0.00
Archive Material $0.00 $5,000.00
Document Manager Work 200% $25.00/hr $0.00/hr $0.00
3. Part Three
3.1. Milestone
The major milestones of the project are as follows-
M1: Project Approval
M2:Project Plan Approval
M3: Successful application and website development
M5: Successful Project Release
M6: Project Closes
3.2. Activities/tasks
The list of activities and the tasks are as follows-
WBS Task Name

6
PROJECT MANAGEMENT
0 Project by Globex and Virtucon
1 Initiation Phase
1.1 Identification of the Requirement specifications
1.2 Documentation
1.3 Sharing Documents
1.4 M1: Project Approval
2 Project Planning
2.1 Project Scheduling
2.2 Project Budget Estimation
2.3 Resource Estimation and Allocation
2.4 Development of Project Plan
2.5 M2:Project Plan Approval
3 Project Implementation
3.1 Interface Designing
3.2 Coding
3.3 Database Designing
3.4 Linking with the database
3.5 Documentation
3.6 M3: Successful application and website development
4 Testing
4.1 Alpha Testing
4.2 System testing
4.3 User acceptance testing
4.4 Bug Fixing (if any)
4.5 M4: Completion of Testing and Bug Fixing
5 Website and Application Go Live and Training
5.1 Application and Website launch
5.2 Training
5.3 Maintenance
5.4 M5: Successful Project Release
6 Project Closure
6.1 Payment Completion
6.2 Resource Release
6.3 Project Evaluation
6.4 Client Sign off
6.5 M6: Project Closes
3.3. Resource Assignments

7
PROJECT MANAGEMENT
The resource allocated to the project is as follows-
Task Name Duration Resource Names
Project by Globex and Virtucon 183 days
Initiation Phase 12 days
Identification of the Requirement
specifications 6 days Project Manager, Functional
Manager
Documentation 5 days Archive[1],Document Manger
Sharing Documents 1 day Document Manger
M1: Project Approval 0 days
Project Planning 21 days
Project Scheduling 2 days Functional Manager
Project Budget Estimation 10 days
Resource Estimation and Allocation 4 days Resource Manager
Development of Project Plan 5 days Functional Manager
M2:Project Plan Approval 0 days
Project Implementation 61 days
Interface Designing 20 days Coding team of Virtucon
Coding 25 days Coding team of Virtucon, Website
and Application Launch[1]
Database Designing 30 days Coding team of Virtucon, Database
Administrator
Linking with the database 10 days Coding team of Virtucon, Database
Administrator
Documentation 1 day Archive[1],Document Manger
M3: Successful application and
website development 0 days
Testing 47 days
Alpha Testing 10 days Testing Team of Virtucon
System testing 12 days Testing Team of Virtucon
User acceptance testing 15 days Testing Team of Virtucon
Bug Fixing (if any) 10 days Testing Team of Virtucon
M4: Completion of Testing and
Bug Fixing 0 days
Website and Application Go Live
and Training 42 days
Application and Website launch 10 days Project Manager, Functional
Manager
Training 12 days Training Team by Virtucon,
Functional Manager
Maintenance 20 days Functional Manager, Training Team

8
PROJECT MANAGEMENT
by Virtucon
M5: Successful Project Release 0 days
Project Closure 15 days
Payment Completion 5 days Archive[1]
Resource Release 2 days Project Manager
Project Evaluation 8 days Functional Manager, Project
Manager
Client Sign off 1 day Project Manager
M6: Project Closes 0 days
3.4. Estimates for Each Activity
The time estimate for each project activities is as follows-
WBS Task Name Duration Start Finish
0 Project by Globex and
Virtucon 183 days Wed 12-09-18 Fri 24-05-19
1 Initiation Phase 12 days Wed 12-09-18 Thu 27-09-18
1.1 Identification of the
Requirement specifications 6 days Wed 12-09-18 Wed 19-09-18
1.2 Documentation 5 days Thu 20-09-18 Wed 26-09-18
1.3 Sharing Documents 1 day Thu 27-09-18 Thu 27-09-18
1.4 M1: Project Approval 0 days Thu 27-09-18 Thu 27-09-18
2 Project Planning 21 days Fri 28-09-18 Fri 26-10-18
2.1 Project Scheduling 2 days Fri 28-09-18 Mon 01-10-18
2.2 Project Budget Estimation 10 days Tue 02-10-18 Mon 15-10-18
2.3 Resource Estimation and
Allocation 4 days Tue 16-10-18 Fri 19-10-18
2.4 Development of Project Plan 5 days Mon 22-10-18 Fri 26-10-18
2.5 M2:Project Plan Approval 0 days Fri 26-10-18 Fri 26-10-18
3 Project Implementation 61 days Mon 29-10-18 Mon 21-01-19
3.1 Interface Designing 20 days Mon 29-10-18 Fri 23-11-18
3.2 Coding 25 days Mon 26-11-18 Fri 28-12-18
3.3 Database Designing 30 days Mon 26-11-18 Fri 04-01-19
3.4 Linking with the database 10 days Mon 07-01-19 Fri 18-01-19
3.5 Documentation 1 day Mon 21-01-19 Mon 21-01-19
3.6 M3: Successful application
and website development 0 days Mon 21-01-19 Mon 21-01-19
4 Testing 47 days Tue 22-01-19 Wed 27-03-19

9
PROJECT MANAGEMENT
4.1 Alpha Testing 10 days Tue 22-01-19 Mon 04-02-19
4.2 System testing 12 days Tue 05-02-19 Wed 20-02-19
4.3 User acceptance testing 15 days Thu 21-02-19 Wed 13-03-19
4.4 Bug Fixing (if any) 10 days Thu 14-03-19 Wed 27-03-19
4.5 M4: Completion of Testing
and Bug Fixing 0 days Wed 27-03-19 Wed 27-03-19
5 Website and Application Go
Live and Training 42 days Thu 28-03-19 Fri 24-05-19
5.1 Application and Website
launch 10 days Thu 28-03-19 Wed 10-04-19
5.2 Training 12 days Thu 11-04-19 Fri 26-04-19
5.3 Maintenance 20 days Mon 29-04-19 Fri 24-05-19
5.4 M5: Successful Project
Release 0 days Fri 26-04-19 Fri 26-04-19
6 Project Closure 15 days Mon 29-04-19 Fri 17-05-19
6.1 Payment Completion 5 days Mon 29-04-19 Fri 03-05-19
6.2 Resource Release 2 days Mon 06-05-19 Tue 07-05-19
6.3 Project Evaluation 8 days Wed 08-05-19 Fri 17-05-19
6.4 Client Sign off 1 day Wed 08-05-19 Wed 08-05-19
6.5 M6: Project Closes 0 days Wed 08-05-19 Wed 08-05-19
The Gantt chart of the project is represented in the picture below-

10
PROJECT MANAGEMENT

11
PROJECT MANAGEMENT
Figure 1: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)
The WBS of the project is represented below-
Project by Globex and
Virtucon
Initiation Phase
Identification of the
Requirmenet
specifications
Docuemntation
Sharing Documents
M1: Project Approv al
Project Planning
Project Scheduling
Project Budget Estimation
Resource Estim ation and
Allocation
Dv elopem ent of Project
Plan
M2: Project Plan Approv al
Project Implementation
Interface Designing
Coding
Database Designing
Linking with the database
Documentation
M3: Successful
application and w ebsite
dev elopment
Testing
Alpha Testing
System testing
User acceptance testing
Bug Fix ing (if
any )M4: Completion of Testing
and Bug Fix ing
Website and Application
Go Liv e and Training
Application and Website
launch
Training
Maintennanace
M5: Successful Project
Release
Project Closure
Pay em ent
CompletionResource Release
Project Ev aluation
Client Sign off
M6: Project Closes
Figure 2: Representing the WBS of the Project
(Source: generated by author using MS schedule Pro)
3.5. Project Budget
The budget estimated for the project is represented in the following table-
WBS Task Name Resource Names Cost
0 Project by Globex and
Virtucon $163,600.00
1 Initiation Phase $12,440.00
1.1 Identification of the
Requirement specifications
Project Manager, Functional
Manager $6,240.00
1.2 Documentation Archive[1],Document Manager $6,000.00
1.3 Sharing Documents Document Manager $200.00
1.4 M1: Project Approval $0.00
2 Project Planning $4,400.00
2.1 Project Scheduling Functional Manager $800.00
2.2 Project Budget $0.00

12
PROJECT MANAGEMENT
Estimation
2.3 Resource Estimation and
Allocation Resource Manager $1,600.00
2.4 Development of Project Plan Functional Manager $2,000.00
2.5 M2:Project Plan
Approval $0.00
3 Project Implementation $84,320.00
3.1 Interface Designing Coding team of Virtucon $6,400.00
3.2 Coding Coding team of Virtucon, Website
and Application Launch[1] $58,000.00
3.3 Database Designing Coding team of Virtucon,
Database Administrator $11,040.00
3.4 Linking with the database Coding team of Virtucon,
Database Administrator $3,680.00
3.5 Documentation Archive[1],Document Manager $5,200.00
3.6
M3: Successful
application and website
development
$0.00
4 Testing $15,040.00
4.1 Alpha Testing Testing Team of Virtucon $3,200.00
4.2 System testing Testing Team of Virtucon $3,840.00
4.3 User acceptance testing Testing Team of Virtucon $4,800.00
4.4 Bug Fixing (if any) Testing Team of Virtucon $3,200.00
4.5 M4: Completion of
Testing and Bug Fixing $0.00
5 Website and Application
Go Live and Training $32,160.00
5.1 Application and Website
launch
Project Manager, Functional
Manager $10,400.00
5.2 Training Training Team by Virtucon,
Functional Manager $8,160.00
5.3 Maintenance Functional Manager, Training
Team by Virtucon $13,600.00
5.4 M5: Successful Project
Release $0.00
6 Project Closure $15,240.00
6.1 Payment Completion Archive[1] $5,000.00
6.2 Resource Release Project Manager $1,280.00
6.3 Project Evaluation Functional Manager, Project
Manager $8,320.00
6.4 Client Sign off Project Manager $640.00
6.5 M6: Project Closes $0.00

13
PROJECT MANAGEMENT
4. Part Four
4.1. Assumptions
While development of the project plan, it is essential to understand the assumptions
associated with the project (Nicholas & Steyn, 2017). The assumptions considered in this project
are as follows-
1. Project should be completed within a scheduled time
2. The resources needed in the project should be readily available.
4.2. Project Risks
The risks associated with the project are as follows-
1. Schedule Risk
2. Resource Risk
3. Budget Risk
4. Risk of scope creep
5. Management Issue
4.3. Risk Analysis
Risk Responsibility Mitigation
1. Schedule Risk Project manager Risk Reduction

14
PROJECT MANAGEMENT
2. Resource Risk
(Marcelino-Sádaba, Pérez-
Ezcurdia, Lazcano & Villanueva,
2014)
Resource Head Risk Avoidance
Budget Risk Globex Risk Transfer
4. Risk of scope creep Project Manager Risk Accept
5. Management Issue Virtucon Risk Avoidance
5. Part Five: Quality Management Plan
Quality Management is an important aspect of project management. With quality
management, it is possible to ensure that the project that is being delivered is of desired quality.
In order to ensure that a project of appropriate quality will be delivered, the team will be
following a set of verification and validation activities, which are as follows-
1. Review of the specifications of the project
2. Reviewing the Code
3. Requirements based Testing
4. Training of the verification activities
6. Part Six
6.1. Closure Checklist

15
PROJECT MANAGEMENT
The checklist that is prepared for the project includes checking and review of the
following items. These are as follows (Martinelli & Milosevic, 2016 )-
1. Reviewing the deliverables
2. Documenting the project
3. Reporting the Project Status
4 Resource Release
6.2. Project Evaluation
Evaluation of the project is important to check whether the project deliverables are
meeting a desired standard (refer to appendix). The project evaluation activities that will be
followed in the project are as follows (Desmond, 2014)-
1. The specification of the project is needed to be checked.
2. It is to be ensured that the goals of the project have been achieved.

16
PROJECT MANAGEMENT
References
Davis, K. (2014). Different stakeholder groups and their perceptions of project
success. International journal of project management, 32(2), 189-201.
Desmond, C. (2014). Project management tools. IEEE Engineering Management Review, 42(4),
11-12.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach.
Routledge.
Heagney, J. (2016). Fundamentals of project management. Amacom.
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.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project
risk management methodology for small firms. International journal of project
management, 32(2), 327-340
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project
risk management methodology for small firms. International journal of project
management, 32(2), 327-340.
Marchewka, J. T. (2014). Information technology project management. John Wiley & Sons.
Martinelli, R. J., & Milosevic, D. Z. (2016). Project management toolbox: tools and techniques
for the practicing project manager. John Wiley & Sons.
Martinsuo, M. (2013). Project portfolio management in practice and in context. International
Journal of Project Management, 31(6), 794-803.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Routledge.

17
PROJECT MANAGEMENT
Appendix
Annotated Bibliography
Martinsuo, M. (2013). Project portfolio management in practice and in
context. International Journal of Project Management, 31(6), 794-803.
According the Martinsuo (2013), portfolio management is an important aspect of project
management. An accurate portfolio management further helps in easier project evaluation during
the project closure phase. It is essential to appropriately manage the evaluation of project. Project
evaluation is one of the most important needs of project management. The most significant aim
of the project management phase is to ensure that the project meets the accurate standard of
project implementation. The work of project implementation phase is to consider all the issues,
pros and cons of a project. Portfolio is a major project management tool that ensures easier
documentation of the project activities in the project (Martinsuo, 2013). Thus portfolios can help
in easier implementation of project evaluation phase as well. Since the activities are already
documented, it becomes easier for project evaluation. Project evaluation is a technique for
reviewing the project activities and to assess to the extent to which the values of the organization
has been achieved. Thus project evaluation can be considered as an important tool for project
management and implementation of a project along with project closure.
Davis, K. (2014). Different stakeholder groups and their perceptions of project
success. International journal of project management, 32(2), 189-201.
According to Davis (2014), managing the stakeholders of the project is an important
consideration since stakeholders are often the most important investors of the project. Keeping
up to the expectation of the stakeholders of the project is important for ensuring that the projects

18
PROJECT MANAGEMENT
are completed in a successful manner. The stakeholders of the project play a significant role in
management of the project and therefore it is essential to ensure that the project stakeholders are
rightly management. One of the needs of project evaluation phase is to provide the stakeholders
with the activity and project completion report so that they can have an easier idea of the project
completion. The need for managing the issues associated with the project gives rise to the need
of project evaluation phase. Evaluation of the project is not only important for the stakeholders
but for the project managers as well. It helps the project manager to ensure that the project is
rightly managed and that the needed project standard is met.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014).
Project risk management methodology for small firms. International journal of
project management, 32(2), 327-340
According to Marcelino-Sádaba, Pérez-Ezcurdia, Lazcano & Villanueva (2014),
management of risks is an important aspect of project management. Risk management is an
important criterion of ensuring a successful project as it unveils the different issues associated
with the project. Project evaluation is a part for risk management process in project as it unveils
the risks and the issues associated with the project. The need for management of the risks in the
project suggests appropriate project evaluation. There are a number of activities that are
undertaken in the project evaluation phase (Marcelino-Sádaba et al., 2014). The most significant
activity that is performed in the project evaluation phase includes checking the specifications of
the project and generating the reports accordingly. The project evaluation phase further ensures
easier mitigation and management of the risks associated with the project (Marcelino-Sádaba et
al., 2014). Every project irrespective of its size needs to adhere to project evaluation phase for
accurate report generation. The generated reports further help in easier risk management

19
PROJECT MANAGEMENT
(Marcelino-Sádaba et al., 2014). Thus it can be said that project management should involve
evaluation phase of the project. Evaluation of the project is therefore advantageous for project
and helps in efficient risk management in the project.