Project Management for Mobile Application Development at QAHE

The report provides a project initiation document, work breakdown structure, risk register, and methodologies used in mobile app development at QAHE. The subject is project management, the course code and name are not mentioned, and the college/university is QAHE.

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.

For example, due to no fluctuation in the budget, QAHE faces the issue of over-budget in
which project got delayed and this harms project and students. Thus, before proceeding to
execute stage, a project manager must develop a risk register to identify, log as well as track the
potential project risk. In addition to this, with the help of a risk register, the project manager can
easily spot the project is in trouble or not. Also, effective communication can be developed that
helps to meet the defined aim of a project. Therefore, it can be stated that with the help of the
risk register, a project manager can identify whether the project meets the defined aim or not
(Testorelli, Ferreira de Araujo Lima and Verbano, 2020). For example, one of the key activities
may be delayed either due to human error, financial constraints and that is why the project
manager should be aware and make a risk register that helps to meet the defined aim and
implement the strategy accordingly.
Overall, it has been identified that the risk register assists to have control over key aspects
within a project and with proper involvement of all key stakeholders within project assist to
implement mobile application within University. Thus, it can be stated that the risk register only
helps to provide better quality data for decision-making and comply with a more accurate budget
as well. The same has been performed in the present study where QAHE looking to implement a
mobile application to create awareness among students and minimize miscommunication as well.
How to manage project completion
The project closure is a process that was completed at the end of a project. In this, all the
work mentioned in the contract has been delivered by complying with the relevant PMO process.
It has been also analyzed throughout the project that with the help of teamwork, a project can
meet its defined aim (Zhao and et.al., 2021). The project manager uses the Belbin Team role
theory that assists to develop a team in which different roles have been defined according to the
project that includes monitor evaluator, specialist, plant, shaper, etc.
As per WBS, the project closure includes only three sub-task that helps to complete the
mobile application implementation. The main reason for including this stage is to overcome the
mistakes in the future, approval and final acceptance regarding deliverable and most important
clearance of payment, make sure that all relevant stakeholders have complete information.
Generally, project closure includes many steps like formal submission of all deliverables, project

completion and sign-off, review of all legal documentation, etc. However, by considering the
stages of WBS, the description of project closure is as mentioned below:
Update records or documentation:
It is all about the formal submission of all records in different documents in which
stakeholders review and update the records accordingly. Further, with the help of this stage, a
project manager can easily submit documents by considering quality resources. Along with this,
the document can be closed by reviewing legal requirements, so that it does not affect the
performance and delay (Ripalda, Guevara and Garrido, 2020). Also, project closure report has
been made during this stage that summarizes and contain all the document which will also
review by stakeholders. In this, the project manager also presents the lesson learned that is
beneficial in a future project.
Staff and other resources unassigned
It is a phase of sign-offs entire resource which includes suppliers, contractors, technical
experts, etc. In this, the project manager made the final payment so that project proceeds towards
closure. Apart from this, a resource release plan was also executed where resources should be
formally intimated regarding project closure and release duties. Therefore, in the context of the
present project, all the relevant staff and other resources have been released from their respective
duties. Along with this, the payment procedure of the staff should be made according to their
contracts in which all the relevant legislation should comply.
Approval
It is the last stage where project managers get final approval from their stakeholders by
signing. It is so because announcing completion only is not only enough for the project closure
stage (Azadi and et.al., 2020). Concerning the same, a document has been designed that assists to
determine whether the team can meet the set target. Therefore, the documents should be formally
signed off so that the project manager can complete the defined aim.
Overall, it has been reflected that through project closure, different theories have been
used to lead a project towards a better outcome. By focusing upon these activities, QAHE
University also ensures to proceed towards formally closing activities so that there will be no

confusion. Thus, by following the entire activity of project closure, the project team gets a
chance to evaluate their work so that the same mistakes will not be done in the future. That is
why all the five stages of a project need to be followed to meet the defined aim of a project.
Critically analysis of methodologies used in project
Project methodologies is a collection of methods, practices, and techniques which are
used in each project’s life. There are different types of project methodologies used for different
scenarios which include Waterfall, Agile, Scrum, Prince2, etc. Three of these areas mentioned
below:
Waterfall:
It is one of the most common types of project methodology where a project is completed
in stages and moves ahead step by step. This methodology is best suited for long and detailed
projects that require a single timeline (
Waterfall model of project management, 2020). Under
this, changes are often discouraged because the project manager has to start with scratch.
Figure 1: Stages of Waterfall methodology
As per the above diagram, it has been identified that project management performs each
task within a key stage that helps to complete the defined task. Such that under requirement,
manager analyses as well as gather all the key requirement about the project and next proceed to
next stage of design where manager design the project’s workflow. In the third stage, the system
will be implemented in which teamwork pays off. Further, in the fourth stage, testing performs
that ensure it works as expected and meets the requirement and the last is maintenance where the
team performs to meet the results.

Advantages Disadvantages
 Initially, the project starts with a
comprehensive document.
 Assist to enhance the knowledge
 Easy to understand and implement
(Avlijaš, 2020).
 It is an expensive method and the
project manager cannot go back of
previous stage
 Can be used when the client provides
an accurate idea
 Change in scope might impact upon
the project
Agile:
It is comprising of different iteration and incremental steps that lead towards the
completion of the project. This is regularly used in software development projects to complete
the project. The methodology work on an iterative approach so that it benefits the project rather
than the only completion. It allows team members to work quickly and collaboratively within a
specific timeframe and budget (Chandrachooodan and Radhika, 2020). This is also focused upon
quality products and also working in small batches that help to work in collaboration. There are
five attributes used by the project manager while using this methodology which include
transparency, customer focus, adaptability, sense of ownership, continuous improvement.
Pros Cons
 The methodology is flexible and uses
effective communication medium to
share ideas
 Assist to satisfy the customer demand
 Use superior quality of product to
deliver the best result.
 Require high customer involvement to
provide end-user.
 Poor resource planning affects the
entire project.
 The results are difficult to measure.
Prince2:
It is a flexible method that is used to manage successful projects by complying with 7
principles. The methodology focused upon four integrated elements of principles, themes,
process, and project environment. It is one of the most famous methodologies which is mostly
used by the project manager to implement the project effectively. Thus, it focused on the
business justification that helps to define the structure of an organization for a project team.
Along with this, it has proper control over the project resources and also manages project risk
more effectively.

Benefits Drawbacks
 Prince2 methodology is used for better
communication and have a strong
accountability within project
(Hamzane and et.al., 2020).
 It is entirely based upon product and
also divides project in different stages.
 Also, involve all the stakeholder in
order to make effective decision.
 It does not use soft skills
 Always require senior and experts to
monitor the changes.
 It is not easy to implement and run
easily
 It has an unfair reputation in market.
From all the methodologies discussed above, it has been identified that QAHE should go
with Agile methodology over other because its main focus upon customer engagement and also
uses the feedback of stakeholder to make any changes in the decision. The chosen methodology
is more flexible over other and in this regard, it can be acceptable at all platforms. Apart from
this, with the help of Agile methodology, the project manager also collects the feedback of user
and determine the triggers that can be implemented to deliver the project effectively. Thus,
complying with the key rules of Agile, QAHE will easily develop a mobile application that helps
to communicate the essential information to their students due to its flexibility in nature.

REFERENCES
Books and Journals
Avlijaš, G., 2020. Modern Approach to Project Management, Usage, and Success Rate of Agile
Methodologies: an Evidence From Serbia. In
Sinteza 2020-International Scientific
Conference on Information Technology and Data Related Research (pp. 154-159).
Singidunum University.
Azadi, F. and et.al., 2020. Mobile application development and testing for work zone activity
real-time data collection.
Transportation research record. 2674(6). pp.351-362.
Chandrachooodan, G. and Radhika, R., 2020. PROJECT MANAGEMENT METHODOLOGIES
IN E-GOVERNANCE PROJECTS–A CONCEPTUAL REVIEW.
Journal of Critical
Reviews. 7(13). pp.1127-1132.
Hamzane, I. and et.al., 2020. MDA Transformation Process from predictive project management
methodologies to agile project management methodologies.
International Journal. 8(9).
Hillson, D. and Simon, P., 2020.
Practical project risk management: The ATOM methodology.
Berrett-Koehler Publishers.
Nguyen, P. T. and Nguyen, P. C., 2020. Risk Management in Engineering and
Construction.
Engineering, Technology & Applied Science Research. 10(1). pp.5237-
5241.
Ripalda, D., Guevara, C. and Garrido, A., 2020, July. Framework based on Gestalt principles to
design mobile interfaces for a better user experience. In
International Conference on
Applied Human Factors and Ergonomics (pp. 158-165). Springer, Cham.
Testorelli, R., Ferreira de Araujo Lima, P. and Verbano, C., 2020. Fostering project risk
management in SMEs: an emergent framework from a literature review.
Production
Planning & Control, pp.1-15.
Zhao, M. and et.al., 2021. Closure to “Performance of Geogrid-Reinforced and PTC Pile-
Supported Embankment in a Highway Widening Project over Soft Soils” by Mengxuan
Zhao, Chunyuan Liu, Tahar El-Korchi, Haichao Song, and Mingjiang Tao.
Journal of
Geotechnical and Geoenvironmental Engineering. 147(2). p.07020030.
Online
Waterfall model of project management. 2020. [Online]. Available through:
<https://www.toolsqa.com/software-testing/waterfall-model/>