PROJECT MANAGEMENT.

Running head: PROJECT MANAGEMENT
Project management
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Part A.........................................................................................................................................2
A.1 Identification of the project.............................................................................................2
A.2 Ways in which the undertaken project creates business value........................................2
A.3 Estimation of requirement breakdown structure.............................................................3
A.4 Consideration of the four quadrants for the project landscapes......................................3
A.5 Project management life cycle and project scoping........................................................4
A.6 Appropriate PMLC for the project..................................................................................5
Part B..........................................................................................................................................5
B.1 Precedence table..............................................................................................................5
B.2 Gantt chart.......................................................................................................................7
B.3 Network analysis.............................................................................................................7
B.4 Resource chart.................................................................................................................8
B.5 Importance of project Libre for the development of schedule........................................8
Conclusion..................................................................................................................................9
Bibliography.............................................................................................................................11

2
PROJECT MANAGEMENT
Part A
A.1 Identification of the project
The paper mainly reflects on the organization "Lightening Fast" that generally takes
several projects for attracting more number of visitors by providing new as well as interesting
services. The services mainly include new rides and different types of new experiences at
affordable prices. The main project that is selected by the organization is the building of big
tents with indoor play areas with mini restaurants as well as entertainers is generally offered.
The tents will be present near the most popular regions. The objectives of the project are
generally elaborated below:
 To make the waiting lines comfortable as well as less boring
 To increase the customers of the organization by providing new services
 To increase the revenue of the lightning theme park that generally influences the
customers to spend more money on the snack as well as drinks.
A.2 Ways in which the undertaken project creates business value
It is found that the main aim of the project is to develop a big tent within the indoor
play areas for the children with proper restaurants, entertainers as well as shops that sells
snacks as well as other types of healthy food. The tents are generally present within the areas
which are very much popular and are mainly high demand for the children's rides. With the
help of this project, the people who are standing in the queue does not get bored and can be
able to enjoy the services including jugglers, mini restaurant and can have snacks in order to
have fun. This facility of the theme park generally attracts more people as no one wants to
get bored. As a result, the yearly revenue of the organization generally increases, which

3
PROJECT MANAGEMENT
further bring profit. In addition to this, excellent service by the developed big tents can also
be helpful in increasing the brand value of the organization.
A.3 Estimation of requirement breakdown structure
The requirement breakdown structure is defined as one of the hierarchical
decomposition of the various requirements that generally be related to the solution for
delivering the expected business value (Kerzner and Kerzner 2017). The requirement
breakdown structures for this project are generally provided below. The diagram helps in
reflecting that the business requirements of the organization is generally categorized into
stakeholder requirements as well as transition requirements.
Figure 1: Requirement breakdown structure
(Source: Created by Author)
A.4 Consideration of the four quadrants for the project landscapes
The four different quadrants for the project landscape is generally reflected with the
help of the image that is generally provided below: It is found that if the project solution is
Business
requirement
Stakeholder
requirement
Functional
requirements
User
Roller coastal ride
Transition
requirement
Non functional
requirements
Quality
Constraints
Assumption

MPx
Extreme xPM
Extreme
TPM
Linear
Incremental
APM
Iterative
Adaptive
Clear
Clear Not clear
Not clear
Solution
G
o
a
l
4
PROJECT MANAGEMENT
clear and the project goal is unclear then the project remains within the 1st quadrant whereas
when both the solution as well as project goal is not clear when the project will remain in the
XPM quadrant (Kerzner 2017). Moreover, when both the solution as well as the goal of the
project is clear, the project remains in TPM quadrants. Additionally, in the solution is not
clear, and project goal is clear then the project will be present within APM methodologies.
Figure 2: Four quadrants for the project landscapes
(Source: Steenkamp and Bekker 2018, pp.77)
It is identified that in the project of developing the big tent generally focuses on
attracting more number of customers by providing proper facility of food as well as
entertainment services so that the people does not get bored while standing in a queue. This
helps in reflecting the big tent project generally have both clear goal and project solution and
therefore the project will remain in the TPM quadrant.

5
PROJECT MANAGEMENT
A.5 Project management life cycle and project scoping
The PM lifecycle generally helps in elaborating the high level procedures of the
project that further helps in describing the high level procedures for delivering the success of
the entire project. It is found that the project management life cycle generally has four phases,
which mainly includes the initiation phase, planning phase, execution phase, as well as
closure phase (Steenkamp and Bekker 2018). It is found that there are numerous types of PM
life cycle and they are waterfall model, interactive and incremental model as well as an
adaptive life cycle. It is found that PM lifecycle is generally selected as per the needs as well
as requirements of the project so that with the assistance of appropriate project management
life cycle, the entire project can be executed successfully.
On the other hand, it is found that project scope is considered as one of the significant
parts of the project planning that assists in properly defining as well as recording the list of
project deliverables as well as various types of features of the project. It is essential to follow
the project scope in order to accomplish the objectives (Hornstein 2015). Proper project
scoping helps in ensuring that the scope is accurately designed and it further enables the
managers for allocating both the labour as well as costs that are necessary for finishing the
project successfully.
A.6 Appropriate PMLC for the project
It is found that for this project, Iterative and Incremental Life Cycle will be more
suitable. It is found that in the iterative as well as incremental life cycle, the project team
generally starts working on a single set of project needs after they are generally signed off.
The incremental approach generally utilizes a number of steps, and therefore, the
development of the project generally goes in a linear fashion starting from the initiation to the
closure phase. This approach is generally used within different steps including design,
implementation, testing as well as maintenance. Moreover, these steps can generally be

6
PROJECT MANAGEMENT
broken down into further sub-categories however, it is found that the incremental model
generally uses the same pattern. This project management lifecycle is considered to be very
much important as this model is very much flexible and generally requires less money for
changing the scope as well as project requirements (Wong et al. 2017). It is very much easier
to test as well as debug during the iteration procedure properly. In addition to this, it is found
that with the help of this type of project management life cycle, it will be quite easier to
manage the project risks that are identified within the project phases.
Part B
B.1 Precedence table
The table that is given below reflects on the predecessor of the project.
WBS Task Name Duration Start Finish Predecessors
0 Developing a coastal roller
ride 93 days Fri 17-05-
19
Tue 24-09-
19
1 Initiation phase 16 days Fri 17-05-
19
Fri 07-06-
19
1.1 Development of business
case 4 days Fri 17-05-
19
Wed 22-05-
19
1.2 Undertaking feasibility
study 3 days Thu 23-05-
19
Mon 27-05-
19 2
1.3 Establishing project
charter 4 days Tue 28-05-
19
Fri 31-05-
19 3
1.4 Appointing team
members 5 days Mon 03-06-
19
Fri 07-06-
19 4
1.5 Milestone 1: Completion
of initiation phase 0 days Fri 07-06-
19
Fri 07-06-
19 5
2 Planning phase 13 days Mon 10-
06-19
Wed 26-
06-19
2.1 Development of resource
plan 5 days Mon 10-06-
19
Fri 14-06-
19 5
2.2 Development of financial
plan 5 days Mon 17-06-
19
Fri 21-06-
19 8
2.3 Development of risk
management plan 3 days Mon 24-06-
19
Wed 26-06-
19 9
2.4 Milestone 2: Completion 0 days Wed 26-06- Wed 26-06- 10

7
PROJECT MANAGEMENT
of planning phase 19 19
3 Execution phase 55 days Thu 27-06-
19
Wed 11-
09-19
3.1 Determining the
materials 10 days Thu 27-06-
19
Wed 10-07-
19 10
3.2 Implementation of car of
the roller coaster 12 days Thu 11-07-
19
Fri 26-07-
19 13
3.3 A standard full circuit
coaster 13 days Mon 29-07-
19
Wed 14-08-
19 14
3.4 Launching mechanism
such as flywheel launch 10 days Thu 15-08-
19
Wed 28-08-
19 15
3.5 Properly designed ride 10 days Thu 29-08-
19
Wed 11-09-
19 16
3.6 Milestone 3: Completion
of execution phase 0 days Wed 11-09-
19
Wed 11-09-
19 17
4 Closure phase 9 days Thu 12-09-
19
Tue 24-09-
19
4.1 Post project review 5 days Thu 12-09-
19
Wed 18-09-
19 17
4.2 Stakeholder sign off 2 days Thu 19-09-
19
Fri 20-09-
19 20
4.3 Documentation 2 days Mon 23-09-
19
Tue 24-09-
19 21
4.4 Milestone 4: Completion
of closure phase 0 days Tue 24-09-
19
Tue 24-09-
19 22
B.2 Gantt chart
The Gantt chart that is provided below helps in reflecting the schedule that the project
follows for finishing the project.

8
PROJECT MANAGEMENT
Figure 1: Gantt chart
(Source: Created by Author)
B.3 Network analysis
The network diagram for the roller coastal project is created with the help of the
project Libre and are reflected below that helps in showcasing the activities in red that are
critical.
Figure 2: Network diagram
(Source: Created by Author)
B.4 Resource chart
The resource chart that is provided below helps in showcasing the time period for
which the project team members generally work within the entire project. The chart below
also showcases on the actual work, remaining work as well as the baseline work.

9
PROJECT MANAGEMENT
Business analyst
Project manager
Finacial manager
HR manager
Risk maanger
IT manager
Mechanical engineer
Workers
Designing team
0 hrs
150 hrs
300 hrs
Actual Work Remaining Work
Baseline Work
Figure 3: Resource chart
(Source: Created by Author)
B.5 Importance of project Libre for the development of schedule
Project Libre is one of the free as well as open source PM related software system
that is generally anticipated as one of the unconnected replacement for the MS project. It is
utilized for creating the project schedule for the development of the roller coastal project as
project Libre are considered to be great for the project management, and it generally helps in
developing the milestone as well as a timeline for the entire project quite accurately.
Additionally, project Libre is very much simple and it generally takes very much little time
for planning out the project with key dates for providing a nice graphics (Kostalova,
Tetrevova and Svedik 2015). The other advantages due to which project Libre is used in this
project are generally illustrated below:
Core PM Functionality: This is considered as one of the alternative software that
generally includes a number of features including Gantt charts, Work breakdown structure,
Network diagram, resource charts as well as resource histograms. It is found that the users
who use it can be able to set dependencies and can be capable of effectively generating the
cost baseline and further utilizes a number of calendars for defining either the working or the

10
PROJECT MANAGEMENT
non-working days. In addition to this, it is considered s one of the reporting functionality that
helps in displaying the dates of the project, task information as well as more.
Enterprise cloud: Project Libre is considered as a busy that generally finalizes the
cloud version. It generally has the capability of extending the open source software into a
cloud version with generally can be accessed at any time. It is found that with the help of the
single user desktop-based version, it is found that the cloud version is generally capable of
properly handling a number of projects by the users (Abramova, Pires and Bernardino 2016).
Therefore, it is found that simple project features will also be available. Proper project
collaboration from the team members at different locations is helpful. Due to all this
functionality, it is found that the project Libre is mainly utilized in order to develop the
project for roller coastal ride.
Additional advantage: It is found that the Projectlibre is considered to be very much
compatible with MS project 2003, 2007 and 2010. It generally has both the import as well as
export capabilities. It is found that in order to develop the entire project plan, it is quite
necessary to have a simple approach those helps in listing as well as indenting the list of tasks
(Wei et al. 2017). In addition to this, they can set predecessors, durations, resources just like
MS project. Moreover, they help in providing PDF based exporting as well as ribbon-based
interface.
Conclusion
It can be concluded that the development of big tent project will bring proper benefits
for the organization by attracting the customers with the help of the services. It is found that
the project mainly utilizes incremental project management lifecycle in order to manage the
entire project effectively. On the other hand, it is found that in order to develop the roller
coastal ride, project Libre is mainly used. Moreover, the main reason for using project Libre

11
PROJECT MANAGEMENT
is that it is quite simple and mainly takes very much little time for planning out the project
with key dates for in order to develop the project schedule.

12
PROJECT MANAGEMENT
Bibliography
Abramova, V., Pires, F. and Bernardino, J., 2016. Open Source and Proprietary Project
Management Tools for SMEs. Journal of Information Systems Engineering & Management,
1(3), pp.177-186.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach.
Routledge.
Hornstein, H.A., 2015. The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2),
pp.291-298.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Kerzner, H., 2017. Project management metrics, KPIs, and dashboards: a guide to
measuring and monitoring project performance. John Wiley & Sons.
Kostalova, J., Tetrevova, L. and Svedik, J., 2015. Support of project management methods by
project management information system. Procedia-Social and Behavioral Sciences, 210,
pp.96-104.
Liu, L. and Shang, L., 2019, February. Cost Management of Power Engineering Projects
based on BIM Life Cycle. In 2018 International Symposium on Social Science and
Management Innovation (SSMI 2018). Atlantis Press.
Steenkamp, J.R. and Bekker, M.C., 2018. Validating a project life-cycle review framework
for mining projects at Exxaro. South African Journal of Industrial Engineering, 29(1), pp.74-
85.

13
PROJECT MANAGEMENT
Wei, K., Crowston, K., Eseryel, U. Y., & Heckman, R. (2017). Roles and politeness behavior
in community-based free/libre open source software development. Information &
Management, 54(5), 573-582.
Wong, W.Y., Yu, S.W. and Too, C.W., 2019, May. A Systematic Approach to Software
Quality Assurance: The Relationship of Project Activities within Project Life Cycle and
System Development Life Cycle. In 2018 IEEE Conference on Systems, Process and Control
(ICSPC) (pp. 123-128). IEEE.