Project Management Report: Mobile App Development for QAHE Students

This report provides a comprehensive overview of the project management processes involved in the development of a mobile application for QAHE. It includes a detailed project initiation document (PID) outlining the project's objectives, scope, and key deliverables, as well as a work breakdown structure (WBS) that breaks down the project into manageable tasks. Furthermore, the report presents a risk register identifying potential risks associated with the project and mitigation strategies to address them. The document also discusses how to effectively manage project completion and provides a critical analysis of the methodologies used in the project, emphasizing the importance of teamwork, stakeholder communication, and proactive risk management to ensure successful project outcomes. The goal is to enhance student engagement and improve information dissemination within the university.

Project Management

TABLE OF CONTENTS
TABLE OF CONTENTS.................................................................................................................2
INTRODUCTION...........................................................................................................................3
PART 1............................................................................................................................................3
Project initiation document (PID)................................................................................................3
Work breakdown structure...........................................................................................................6
PART 2..........................................................................................................................................10
Risk register...............................................................................................................................11
How to manage project completion...........................................................................................13
Critically analysis of methodologies used in project.................................................................14
REFERENCES..............................................................................................................................18

INTRODUCTION
Project management is all about applying different process within a project which
includes planning, initiation, executing and closure. The present report is based upon QAHE,
where a project of mobile application will be implemented that helps to engage students and
facilitate better information. For that, the report will provide PID, WBS, risk register and best
project management methodology that helps to meet the defined aim of a project.
PART 1
Project initiation document (PID)
Project name: Mobile application development project
Project
information
Name: QAHR Mobile application development project
Location: Remote
Start date: 27/7/2021
End date: 10/11/2021
Budget: £200,000
Sponsor: O2
Project manager (PM): XXXX
Background With the changing era, organizations keep complying with advance
technology so that information sharing can be improved. That is why,
through implementation of mobile application, QAHE also trying to
engage their students in order to minimize the challenges.
Objectives  To increase engagement of students within extra-curricular
activities
 Develop a system that interact with employees about all the
cultural activities
 To enhance the competitive edge of University
Purpose The purpose of this project is to enhance the awareness about University

among all the students through online mode regarding cultural activities,
events.
Key deliverables  Mobile app
 Sponsor and University promotion
 Satisfaction of students
 Funding from sponsor and government
Scope The scope of this project is to maintain the flow of information among
students through development of mobile application.
Assumptions  Reduce the expenses of communication
 Ensure each student get an information
 Comply with advance technology regarding communication
Executive
members
 Sponsor
 Project manager
 Project team members
 Experts
 Mobile app developer and designer
Risk  Financial risk
 Technological risk
 Human risk
 Natural risk
 Planning risk
Success factors  Timely completion of risk
 Strong communication with stakeholder
 Effective resources with planned budget
 Project risk should be consider and develop strategy to mitigate
the same
Constraints Time: The project must complete on time and for that milestone must be
developed through gantt chart. With regard to same, the present project
will be start from 27th July 2021 and end on 11th October 2021.
Cost: It is necessary for project manager to identify the amount required

for completion of project along with expenses. So, for each stage, the
budget is set such as:
Particulars Budget (£)
Initiation 10,000
Planning 20,000
Executing 1,40,000
Controlling 10,000
Closure 20,000
Total 2,00,000
Quality: Another important key constraint that project manager need to be
focused in which quality of the project should not be compromised. In the
context of current project, the application is designed only for sharing
information that helps to keep students update.
Stakeholder
analysis
In the present project, there are 5 key stakeholders used who have interest
over the project. The stakeholder matrix is as mentioned below:
Approval Sign:
(Project Sponsor)
Stakeholder analysis
S.no. Title Roles/responsibilities Power
(high,
medium,
low)
Interest
(H/M/L)
How they block
the project
Strategy to
engage
them
1 Project Evaluate the project’s M H Stop funding for Through

sponsor actual progress
against the planned.
a project, loss of
interest
email,
meeting
once in a
week
2 Project
manager
Quality assurance,
taking feedback to
team, monitor
progress
H H Lack of
communication
between key
stakeholders,
loss of interest
towards project
Open
discussion
at weekly
3 Project
team
Execute the
instruction given by
project manager
H H Loss of
communication,
conflict
Email,
phone
calls,
meeting
once or
daily basis
4 Technical
experts
Assist to develop a
mobile application
M L Communication
discontent, lack
of knowledge
Email,
phone call
5 Students Enjoy the activity
offered by the
University.
L H Loss of interest Mobile
application
Work breakdown structure
Task
Mode Task Name Duration Start Finish Predecessors
1 Project initiation 77 days Tue 7/27/21 Wed 11/10/21
1.1 PID development 4 days Tue 7/27/21 Fri 7/30/21

1.2 PID submission 2 days Mon 8/2/21 Tue 8/3/21 2
1.3 Review by sponsor 3 days Wed 8/4/21 Fri 8/6/21 3
1.4 Approved 2 days Mon 8/9/21 Tue 8/10/21 4
2. Project planning 16 days Wed 8/11/21 Wed 9/1/21
2.1 team identification 4 days Wed 8/11/21 Mon 8/16/21 5
2.2 project scope 3 days Tue 8/17/21 Thu 8/19/21 5,7,2
2.3 Select expert for
application designing 2 days Fri 8/20/21 Mon 8/23/21 5,8
2.4 finalize the team 3 days Tue 8/24/21 Thu 8/26/21 9
2.5 planning submission 2 days Fri 8/27/21 Mon 8/30/21 5,9,10
2.6 Approval 2 days Tue 8/31/21 Wed 9/1/21 11
3 Project execution 32 days Thu 9/2/21 Fri 10/15/21
3.1 designing of mobile
app 5 days Thu 9/2/21 Wed 9/8/21 12,5
3.2 development 6 days Thu 9/9/21 Thu 9/16/21 14
3.3 logo designating 4 days Fri 9/17/21 Wed 9/22/21 14,15
3.4 finalizing the
application 3 days Thu 9/23/21 Mon 9/27/21 15,16
3.5 finishing 4 days Tue 9/28/21 Fri 10/1/21 17
3.6 testing 2 days Mon 10/4/21 Tue 10/5/21 18
3.7 risk register 6 days Wed 10/6/21 Wed 10/13/21 5,12,19
3.8 approval 2 days Thu 10/14/21 Fri 10/15/21 20
4 Project controlling 18 days Mon 10/18/21 Wed 11/10/21
4.1 product checking 3 days Mon 10/18/21 Wed 10/20/21 5,21
4.2 kickoff meeting 2 days Thu 10/21/21 Fri 10/22/21 23
4.3 risk management 5 days Mon 10/25/21 Fri 10/29/21 20,24
4.4 updates within plan
after consultation 2 days Mon 11/1/21 Tue 11/2/21 25
5 Closing 6 days Wed 11/3/21 Wed 11/10/21
5.1 update records 3 days Wed 11/3/21 Fri 11/5/21 26
5.2 staff and resources
unassigned 2 days Mon 11/8/21 Tue 11/9/21 5,28
5.3 Approvals 1 day Wed 11/10/21 Wed 11/10/21 29

Mobile application
implementation
Initiation Planning Execution Monitoring Closure
PID
development
PID submission
Review by
sponsor
Approved
Team
identification
Project scope
Select expert
Finalize the
team
Planning
submission
Designing of
mobile app
Logo
development
Finalize the
application
Finishing
Testing
Risk register
Approval
Product
checking
Kickoff meeting
Risk
management
Updates within
plan
Update records
Staff and
resources
unassigned
Approvals

PART 2
Risk register
In the context of present study, there are different risks associated with mobile
application implementation and some of them are as mentioned below:
Low =1 Medium = 2 High =3
Type of risk Description Probability Impact Score Mitigation strategy
Financial risk It means team is
not able to meet
the steps within
defined budget.
3 To mitigate the
same, project
manager of QAHE
should allocate a
fixed budget to each
core members of
team and then review
the same after
completion.
Planning risk Due to poor
implementation
and process of a
stage.
9 To improve planning
risk, it is necessary
for QAHE to consult
with stakeholder
before making any
decision because it
assists to critically
analyse the options
so that effective
decision can be
taken.
Natural risk Risk associated
with external
hazard like storms,
floods.
2 Effective analysis
should be performed
by QAHE project
manager before
implementation of
project that helps to
minimize the risk.
Technological
risk
Error in
installation of an
application
4 QAHE should take
back-up of each
important data and
hire experts that help
to minimize the
issue.
Human risk One of the team 3 Alternate human

members may fall
ill and it affect the
performance
resource should be
hiring at urgent basis
by University that
helps to improve the
risk.
Governance
risk
The risk related to
ethics, community
stewardship and
company
reputation
3 Codes of ethics
should be used by
University and the
behaviour of each
employee should be
favourable.
Schedule risk Not able to meet
the defined aim
within specific
time.
9 Benchmark should
be set by QAHE that
helps to minimize
the issue and meet
deadline.
Legal risk Not able to
comply with
regulatory
obligation
3 A list of legislation
should be mentioned
in order to comply
with the same
(Nguyen and
Nguyen, 2020).
Performance
risk
Team members
fail to produce
results consistent
with project
specification.
4 Project manager o
QAHE must review
each stage in order to
determine the
performance level.
Market risk Fluctuation in
interest rate risk,
foreign exchange
and credit risk.
1 To minimize the
same, external audit
should be performed
and then implement
the same within
business.
The risk register enables the project manager to outline all components of risk which
might affect the project in a negative manner. The key purpose of the risk register is to let the
project manager know about several risks faced by the organization. Through this, the
organization gets a clear and concise view of some risks faced by the organization. In the context
of mobile application development, there are a range of risks faced by the project manager and if
the risk register did not implement then it affects the project negatively (Hillson and Simon,
2020). Also, a risk register is a tool within risk management that is used to determine potential
risk in the project because it has direct control over the intended outcomes.