Project Management

This project management guide covers scope management, resource assignments, estimates for each activity, and more.

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..........................................................................................................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..........................................................................................................14
5. Part Five: Quality Management Plan.............................................................................14
6. Part Six...........................................................................................................................15
6.1. Closure Checklist....................................................................................................15
6.2. Project Evaluation...................................................................................................15
References..........................................................................................................................16

2
PROJECT MANAGEMENT
Appendix............................................................................................................................18
Annotated Bibliography.................................................................................................18

3
PROJECT MANAGEMENT
1. Part One
The measurable organization value provides a clear definition of the success and the
objectives of the project (Martinelli & Milosevic, 2016). The goal of this project is to develop an
application and a website that will help the crop growers and the buyers in easier dealing with
the warehoused grains. The desired areas that the project will have an impact on include
customer, operational, financial and strategy. The ranking of the area of impact according to their
importance are as follows-
Area of Impact Ranking
Customer 1
Operational 2
Financial 3
Strategy 4
The values that i-crop application development project will bring to the company are as follows-
Do More: The Company wants to continue its growth by improving the ease of access and
management of the warehoused grains by development of an online website and a smartphone
application.
Faster: With the use of online website the buyers and the growers will be able to easily deal
with the warehoused grains thus increasing the efficiency of the process.
The metrics that will help in easier measurement of the measurable organizational value are as
follows-

4
PROJECT MANAGEMENT
1. It is to be checked whether the project has been able to fulfill the required deliverables.
2. It is to be ensured that no scope creep has occurred in the project.
The timeframe for achieving the MOV will be 5 months from the start date of the project.
2. Part Two
2.1. Scope and Scope management
It is essential to identify the scope of the project. For efficient scope management it is
essential to identify the accurate scope of the project. The main aim or scope of this project is to
develop and implement the website and the application in an inexpensive manner and therefore
the scope management in this project is essential (Desmond, 2014). As a part of scope
management, it is necessary to ensure that the project does not suffer scope creep. Furthermore,
resource management is quite vital for implementation of this project (Rolstadås, Tommelein,
Morten Schiefloe & Ballard, 2014). The list of resources associated with this project is
represented in the following section.
2.2. List of Resources
The resources associated with this project are as follows-
Resource Name Type Max. Units Std. Rate Cost/Use
Project Manager Work 100% $95.00/hr $0.00
Resource Manager Work 100% $40.00/hr $0.00
Functional Manager Work 200% $35.00/hr $0.00
Supervisor From Globex Work 200% $40.00/hr $0.00
Supervisor from Virtucon Work 100% $65.00/hr $0.00
Virtucon Coding Team Work 1,000% $30.00/hr $0.00
Virtucon Testing Team Work 200% $30.00/hr $0.00
Database Administrator Work 100% $30.00/hr $0.00

5
PROJECT MANAGEMENT
Software licensing Fee Material $0.00 $75,000.00
Website and Application
Launch Material $0.00 $50,000.00
Virtucon Training Team Work 400% $20.00/hr $0.00
Archive Material $0.00 $5,000.00
Document handler Work 100% $15.00/hr $0.00
3. Part Three
3.1. Milestone
The major milestones associated with this project are as follows-
M1: Requirements and the Specification of the project are gathered
M2: Preparation and Approval of Project Plan
M3: Successful application and website development
M4: Completion of Testing and Bug Fixing
M5: Successful Project Release
M6: Project Closes
3.2. Activities/tasks
The list of activities or tasks the project will fulfill are as follows-
WBS Task Name
0 i-Crop Project Implementation
1 Initiation Phase
1.1 Setting up a meeting with the Clients
1.2 Identification of the Requirement specifications
1.3 Specification documentation

6
PROJECT MANAGEMENT
1.4 Documenting the findings
1.5 M1: Requirements and the Specification of the project are
gathered
2 Project Planning
2.1 Setting the structure of Project Plan
2.2 Project Scheduling
2.3 Project Budget Estimation
2.4 Resource Estimation
2.5 Resource Allocation
2.6 M2: Preparation and Approval of Project Plan
3 Project Implementation
3.1 Interface Designing
3.2 Software 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 Unit 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 Website and Application Demonstration
5.2 Training and Maintenance
5.3 Post Launch Support
5.4 M5: Successful Project Release
6 Project Closure
6.1 Document archival
6.2 Payment Completion
6.3 Resource Release
6.4 Project Evaluation
6.5 Client Sign off
6.6 M6: Project Closes
3.3. Resource Assignments

7
PROJECT MANAGEMENT
The Resources that has been assigned to each of the tasks or activities in the project is
represented in the following table-
WBS Task Name Resource Names
0 i-Crop Project Implementation
1 Initiation Phase
1.1 Setting up a meeting with the Clients Functional Manager
1.2 Identification of the Requirement
specifications Project Manager, Functional Manager
1.3 Specification documentation Archive[1],Document handler
1.4 Documenting the findings Document handler
1.5
M1: Requirements and the
Specification of the project are
gathered
2 Project Planning
2.1 Setting the structure of Project Plan Supervisor from Virtucon, Supervisor
From Globex
2.2 Project Scheduling Functional Manager, Supervisor From
Globex
2.3 Project Budget Estimation Supervisor From Globex
2.4 Resource Estimation Resource Manager
2.5 Resource Allocation Resource Manager
2.6 M2: Preparation and Approval of
Project Plan
3 Project Implementation
3.1 Interface Designing Virtucon Coding Team
3.2 Software Coding Virtucon Coding Team, Website and
Application Launch[1]
3.3 Database Designing Virtucon Coding Team, Software
licensing Fee[1],Database Administrator
3.4 Linking with the database Virtucon Coding Team, Database
Administrator
3.5 Documentation Archive[1],Document handler
3.6 M3: Successful application and
website development
4 Testing
4.1 Unit Testing Virtucon Testing Team
4.2 System testing Virtucon Testing Team
4.3 User acceptance testing Virtucon Testing Team
4.4 Bug Fixing (if any) Virtucon Testing Team
4.5 M4: Completion of Testing and

8
PROJECT MANAGEMENT
Bug Fixing
5 Website and Application Go Live
and Training
5.1 Website and Application
Demonstration
Virtucon Training Team ,Functional
Manager
5.2 Training and Maintenance Virtucon Training Team ,Functional
Manager
5.3 Post Launch Support Functional Manager,Virtucon Training
Team
5.4 M5: Successful Project Release
6 Project Closure
6.1 Document archival Archive[1],Document handler
6.2 Payment Completion Archive[1]
6.3 Resource Release Project Manager
6.4 Project Evaluation Functional Manager, Project Manager
6.5 Client Sign off Project Manager
6.6 M6: Project Closes
3.4. Estimates for Each Activity
The time estimates for each activity is represented as follows-
Task Name Duration Start Finish
i-Crop Project Implementation 164 days Tue 02-10-18 Fri 17-05-19
Initiation Phase 22 days Tue 02-10-18 Wed 31-10-18
Setting up a meeting with the
Clients 6 days Tue 02-10-18 Tue 09-10-18
Identification of the Requirement
specifications 11 days Wed 10-10-18 Wed 24-10-18
Specification documentation 3 days Thu 25-10-18 Mon 29-10-18
Documenting the findings 2 days Tue 30-10-18 Wed 31-10-18
M1: Requirements and the
Specification of the project are
gathered
0 days Wed 31-10-18 Wed 31-10-18
Project Planning 16 days Thu 01-11-18 Thu 22-11-18
Setting the structure of Project
Plan 8 days Thu 01-11-18 Mon 12-11-18
Project Scheduling 3 days Tue 13-11-18 Thu 15-11-18
Project Budget Estimation 8 days Tue 13-11-18 Thu 22-11-18
Resource Estimation 6 days Tue 13-11-18 Tue 20-11-18

9
PROJECT MANAGEMENT
Resource Allocation 1 day Wed 21-11-18 Wed 21-11-18
M2: Preparation and Approval
of Project Plan 0 days Wed 21-11-18 Wed 21-11-18
Project Implementation 46 days Thu 22-11-18 Thu 24-01-19
Interface Designing 15 days Thu 22-11-18 Wed 12-12-18
Software Coding 20 days Thu 13-12-18 Wed 09-01-19
Database Designing 15 days Thu 13-12-18 Wed 02-01-19
Linking with the database 13 days Thu 03-01-19 Mon 21-01-19
Documentation 3 days Tue 22-01-19 Thu 24-01-19
M3: Successful application and
website development 0 days Thu 24-01-19 Thu 24-01-19
Testing 41 days Fri 25-01-19 Fri 22-03-19
Unit Testing 8 days Fri 25-01-19 Tue 05-02-19
System testing 15 days Wed 06-02-19 Tue 26-02-19
User acceptance testing 10 days Wed 27-02-19 Tue 12-03-19
Bug Fixing (if any) 8 days Wed 13-03-19 Fri 22-03-19
M4: Completion of Testing and
Bug Fixing 0 days Fri 22-03-19 Fri 22-03-19
Website and Application Go Live
and Training 32 days Mon 25-03-19 Tue 07-05-19
Website and Application
Demonstration 7 days Mon 25-03-19 Tue 02-04-19
Training and Maintenance 10 days Wed 03-04-19 Tue 16-04-19
Post Launch Support 15 days Wed 17-04-19 Tue 07-05-19
M5: Successful Project Release 0 days Tue 16-04-19 Tue 16-04-19
Project Closure 23 days Wed 17-04-19 Fri 17-05-19
Document archival 3 days Wed 17-04-19 Fri 19-04-19
Payment Completion 7 days Mon 22-04-19 Tue 30-04-19
Resource Release 3 days Wed 01-05-19 Fri 03-05-19
Project Evaluation 10 days Mon 06-05-19 Fri 17-05-19
Client Sign off 1 day Mon 06-05-19 Mon 06-05-19
M6: Project Closes 0 days Mon 06-05-19 Mon 06-05-19
The scheduled Gantt Chart for the project is represented in the following picture-

10
PROJECT MANAGEMENT

11
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 Project
Implementation
Initiation Phase
Setting up a meeting with
the Cleints
Identification of the
Requirmenet
specifications
Specification
documentation
Documenting the
findingsM1: Requirements and
the Specification of the
project are gathered
Project Planning
Setting the structure of
Project Plan
Project Scheduling
Project Budget Estimation
Resource Estimation
Resource Allocation
M2: Preparation and
Approval of Project Plan
Project Implementation
Interface Designing
Software Coding
Database Designing
Linking with the database
Documentation
M3: Successful
application and website
development
Testing
Unit Testing
System testing
User acceptance testing
Bug Fixing (if
any)M4: Completion of Testing
and Bug Fixing
Website and Application
Go Live and Training
Website and Application
Demonstration
Training and
Maintaianance
Post Launch Support
M5: Successful Project
Release
Project Closure
Document archival
Payement
CompletionResource Release
Project Evaluation
Client Sign off
M6: Project Closes
Figure 2: Representing the work breakdown structure of the project
(Source: created by author using MS schedule Pro)
3.5. Project Budget
The estimated budget of the project is as follows-
Task Name Duration Resource Names Cost
i-Crop Project
Implementation 164 days $231,960.00
Initiation Phase 22 days $18,720.00
Setting up a meeting
with the Clients 6 days Functional Manager $1,680.00
Identification of the
Requirement specifications 11 days Project Manager, Functional
Manager $11,440.00
Specification
documentation 3 days Archive[1],Document handler $5,360.00
Documenting the
findings 2 days Document handler $240.00

12
PROJECT MANAGEMENT
M1: Requirements and
the Specification of the
project are gathered
0 days $0.00
Project Planning 16 days $13,320.00
Setting the structure of
Project Plan 8 days Supervisor from Virtucon,
Supervisor From Globex $6,720.00
Project Scheduling 3 days Functional Manager,
Supervisor From Globex $1,800.00
Project Budget
Estimation 8 days Supervisor From Globex $2,560.00
Resource Estimation 6 days Resource Manager $1,920.00
Resource Allocation 1 day Resource Manager $320.00
M2: Preparation and
Approval of Project Plan 0 days $0.00
Project Implementation 46 days $152,200.00
Interface Designing 15 days Virtucon Coding Team $3,600.00
Software Coding 20 days
Virtucon Coding Team,
Website and Application
Launch[1]
$54,800.00
Database Designing 15 days
Virtucon Coding Team,
Software licensing
Fee[1],Database Administrator
$82,200.00
Linking with the
database 13 days Virtucon Coding Team,
Database Administrator $6,240.00
Documentation 3 days Archive[1],Document handler $5,360.00
M3: Successful
application and website
development
0 days $0.00
Testing 41 days $9,840.00
Unit Testing 8 days Virtucon Testing Team $1,920.00
System testing 15 days Virtucon Testing Team $3,600.00
User acceptance testing 10 days Virtucon Testing Team $2,400.00
Bug Fixing (if any) 8 days Virtucon Testing Team $1,920.00
M4: Completion of
Testing and Bug Fixing 0 days $0.00
Website and Application
Go Live and Training 32 days $14,080.00
Website and Application
Demonstration 7 days Virtucon Training
Team ,Functional Manager $3,080.00
Training and
Maintenance 10 days Virtucon Training
Team ,Functional Manager $4,400.00
Post Launch Support 15 days Functional Manager, Virtucon
Training Team $6,600.00

13
PROJECT MANAGEMENT
M5: Successful Project
Release 0 days $0.00
Project Closure 23 days $23,800.00
Document archival 3 days Archive[1],Document handler $5,360.00
Payment Completion 7 days Archive[1] $5,000.00
Resource Release 3 days Project Manager $2,280.00
Project Evaluation 10 days Functional Manager, Project
Manager $10,400.00
Client Sign off 1 day Project Manager $760.00
M6: Project Closes 0 days $0.00
4. Part Four
4.1. Assumptions
For accurate project implementation certain project assumptions are made. These
assumptions are as follows-
1. It is assumed that the project can be completed in a constricted budget
2. It is assumed that the resources will remain available throughout the project
implementation phase.
4.2. Project Risks
There are certain risks associated with the implementation of the project which are as
follows (Pritchard & PMP, 2014)-
1. Risk of improper scheduling
2. Risk of inaccurate coding
3. Risk of resource shortage

14
PROJECT MANAGEMENT
4. Budget Risk (Serrador & Turner, 2014).)
5. Risk of scope creep
These risks are analyzed in the following section
4.3. Risk Analysis
The project risk are analyzed in the following table-
Risk Responsibility Mitigation strategy
Risk of improper scheduling
(Hopkin, 2018)
Project Manager Risk Avoidance
Risk of inaccurate coding Coding Team Risk Reduction
Risk of resource shortage Resource Manager Risk Transfer
Budget Risk Project Manager Risk Reduction
Risk of scope creep Project Manager Risk Accept
5. Part Five: Quality Management Plan
Quality management is one of the most significant aspects of the project. Quality
management ensures that a particular project will be delivered according to the given
specifications. For accurate quality management, verification and validation activities will be
implemented in the project. The identified verification and the validation activities are as
follows-
1. Specification Review
2. Code Review

15
PROJECT MANAGEMENT
6. Part Six
6.1. Closure Checklist
Closure checklist is an important tool that enables the project manager to ensure that the
project has been appropriately implemented (Aven, 2016). The project checklist for this project
will have following components-
Checking whether the deliverables of the project are met
Documenting the Reports
Release of the resources
Procurement completion
Project sign off
6.2. Project Evaluation
Project evaluation is important for project management as that standard of the project is
validated by project evaluation (refer to appendix). The project validation activities that will be
followed in the project are as follows (Badewi, 2016)-
1. The objectives of the project are reviewed and will be matched to the project
implementation (Lech, 2013)
2. The specification of the application and the website that is developed will be reviewed.

16
PROJECT MANAGEMENT
References
Aven, T. (2016). Risk assessment and risk management: Review of recent advances on their
foundation. European Journal of Operational Research, 253(1), 1-13.
Badewi, A. (2016). The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework. International Journal of Project Management, 34(4), 761-778.
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.
Hopkin, P. (2018). Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers.
Lech, P. (2013). Time, budget, and functionality?—IT project success criteria
revised. Information Systems Management, 30(3), 263-275.
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.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. Auerbach
Publications.

17
PROJECT MANAGEMENT
Rolstadås, A., Tommelein, I., Morten Schiefloe, P., & Ballard, G. (2014). Understanding project
success through analysis of project management approach. International journal of
managing projects in business, 7(4), 638-660.
Serrador, P., & Turner, J. R. (2014). The relationship between project success and project
efficiency. Procedia-Social and Behavioral Sciences, 119, 75-84.
Todorović, M. L., Petrović, D. Č., Mihić, M. M., Obradović, V. L., & Bushuyev, S. D. (2015).
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), 772-783.

18
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 to Martinsuo (2013), one of the important aspects of project management is
appropriate project evaluation. The technique of project evaluation is mainly based on the
evaluating whether the project has worked according to the desired objectives or not. It is
essential to understand that the importance of project evaluation in project management. Project
portfolio management is an important aspect for project management and it further helps in
project evaluation as well. The process project evaluation helps deals with the systematic
analysis of tasks and the activities associated with a project. Every aspect of a project is
measured in the project evaluation phase with appropriate tools and techniques. It is essential to
understand the process of project evaluation as it differs in different project. For information
technology project, project evaluation is an important phase and it ensures accurate project
delivery. The reports generated in this phase helps in easier identification of all the vital activities
associated with a project and helps in its easier delivery as well. The main aim of project
evaluation phase is to verify and validate the different tasks and the activities associated with a
project. In project evaluation phase, each activities and aspect of the project is accurately
measured.
Davis, K. (2014). Different stakeholder groups and their perceptions of project
success. International journal of project management, 32(2), 189-201.

19
PROJECT MANAGEMENT
According to Davis (2014), stakeholders are an important part of project management
and therefore, keeping the stakeholders engaged is an important aspect of project management.
For this, the project should incorporate all the requirements as specified by the stakeholders of
the project. The project evaluation phase checks and ensures whether all the requirements of the
project are met. The reports that are generated in the project evaluation phase are generally
shared with the project stakeholders. Appropriate report generation is one of the important
aspects of project evaluation and therefore, the project evaluation phase is considered to be one
of the most vital stages of the project. It is therefore essential to ensure that the project is
appropriately implemented and the project evaluation phase is correctly followed. The project
evaluation phase can be divided into three major phase, which are pre project evaluation,
ongoing, post project evaluation. In each of the phases of project evaluation, the requirement of
the project along with the specifications is verified that helps in easier report generation. Thus
project evaluation is one of the most important phases of project management.
Todorović, M. L., Petrović, D. Č., Mihić, M. M., Obradović, V. L., & Bushuyev, S. D.
(2015). Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), 772-783.
According to Todorović, Petrović, Mihić, Obradović & Bushuyev (2015), the success of
a project largely depends on accurate project evaluation. The project evaluation process is
important for managing the project closure phase. The success of the project largely depends on
accurate project closure, which can be achieved by successful project implementation. Project
evaluation is one of the most essential phases of project management since it ensures appropriate
project delivery by matching the delivered project with the specifications of the project. Project
manager is mainly responsible for arranging the project evaluation. It is therefore the

20
PROJECT MANAGEMENT
responsibility of the project manager to ensure that the project is successfully implemented and
the delivered project meets its specifications. Thus project evaluation is important for project
management as it is one of the most important techniques for ensuring project success. The
validation along with the verification activities in the project is mainly performed in the project
implementation stage. Thus accurate project implementation and project evaluation is an
important factor of project management and every project should undertake project evaluation.