Project Reflection Report: Mobile Application Development Analysis

This project reflection report provides a comprehensive analysis of a mobile application development project. It begins with an overview of the company, Smartapps, its strategic goals, and the project's objectives, scope, and deliverables. The report then delves into traditional project management, examining the PMBOK Process Groups and Knowledge Areas, and how the project was managed to meet stakeholder needs within constraints. Following this, the report explores Agile project management, describing the methodology and frameworks like Scrum and Kanban, and their relevance to the project. The report also highlights strategic enterprise awareness, discussing how the project aligns with the organization's strategic goals, focusing on financial and organizational awareness. The project involves developing an Android and iOS compatible mobile application for a banking firm, aiming to enhance banking services and attract new customers. The report includes detailed discussions of project management, Agile methodologies, stakeholder management, and risk assessment.

Running head: PROJECT REFLECTION REPORT
PROJECT REFLECTION REPORT
Name of the Student
Name of the University
Author Note

1
PROJECT REFLECTION REPORT
Table of Contents
OVERVIEW.........................................................................................................................................2
 Overview of the company and its strategic goals:.....................................................................2
 Broad description of project and relationship to stakeholder objectives...................................2
 The sustainable business value of the project across operational functions..............................2
 High-level review of key objectives, scope, milestones, deliverables, risks and constraints. . .3
TRADITIONAL PROJECT MANAGEMENT ANALYSIS..............................................................4
 The traditional PMBOK Process Groups and Knowledge Areas..............................................4
 Describes how project was organized and managed to meet stakeholder needs within
constraints of scope, cost, time and quality......................................................................................4
AGILE PROJECT MANAGEMENT ANALYSIS.............................................................................5
 Description of Agile project management.................................................................................5
 Description and overview of an Agile project management framework...................................5
 Two Agile frameworks:.............................................................................................................6
Strategic Enterprise Awareness:...........................................................................................................7
CONCLUSION/ PERSONAL REFLECTION....................................................................................7
 Thoroughly summarizes content of the research paper.............................................................7
References:...........................................................................................................................................9

2
PROJECT REFLECTION REPORT
OVERVIEW
 Overview of the company and its strategic goals:
Smartapps is one of the emerging companies in application development sector specializes
in application development in both iOS and Android. With an expert team specializes in Android
and iOS application development, we deliver world class solution to our customer that meets their
business needs and helps them make maximum benefits out of technology for enhancing
productivity and business values.
The strategic goals of the company is to make application of technology affordable and
accessible to all with specific focus in empowering business with digital applications to ensure
sustain business value creation. The company also aspires to make a strong foundation in the market
through enhanced consumer satisfaction.
 Broad description of project and relationship to stakeholder objectives
The project will develop a mobile application which is Android and iOS compatible. It helps
the banking firm to execute their objective to extend their banking services to new customers and
enhance their banking services for their existing customers.
 The sustainable business value of the project across operational functions
Due to the advancement of technology, it is being integrated into various sectors and
banking is one of them. Technology is being integrated into business operation of banks not just
because it increase efficiency, but it is highly regarded by consumers as well, for example mobile
applications are becoming highly popular among consumers as it provides access to banking service
from anywhere anytime. Hence, in order to sustain in market, the banking firm considered in this
project should integrate support for mobile application to attract consumers and offers enhanced
banking services to the consumers. Hence this project provides the sustainable business value of the
project across operational functions

3
PROJECT REFLECTION REPORT
 High-level review of key objectives, scope, milestones, deliverables, risks and
constraints
Key objectives:
The objective of this project is to design, develop and deploy a mobile application
for the banking firm. As the company is in expansion phase, it is becoming difficult for them
to manage their business with their existing infrastructure. Hence the company wants to
have a mobile application that is meant for the employees and stakeholders of the banking
firm.
Scope:
The banking firm wants to develop application to offer banking service to its
consumers through smartphones. The application will support both Android and iOS
platform so that that the banking firm can provide its banking service to a large segment of
consumers. The project is proposed to be finished within 351 days and should not take
longer than 60 to 65 days after source code is designed.
Deliverables:
The deliverables of the project include a fully functional mobile application and a
documents containing technical specification along with manual user guide for helping the
consumers to effectively use the application. Along with that Project Charter, Project Plan,
Requirements Document, Design Document, Source code, Test Plan, Defect Report and a
Closure Report at the end of the project will be provided.
Risks and constraints:
Some of the risks of the project include:
 Application not working as per the project requirements
 Client requirements changed during the execution of the project

4
PROJECT REFLECTION REPORT
 Application crashes during testing process
 Application is not properly optimized for both Android and iOS platforms
 Security features are not properly integrated within the application and thus making the
application less secure
Now along with these risk some of the constraints that might affect the execution of the
project and might affect the project success as well. Constraints include delivering quality product
while maintaining project schedule and budget. Although it is assumed for the project that resources
will be available throughout the project, but it might not be the case as resource scarcity in a project
is one of the common constraints.
TRADITIONAL PROJECT MANAGEMENT ANALYSIS
 The traditional PMBOK Process Groups and Knowledge Areas
The project management plan uses the traditional PMBOK Process Groups and
Knowledge Areas with industry standard artifacts in the initiating, planning, execution,
control, and closing of project (Serrador & Pinto, 2015).
Knowledge Areas PMBOK Process Groups (how applied in this project)
Initiating Planning Executing Monitorin
g and
controlling
Closing

5
PROJECT REFLECTION REPORT
Integration Project charter
developed
Plan for
developing
application
designed
Execution
for the
project with
approval
from
management
Integrated
change
control for
the project
performed
Project
closure
was
done
Scope WBS for
the project
created
Estimation
for activity
cost in the
application
developmen
t
Change
log
designe
d
Time Schedule
for the
project
defined
Schedule
for project
control
designed
Cost Cost
estimation
for the
project
done
Cost
control
integrated
with the
project
Quality Plan for
quality
manageme
nt defined
for project
Quality
assurance
performed
Quality
control
ensured
for the
applicat

6
PROJECT REFLECTION REPORT
ion
develop
ment
Human resource
Communication Detailed
communic
ation plan
developed
for the
project
Communica
tion among
team
members
and
stakeholders
properly
managed
Communic
ation
procedure
properly
controlled
to ensure
effective
communic
ation
Risk Risk
manageme
nt plan
developed
Risk
control
performed
in the
project
Procurement Planning for
procurement
management
plan done for the
project
Procureme
nt
conducted
Procurement
controlled
Procureme
nt closed
Stakeholder Stakeholders for
the project
properly
Stakeholde
r
manageme
Stakeholder
Engagement
managed
Stakeholde
r
Engageme

7
PROJECT REFLECTION REPORT
identified nt plan
developed
properly
with
stakeholder
engagement
strategies
nt
controlled
in the
project
 Describes how project was organized and managed to meet stakeholder needs within
constraints of scope, cost, time and quality
In order to meet stakeholders requirements within constraints of scope, cost, time
and quality, first of all project objectives are defined and it was made clear to the application
developers and every team members who are part of the project (Rasnacis & Berzisa, 2017).
Once project objectives and scope are defined, projects stallholders were identified and their
requirement for the project was gathered and analyzed and a stakeholder register was
created as well. In the next step resource planning was done for proper resource allocation
and make project requirements clear to each and every one so that it is clear to everyone
what tasks they need to perform as per the project timeline and schedule. In order to ensure
that possible risks identified in the project is minimized for ensuring project success and
stakeholder satisfaction, and risk management plan has been developed in this project and
integrated with the project execution. A proper communication plan has been developed as
well to properly communicate with the stakeholders, take feedback from them throughout
the project execution as feedback of the stakeholders plays an important role in software
development project to ensure that the delivered product at the end of the project is
compatible with the stakeholders’ requirements.

8
PROJECT REFLECTION REPORT
AGILE PROJECT MANAGEMENT ANALYSIS
 Description of Agile project management
Agile project management methodologies divides whole project into smaller tasks
and this tasks are managed in sequence. In agile project management, short development
cycle is considered (Patwardhan et al., 2016). These are known as “sprint”. The focus is to
allow continuous development in the product or any service with input taken from the client.
 Description and overview of an Agile project management framework
In order to apply agile project management methodology in this project, first the
projects has to be divided into smaller development cycle or sprint (Larson & Gray, 2017).
1. At the first step, a steering meeting has to be organized for defining business needs or
vision required to develop a mobile application, which is Android and iOS compatible.
Then a product roadmap for developing the mobile application has to be defined which
contain high-level overview of the requirements (Gomes, Oliveira, & Chaves, 2018).
2. Once this is completed, a timeline for executing the project needs to be defined. Then a
meeting arranged with the product owner, project managers, and all team members that
are part of developing the mobile application, allows them to provide input regarding
sprint planning which has to be done before initiation of any sprint cycle. Weekly sprint
as well monthly sprint based on the project requirements decided and shared with the
team members to provide a clear overview of the project progress.
3. Now meeting with the team members are to be arranged daily to ensure that project
execution is according to the project plan. This include review of development progress
on code design required for developing the application.
4. Once a sprint which might be weekly or monthly sprint is completed, review should be
done with feedback from client and identify issues as pointed out by the client or the
stakeholders. If according to the feedback, modifications or improvement is needed, it

9
PROJECT REFLECTION REPORT
has to be incorporated into the sprint. Without completing one sprint properly, next
sprint is not considered
5. Once a sprint that is design of code is completed, the next sprint, which might include
deployment and testing of the designed code for identifying issues in the coding process
in the plan, is considered and same process flows for each sprint until the project is
completed and the application is delivered to the banking firm.
 Two Agile frameworks:
Scrum: how this framework is relevant in this project
It is the most well-known and popular agile project methodology and widely
considered for software development projects as it is effective and simple as well to
implement in project (Malik, Ahmad & Hussain, 2019). In this project, Scrum is considered
as it allows product owner that is the banking firm in this context, to work in close
association with the application development team and this makes it is easier for them in
identifying and prioritizing their goals and add these to product backlog (Larson & Gray,
2017). This backlogs include “features, bug fixes, and non-functional requirements— pretty
much anything that needs to be done in order to deliver working software”
Kanban: how it is relevant to this project
It is also an agile methodology like agile, but it is based continual delivery. The
project team has considered this methodology as it not only keeps things simple but also
makes the jobs of developer teams easier (Nasir et al., 2015). It helps in visualizing
workflow in a board, which makes the project execution extremely informative and easier to
follow as well, even when the project is complex in nature and need extensive guidance to
complete the project with efficiency (Goodison, Borycki & Kushniruk, 2019).

10
PROJECT REFLECTION REPORT
Strategic Enterprise Awareness:
The objective of this project is to design, develop and deploy a mobile application for the
banking firm. As the company is in expansion phase, it is becoming difficult for them to manage
their business with their existing infrastructure. Hence, the company wants to have cost efficient
and effective solution for that. A mobile application that is designed in this project is meant for the
employees and stakeholders of the banking firm. The company with this application will be able to
bring more consistency in their business process through improved consumer management and a
streamlined approach in the business operations, which is the strategic goal of the organization. The
project slect technologies for the project and develop the project plan in such a way that the
application is cost effective and any additional cost due to schedule delay is minimized effectively.
The project has provided special attention to ensure the designed application is efficient and capable
to meet these specified requirements of the stakeholder as discussed in this context.
CONCLUSION/ PERSONAL REFLECTION
 Thoroughly summarizes content of the research paper
In order to ensure ethical and culturally aware project management practices in
leadership it is required that each and every member is treated equally and no bias in
workplace is entertained which will help to provide motivation to the team member. In order
to ensure legal and ethical standard in communication it is important to ensure that
communication is done in proper way so that each and every one is aware of the project
progress and there is no confusion among stakeholder and team members which enhances
stakeholder management and teamwork. Hence this standards should be integrated with
project execution process.

11
PROJECT REFLECTION REPORT
References:
Gomes, F., Oliveira, M., & Chaves, M. S. (2018). An analysis of the relationship between
knowledge sharing and the project management process groups. Knowledge and Process
Management, 25(3), 168-179.
Goodison, R., Borycki, E. M., & Kushniruk, A. W. (2019). Use of Agile Project Methodology in
Health Care IT Implementations: A Scoping Review. Studies in health technology and
informatics, 257, 140-145.
Larson, E. W., & Gray, C. F. (2017). Project management: The managerial process. McGraw-Hill
Education.
Malik, R. S., Ahmad, S. S., & Hussain, M. T. H. (2019). A Review of Agile Methodology in IT
Projects. Available at SSRN 3351064.
Nasir, M. H. N. M., Sahibuddin, S., Ahmad, R. B., & Fauzi, S. S. B. M. (2015). How the PMBOK
Addresses Critical Success Factors for Software Projects: A Multi-round Delphi
Study. JSW, 10(11), 1283-1300.
Patwardhan, A., Kidd, J., Urena, T., & Rajgopalan, A. (2016). Embracing Agile methodology
during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.
Rasnacis, A., & Berzisa, S. (2017). Method for adaptation and implementation of agile project
management methodology. Procedia Computer Science, 104, 43-50.
Serrador, P., & Pinto, J. K. (2015). Does Agile work?—A quantitative analysis of agile project
success. International Journal of Project Management, 33(5), 1040-1051.