Training and Apprenticeship program for high school Students - Project Management Case Study

This Project Management Case Study is about the Training and Apprenticeship program for high school Students. The paper showcases the organization Globlex, which aims to help farmers increase productivity from farmlands. The organization will provide training to higher school students as per farming expertise to help farmers. The paper elaborates on the measurable organizational value, scope of the project, work breakdown structure, risk analysis and plan, quality management plan, and closure and evaluation. The subject is Project Management, and the document type is a Case Study.

Running head: PROJECT MANAGEMENT
Case Study- Training and Apprenticeship program for high school Students
Name of the Students
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Introduction................................................................................................................................2
Project description......................................................................................................................2
Part 1: Measurable organizational Value...................................................................................2
1.1 Desired area of impact.....................................................................................................2
1.2 Identification of value......................................................................................................3
1.3 Metrics..............................................................................................................................3
1.4 Timeframe........................................................................................................................4
1.5 MOV statement................................................................................................................4
Part 2: Scope of the project........................................................................................................4
2.1 Project scope....................................................................................................................4
2.2 Resource plan...................................................................................................................5
2.3 Scope management plan...................................................................................................6
Part 3: Work breakdown structure.............................................................................................6
3.1 Work breakdown structure...............................................................................................6
3.2 Duration, allocated resource and project budget..............................................................7
3.2 Assumptions and constraints made for developing the budget......................................13
3.3 Confidence about the project estimation........................................................................13
Part 4: Risk analysis and plan..................................................................................................14
4.1 Assumptions...................................................................................................................14
4.2 Risk identification..........................................................................................................14
4.3 Risk analysis...................................................................................................................16
Part 5: Quality management plan.............................................................................................17
5.1 Project quality statement................................................................................................17
5.2 Verification activities.....................................................................................................17
5.3 Validation activities.......................................................................................................17
Part 6: Closure and evaluation.................................................................................................18

2
PROJECT MANAGEMENT
6.1 Annotated Bibliography.................................................................................................18
6.2 Development of closure checklist..................................................................................19
6.3 Development of project evaluation................................................................................20
Bibliography.............................................................................................................................21

3
PROJECT MANAGEMENT
Introduction
The paper mainly showcases on the organization “Globlex” which generally has 30
years of experience in agricultural field. The organization mainly aims to help the farmers so
that the productivity from the farmlands can be increased. For this, the organization organizes
a program with the help of which the organization will provide training to the students of
higher class as per the farming expertise so that they can be able to help the farmers. For
managing the operations of the program effectively, the organization mainly aims to develop
an information system.
The main objectives of the project are generally listed below:
 To develop an information system for managing the operations of TAHS program
 To provide the facility of training to the higher school students
 To provide trained expertise in the farmlands for helping the farmers.
Project description
The organization Globlex generally helps the farmers in increasing the production of
the farmlands. Presently the organization is dealing with two different products including
farm equipment as well as precision farming. The team of Globlex farm has 30 years of
experience within the agricultural business and it generally considered as the largest
organization that will serve the farmers in the coming future. It is found that the organization
is using number of new technologies for helping the farmers in the future.
Part 1: Measurable organizational Value
1.1 Desired area of impact
The desired area of impact of the measurable organizational goal of the project are
generally elaborated in the table below:

4
PROJECT MANAGEMENT
Factor Rank
Operational 1st
Customer 2nd
Financial 3rd
Social 4th
Strategy 5th
1.2 Identification of value
The determined value of the project is generally elaborated below:
Better: The services that are received by the organization are very much better as
well as efficient due to the management of operations with the help of a new system
Faster: With the development of the new system, the services that are received by the
organization will be quite faster.
1.3 Metrics
The metrics in context to MOV are generally reflected in the table below:
Factor Metrics
Operational The new system helps in improving the
operations of the organization by 12%.
Customer The rise in the number of customers will be
around 14%.
Financial The yearly revenue of Globlex will be
increased by 13%.
Social Due to the utilization of social media, the
number of customers rises by 3%
Strategy Due to the use of proper strategies, the

5
PROJECT MANAGEMENT
program will be managed effectively.
1.4 Timeframe
The timeframe that is needed is generally reflected in the table below:
Factor Timeframe
Operational 3 months
Customer 3 months
Financial 2 months
Social 1month
Strategy 1 month
1.5 MOV statement
The measurable organizational value is considered as one of the project goals that is
mainly utilized for elaborating the value that the project helps in bringing to the customers of
the organization. In order to provide proper value to the organization, it is quite necessary to
align it with the support of the organization’s mission, strategy as well as vision of the
organization.
Part 2: Scope of the project
2.1 Project scope
The scope of the project mainly includes the following:
 Development of computer-based system for the management of the TAHS
program
 Inviting the students to join the program
 Providing the facility of training to the students
 Adding details about the system within the information system
 Providing trained expertise to the farmers

6
PROJECT MANAGEMENT
 Completing the development of the information system within 82days
2.2 Resource plan
Human resources: The stakeholders who are mainly involved with the computer-
based system development are generally listed in the figure below:
Figure 1: Human resources
(Source: Created by Author)
Technology: The software and hardware that are generally required are mainly listed
below:
 Software: Designing tool as well as development tool
 Hardware: CPU, Desktop, RAM
Facilities: Travelling allowances are given to the team members who work for extra
hours.
Others: Training facilities and proper arrangement for the workshops should be done for
completing the work of the project.

7
PROJECT MANAGEMENT
2.3 Scope management plan
The steps which are generally used for managing the project scope are generally
elaborated below:
 The project requirements must be properly elaborated so that the project team can be
capable of gaining proper information about the project goals
 Proper understanding regarding the objectives is necessary for avoiding the chances
of scope creep within the entire project
 Properly analyzing the problem of scope creep in the initial stages of the project is
quite important for successfully managing the scope of the project
Part 3: Work breakdown structure
3.1 Work breakdown structure
Development of
computer based
system.mpp
Project initiation phase
Analysis of project
idea
Collecting data
about the project
Identifying project
idea
Identifying project
stakeholders
Developing project
plan
Developing
business plan for
the project
Developing charter
Milestone
1:Completion of
initiation phase
Project planning phase
Estimation of project
resources
Project duration
estimation
Drafting resource
plan for the project
Team members
recruitment
System analysis
Schedulling
Project plan
development
Milestone
2:Completion of
planning phase
Project designing phase
Design selection for
the projecr
Prototype
development
Outline of the
design
Design review of the
system
Milestone
3:Completion of the
design phase of the
project
Project development
phase
Development of
project plan
Student invitation
Training fcaility
Adding ideas anbout
the students
Database
development
Stuudent's
placement
Appentice tracking
Milestone 4:
Completion of
development phase
Closing phase
Providing training
manuals
Providing training
facility to the
employees
Reviewing project
Milestone
5:Completion of
closure phase
Figure 2: Work breakdown structure
(Source: Created by Author)

8
PROJECT MANAGEMENT
3.2 Duration, allocated resource and project budget
The table that is provided below generally reflects on the duration, allocated resources
as well as on the needed budget for the development of computer-based system.
W
BS
Task Name Duration Start Finish
Predece
ssors
Resource
Names
Cost
0
Development
of computer-
based system
82 days
Mon 28-
01-19
Tue 21-05-
19
$67,736.00
1
Project
initiation
phase
18 days
Mon 28-
01-19
Wed 20-02-
19
$4,824.00
1.1
Analysis
of project idea
3 days
Mon 28-
01-19
Wed 30-01-
19
Project Manager $600.00
1.2
Collecting
data about the
project
2 days
Thu 31-01-
19
Fri 01-02-19 2 Project Planner $240.00
1.3 Identifying
project idea
2 days
Mon 04-
02-19
Tue 05-02-
19
3
Business
Analyst, Project
Manager
$720.00
1.4
Identifying
project
stakeholders
2 days
Wed 06-
02-19
Thu 07-02-
19
4
Project Manager
Hr. Manager
$688.00
1.5 4 days Fri 08-02- Wed 13-02- 5 IT Manager, $864.00

9
PROJECT MANAGEMENT
Developing
project plan
19 19 Project Planner
1.6
Developing
business plan
for the project
2 days
Thu 14-02-
19
Fri 15-02-19 6
IT Manager,
Business
Analyst, Project
Planner
$752.00
1.7 Developing
charter
3 days
Mon 18-
02-19
Wed 20-02-
19
7
Project
Manager,
Project Planner
$960.00
1.8
Milestone
1:
Completion
of initiation
phase
0 days
Wed 20-
02-19
Wed 20-02-
19
8 $0.00
2
Project
planning
phase
21 days
Thu 21-
02-19
Thu 21-03-
19
$5,112.00
2.1
Estimation of
project
resources
4 days
Thu 21-02-
19
Tue 26-02-
19
9
Financial
Officer
Manager,
Project Sponsor
$1,536.00
2.2
Project
duration
estimation
3 days
Wed 27-
02-19
Fri 01-03-19 11 Project Manager $600.00
2.3 Drafting 2 days Mon 04- Tue 05-03- 12 HR Manager $288.00

10
PROJECT MANAGEMENT
resource plan
for the project
03-19 19
2.4
Team
members
recruitment
4 days
Wed 06-
03-19
Mon 11-03-
19
13 HR Manager $576.00
2.5
System
analysis
2 days
Tue 12-03-
19
Wed 13-03-
19
14
Designer, IT
Consultant, IT
Manager
$752.00
2.6
Scheduling
2 days
Thu 14-03-
19
Fri 15-03-19 15
IT Consultant,
Project Planner
$560.00
2.7
Project
plan
development
4 days
Mon 18-
03-19
Thu 21-03-
19
16 Project Manager $800.00
2.8
Milestone
2:
Completion
of planning
phase
0 days
Thu 21-03-
19
Thu 21-03-
19
17
Project
Manager,
Project Planner
$0.00
3
Project
designing
phase
13 days
Fri 22-03-
19
Tue 09-04-
19
$39,808.00
3.1 Design
selection for
the project
4 days Fri 22-03-
19
Wed 27-03-
19
18 Business
Analyst,
Designer,
$1,504.00

11
PROJECT MANAGEMENT
Developer
3.2
Prototype
development
3 days
Thu 28-03-
19
Mon 01-04-
19
20
Business
Analyst,
Designer
$840.00
3.3
Outline of
the design
4 days
Tue 02-04-
19
Fri 05-04-19 21
Designer, IT
Consultant, IT
Manager,
Hardware [1]
$16,504.00
3.4
Design
review of the
system
2 days
Mon 08-
04-19
Tue 09-04-
19
22
Designer, IT
Consultant,
Project
Manager,
Software [1]
$20,960.00
3.5
Milestone
3:
Completion
of the design
phase of the
project
0 days
Tue 09-04-
19
Tue 09-04-
19
23 Designer $0.00
4
Project
development
phase
23 days
Wed 10-
04-19
Fri 10-05-
19
$16,192.00
4.1
Development
of project
6 days Wed 10-
04-19
Wed 17-04-
19
24 Developer,
System Analyst
$1,296.00

12
PROJECT MANAGEMENT
plan
4.2
Student
invitation
4 days
Thu 18-04-
19
Tue 23-04-
19
26
Business
Analyst
$640.00
4.3
Training
facility
3 days
Wed 24-
04-19
Fri 26-04-19 27
Trainer, Other
cost [1]
$10,312.00
4.4
Adding
ideas about
the students
4 days
Mon 29-
04-19
Thu 02-05-
19
28
Project
Manager,
Project Planner,
Risk Manager
$1,824.00
4.5
Database
development
3 days
Fri 03-05-
19
Tue 07-05-
19
29
Designer,
Developer,
System Analyst,
Tester
$1,248.00
4.6
Student’s
placement
3 days
Wed 08-
05-19
Fri 10-05-19 30 Project Planner $360.00
4.7 Apprentice
tracking
4 days
Fri 03-05-
19
Wed 08-05-
19
29
Operational
Manager
$512.00
4.8
Milestone
4:
Completion
of
development
phase
0 days
Fri 10-05-
19
Fri 10-05-19 31 Project Manager $0.00

13
PROJECT MANAGEMENT
5
Closing
phase
7 days
Mon 13-
05-19
Tue 21-05-
19
$1,800.00
5.1
Providing
training
manuals
3 days
Mon 13-
05-19
Wed 15-05-
19
31
Business
Analyst, IT
Consultant,
Trainer
$1,272.00
5.2
Providing
training
facility to the
employees
2 days
Thu 16-05-
19
Fri 17-05-19 35 Trainer $208.00
5.3 Reviewing
project
2 days
Fri 17-05-
19
Tue 21-05-
19
36
Project
Manager,
Project Planner,
Project Sponsor
$320.00
5.4
Milestone
5:
Completion
of closure
phase
0 days
Tue 21-05-
19
Tue 21-05-
19
37 Project Manager $0.00
3.2 Assumptions and constraints made for developing the budget
Assumptions
The assumptions that are made within the project are listed below:
 The project will progress as per the schedule
 The entire project will get completed within the sponsored amount of money

14
PROJECT MANAGEMENT
 The project will generally follow the project scope
Constraints
The constraints of the project are reflected below:
Budget: It is quite important to complete the project within the assumed budget otherwise
the project will face number of financial issues and challenges.
Time: It is very much necessary to progress the project as per the project schedule
otherwise the time for project completion will get extended which will further increase the
project budget.
Scope: The scope of the project must be followed otherwise it will be difficult for the
project managers to complete the project in the expected budget and time.
3.3 Confidence about the project estimation
It is assumed that in order to develop the information system for the organization
“Globlex”, the amount of money that is needed will be around $67,736. The budget that is
assumed is enough for the successful completion of the project within the expected time. The
budget that is needed for executing each of the project activities is reflected in the schedule of
the project. If the project manager follows the schedule of the project and executes each of
the project activity within the assumed time and budget then the entire project will be
completed within the budget that is assumed.
Part 4: Risk analysis and plan
4.1 Assumptions
The various types of assumptions which are made during the analysis of project risk
are generally reflected below:

15
PROJECT MANAGEMENT
Time: It is assumed that the design that is made effectively and as per the design the
entire system can be developed successfully.
Budget: It is assumed that the execution of the project must be completed within the
budget that is assumed.
4.2 Risk identification
The risks that are identified during the execution of the information system for
managing the TAHS program effectively are generally reflected in the table below:
Risks Description Impact Probability Type
Improper
scheduling
Improper
scheduling occurs
due to addition of
new features within
the system
High High Positive
Budget
overshoot
As the budget of
the project is not
managed properly
then the problem of
budget overshoot
occurs.
High High Negative
Improper design
of the project
Due to improper
design of the
project number of
issues related with
the development of
High High Negative

16
PROJECT MANAGEMENT
information system
occurs.
Inexperienced
team members
If the team
members are not
experienced then it
will be quite
difficult for them to
complete the
project on time.
Medium Medium Negative
Lack of proper
management
If proper
management is not
done then the
project will not be
completed on time.
Medium Medium Negative
4.3 Risk analysis
The risks that are identified can be mitigated with the help of proper mitigation plan
in the table below:
Risks Assigned to Mitigation
Improper scheduling Project manager Tracking would be helpful
in reducing the problem
that occurs due to improper
scheduling.
Budget overshoot Financial manager Proper management of
project budget is necessary
for reducing the problems

17
PROJECT MANAGEMENT
that are associated with
financial manager
Improper design of the
project
Designer Proper design of the
system is helpful in
developing the project
successfully.
Inexperienced team
members
Human resource manager Hiring experienced team
members is helpful in
completing the project
work successfully.
Lack of proper
management
Human resource manager Use of proper project
management strategies are
helpful in managing the
project effectively.
Part 5: Quality management plan
5.1 Project quality statement
Use of proper quality standards are needed for managing the quality of the project
quite successfully. In addition to this, the steps which are generally needed for successfully
managing the project quality are generally listed below:
 Checking the project quality on regular basis is quite necessary
 Appropriate use of strategies such that proper quality of the project is followed
 Proper priority must be provided on the steps for the management of project quality
5.2 Verification activities
Verification activity When?

18
PROJECT MANAGEMENT
System design Deigning of the system is reviewed before
the development of the design phase.
Testing project This is generally conducted for making sure
such that system will be developed quite
effectively.
5.3 Validation activities
Validation activity When?
Project review Review of project is done after the closure
of the project.
Project quality Quality of project is checked after
development phase.
Part 6: Closure and evaluation
6.1 Annotated Bibliography
Article 1: Andersen, E. S. (2016). Do project managers have different perspectives on
project management? International Journal of Project Management, 34(1), 58-65.
The paper mainly reflects on different perspectives that project manager generally
has in order to manage the project. The paper discusses that different project managers
generally have different perspectives. The task perspectives of the managers generally reflect
that the work of the project must be delivered successfully on time and budget with proper
quality. The organizational perspectives help in implying that it is the role of the project
manager to focus on the support value creation. The conducted surveys generally help in
revealing different types of perspectives that the project manager gas. The implications are

19
PROJECT MANAGEMENT
generally considered to be significant. Moreover, it is the responsibility of the project to
properly decide the project outset which is mainly ruled by the different project management
perspectives.
Article 2: Papke-Shields, K. E., & Boyer-Wright, K. M. (2017). Strategic planning
characteristics applied to project management. International Journal of Project
Management, 35(2), 169-179.
This article helps in examining the strategic planning-based characteristics prior from
strategic research to management. It is found that by drawing proper research in strategic
planning, a strategic information system as well as in strategic manufacturing, it is found that
the research helps in combining the rational approach with the adaptive characteristics for
creating proper comprehensive model. After then the resulting rational approach is generally
properly assessed for evaluating the relevance of project management in order to identify
whether it is generally associated with the increased success of the project. Moreover,
rational adaptive approach is generally mapped for establishing the project management-
based tools and techniques. Proper findings help in suggesting that project management is
generally captured with the help of different degrees of strategic planning-based
characteristics which can generally be incorporated within the generalized project
management-based framework which generally helps in yielding useful insights that are
generally related with the relationship of project management behaviours for evaluating the
success of the project.
Article 3: Drouin, N., Sankaran, S., & Muller, R. (2016). The nature of organizational
project management and its role as an organizational capability. Manageable
Cooperation?

20
PROJECT MANAGEMENT
The article generally reflects on the organizational project management which is
mainly defined as one of the integrations for all the project related management activities
throughout the organizational network or hierarchy. This paper helps in reflecting the OPM
that helps in properly integrating the capability by combining as well as embedding the
activities of project management by effectively within the entire organizations. It is found
that proper discussions are generally done on the nature of organizational project
management as the entire role of the capability are generally grounded within the
organizational theory. In addition to this, the paper helps in highlighting the role that OPM
plays for fostering the effectiveness of the organization with the help of vertical as well as
horizontal capability in context to diverse project related activities.
6.2 Development of closure checklist
Activities Status
After the project is completed then the
resources of the project are released?
Yes
Does documentation for the project is
developed?
Yes
Does the project is generally closed? Yes
6.3 Development of project evaluation
Evaluation activities Option
Does the goals of the project are met? Yes  No 
Does proper method of tracking is used
within the project?
Yes  No 
Does the project creates positive impact? Yes  No 

21
PROJECT MANAGEMENT

22
PROJECT MANAGEMENT
Bibliography
De Carvalho, M. M., Patah, L. A., & de Souza Bido, D. (2015). Project management and its
effects on project success: Cross-country and cross-industry
comparisons. International Journal of Project Management, 33(7), 1509-1522.
Hornstein, H. A. (2015). The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2),
291-298.
Joslin, R., & Müller, R. (2015). Relationships between a project management methodology
and project success in different project governance contexts. International Journal of
Project Management, 33(6), 1377-1392.
Kaiser, M. G., El Arbi, F., & Ahlemann, F. (2015). Successful project portfolio management
beyond project selection techniques: Understanding the role of structural
alignment. International Journal of Project Management, 33(1), 126-139
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. 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.
Papke-Shields, K. E., & Boyer-Wright, K. M. (2017). Strategic planning characteristics
applied to project management. International Journal of Project Management, 35(2),
169-179.
Rai, A. K., Agrawal, S., & Khaliq, M. (2017). Identification of Agile Software Risk
Indicators and Evaluation of Agile Software Development Project Risk Occurrence

23
PROJECT MANAGEMENT
Probability. In Proceedings of 7th International Conference on Engineering
Technology, Science and Management Innovation (ICETSMI-2017) (pp. 489-494).
Sánchez, M. A. (2015). Integrating sustainability issues into project management. Journal of
Cleaner Production, 96, 319-330.
Svejvig, P., & Andersen, P. (2015). Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), 278-290.
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.
Ul Musawir, A., Serra, C. E. M., Zwikael, O., & Ali, I. (2017). Project governance, benefit
management, and project success: Towards a framework for supporting organizational
strategy implementation. International Journal of Project Management, 35(8), 1658-
1672.