BM522 Project Management: Analysis of Music Festival Case Study Report

This report examines the project management aspects of organizing a music festival for the Bucks Students' Union. It begins by comparing three project management methodologies: Waterfall, Agile, and Extreme Programming, highlighting their advantages and disadvantages. The report then constructs a network diagram to illustrate the project's activities and critical path, followed by a stakeholder analysis identifying key individuals and their influence. A work breakdown structure is also included to organize project tasks. Finally, the report assesses potential risks, such as financial loss, equipment loss, and overstressed workers, and proposes mitigation strategies. The case study provides a practical application of project management principles, offering insights into planning, execution, and risk management within a real-world context.

Running head: BM522 PROJECT MANAGEMENT
Bucks Students’ Union Music Festival case study
Name of Student-
Name of University-
Author’s Note-

1BM522 PROJECT MANAGEMENT
Table of Contents
Introduction......................................................................................................................................1
Task 1: Comparison of three project management methodologies.................................................1
Task 2: Network Diagram...............................................................................................................3
Task 3: Stakeholder analysis and work breakdown structure..........................................................7
Work Breakdown Structure.............................................................................................................9
Task 4: Risk Analysis....................................................................................................................11
Bibliography..................................................................................................................................15

2BM522 PROJECT MANAGEMENT
Introduction
The report deals with the case study of Bucks Student’s Union and the project that is
included in this case study is organizing a music festival that is to be organized at the Town Hall.
This music festival is to be organized to celebrate the achievements of Alumni and as a
Subbatical Officer, the project has to be managed and assisted to host the music festival. For
managing a project, a proper methodology of project management is to be selected (Ibrahim, Ali
and Sirshar 2019). This report states comparison of 3 project management methodologies that
can be used in managing the project successfully. The hosting of the music festival includes
some set of activities and those are to be managed in the project. For managing the activities and
finding critical path of the project, project network diagram is to be designed and this report
shows the project network diagram for the project plan of music festival. This report also
describes the stakeholder analysis and the risk analysis for carrying out the project.
Task 1: Comparison of three project management methodologies
Waterfall model: This methodology is the oldest methodology of managing the
project. This methodology is a sequential methodology and it is heavily focused on the
requirement of the project (Pasian 2016). If the idea of the project and the requirement of the
project is clear, then only this methodology can be used.
Advantages:
1. This methodology is very easy to use.
2. This methodology provides proper structure of project development (Basari 2017).
3. With agile methodology, proper documentation can be achieved.

3BM522 PROJECT MANAGEMENT
4. This methodology is more efficient than any other methodology in project
management.
Disadvantages:
1. There is a high risk of developing the project with waterfall model. This model
increases the risk of failure.
2. This method mainly depends on the understanding of the project requirement, if the
project requirement is understood well, this methodology will work the best.
Agile model: The agile project management includes four values in the agile manifesto
of software development. There are many frameworks that are followed by Agile project
development. The frameworks are scrum and Kanban (Vhutshilo et al. 2018). All the methods in
agile method of project development follows objective that are mainly defined by the customers
and also provides changes in the final delivery of the project. The project team in Agile method
works in iteration and helps to evaluate the results after completion of each cycle.
Advantages:
1. The agile scrum helps to focus on the project with 30 days sprints. Sprints are time
division that are included in agile project. These sprints help to complete the project work in
repetitive cycles.
2. The agile method of project management is fast paced and is team focused. This would
allow the project team members to complete it within the time and provide their valuable
feedback in the project (Svensson and Tehler 2016).
Disadvantages:

4BM522 PROJECT MANAGEMENT
1. There is a risk of scoop creep and scope creep lead to high risk of the project. Project
completing on time might not be done with the frequent change in scope of the project.
2. This method lacks flexibility in the project and the project might include a high risk.
Extreme Programming model: This method of project management mainly focuses
on the team work and with customer satisfaction. There are five tenets that are included in EP
methodology (Irfan and Hassan 2018). Those are communication, simplicity, feedback, courage
as well as respect. This method works on sprints and the sprints are generally short compared to
agile method. This method mandates engineer practices that are test driven and automated testing
is included in the extreme programming model.
Advantages:
1. This method helps to save the cost of software development and also save the time
required for project realization (Pasian 2016).
2. This method is much simple compared to other methods and methods are visible and
accountable.
Disadvantages:
1. This method mainly depends on code instead of depending on design.
2. This method does not includes quality assurance.
Task 2: Network Diagram
The format for the network diagram is as follows

5BM522 PROJECT MANAGEMENT
Figure 1: Pert chart
calculation
(Source: Created using Visio)

6BM522 PROJECT MANAGEMENT
Figure 2: Network Diagram
(Source: Created using Visio)

7BM522 PROJECT MANAGEMENT
Explanation:
The above mentioned diagram states network diagram for the activities related to hosting
music festival. Critical path for the project is highlighted in red in the diagram above. The EST,
LST and the slack time for each of the activities is mentioned as the format that is mentioned in
the figure 1. In figure 2. The network diagram with critical path network is shown. The total
number of days to complete the project is 123 days. The critical path shows the total possible
time that is needed to complete the project successfully. Critical path states the longest time that
the project will need to complete covering all the important tasks. The above diagram shows the
critical path for the project. There are two critical path for the project, 1 - 2 – 4 – 6 – 7 – 20 – 21-
22 and 1 - 2 – 5 – 6 – 7 – 20 – 21- 22. Both the critical path will take same time to complete the
project.

8BM522 PROJECT MANAGEMENT
Task 3: Stakeholder analysis and work breakdown structure
Stakeholder Type of
stakeholder
Interest Power Communication strategy
Subbatical
officer of student
Union
Internal
stakeholder
High High Communicates only through
email or two way
communication.
Project manager Internal
stakeholder
High High Communicates through
written communication and
with face to face
communication.
Financial
manager
Internal
stakeholder
Medium Medium Communicates through
written communication and
with face to face
communication.
Project
administrator
Internal
stakeholder
Medium High Face to face communication
Advertising
manager
external
stakeholder
Medium Low Social media
communication, and email
communication.
Orchestra
manager and
group
group
stakeholder
Medium High Face to face communication
and written communication.
Contractor of external Low Low Telephone communication

9BM522 PROJECT MANAGEMENT
building stakeholder and written
communications. Can also
have email communication.
Photographer Group
stakeholder
Low Low Email communication
Costume
contractor
Group
stakeholders
Medium Low Face to face communication
Casting group Group
stakeholders
Low Medium Face to face communication
and communication over
telephone.
Viewers External
stakeholders
Low Low Social media
communication.

10BM522 PROJECT MANAGEMENT
Figure 3: Stakeholder matrix
(Source: Created using Visio)
Work Breakdown Structure

11BM522 PROJECT MANAGEMENT
Figure 4: Work Breakdown Structure
(Source: Created using Visio)