Student ID: XXXXXXX

Module: LDI7002M – Strategic Project Management

Assessment: Project Management Plan (Component 2)
Project Title: Development of a Mobile Banking Application for a Commercial Bank
Industry: Financial Technology (FinTech)
Word Count: Approx. 2,500 words

1. Introduction and Project Justification

The global banking sector is undergoing rapid digital transformation driven by technological
innovation, changing customer expectations, and increased competition from FinTech firms.
Mobile banking applications have become a strategic necessity rather than a value-added service,
enabling banks to deliver secure, convenient, and personalised financial services anytime and
anywhere. According to the Project Management Institute (PMI, 2021), projects that align with
organisational strategy and customer value are more likely to achieve long-term success. In this
context, the development of a mobile banking application represents a strategically significant
project for a commercial bank seeking to enhance customer experience, operational efficiency,
and competitive positioning.

This project aims to design, develop, and deploy a secure mobile banking application that allows
customers to perform core banking activities such as balance enquiries, fund transfers, bill
payments, mobile deposits, and customer support access. The business case is underpinned by
increased smartphone penetration, the demand for digital-first banking services, and the need to
reduce reliance on physical branches. From an organisational perspective, the project supports
cost optimisation, customer retention, and data-driven service innovation. Therefore, a structured
Project Management Plan (PMP) is essential to ensure that the project objectives, deliverables,
quality requirements, and timelines are clearly defined and effectively managed.

2. Industry and Project Specialism: FinTech

The FinTech industry is characterised by rapid innovation, high regulatory scrutiny, and strong
customer-centricity. Key developments include the adoption of mobile-first platforms, cloud
computing, application programming interfaces (APIs), artificial intelligence, and enhanced
cybersecurity mechanisms. Regulatory compliance, particularly in areas such as data protection,
anti-money laundering (AML), and know-your-customer (KYC) requirements, plays a critical
role in shaping FinTech projects (Arner, Barberis and Buckley, 2017).

For project managers operating in the FinTech sector, technical competence alone is insufficient.
They must demonstrate strong stakeholder management skills, an understanding of regulatory
environments, agile leadership capabilities, and the ability to manage cross-functional teams
comprising developers, compliance specialists, cybersecurity experts, and business stakeholders.
Furthermore, FinTech projects often operate in uncertain and fast-changing environments,
requiring flexibility, rapid decision-making, and continuous risk assessment (Kerzner, 2022).
These sector-specific characteristics directly influence the choice of project management
methodology for the mobile banking application project.

3. Area 1: Critical Evaluation of Project Management

Approaches (60%)
3.1 Overview of Relevant Project Management Methodologies

Several project management approaches are applicable to technology-driven projects, including

Waterfall, Agile, and Hybrid methodologies. The Waterfall approach follows a linear and
sequential structure, where each phase must be completed before the next begins. While this
approach provides clear documentation and control, it lacks flexibility and is less suitable for
projects with evolving requirements (PMI, 2021).

Agile methodologies, particularly Scrum, emphasise iterative development, customer

collaboration, and responsiveness to change. Agile is widely used in software development due
to its ability to accommodate changing user requirements and deliver incremental value
(Schwaber and Sutherland, 2020). However, Agile may present challenges in highly regulated
environments where documentation and compliance are critical.

Hybrid approaches combine elements of both Waterfall and Agile, enabling organisations to
maintain governance and control while benefiting from flexibility in development stages. This
approach is increasingly adopted in financial services projects where regulatory compliance must
coexist with innovation (Boehm and Turner, 2004).

3.2 Justification of the Selected Approach

For the development of a mobile banking application, a Hybrid Agile approach is the most
appropriate. The project requires strict adherence to regulatory standards, security protocols, and
risk management processes, which align with traditional project management practices.
Simultaneously, the user interface, functionality, and customer experience components benefit
significantly from iterative development and continuous user feedback.

In practice, the project will adopt a Waterfall structure for high-level planning, regulatory
approvals, and architectural design, while utilising Agile Scrum for application development and
testing phases. Similar approaches have been successfully implemented by major banks such as
ING and HSBC, which have adopted Agile frameworks within controlled governance structures
to accelerate digital transformation (Rigby, Sutherland and Takeuchi, 2016).

3.3 Benefits and Limitations of the Chosen Approach

The primary benefit of the Hybrid Agile approach is its balance between control and
adaptability. It enables early identification of compliance risks while allowing rapid refinement
of application features based on stakeholder feedback. This approach also supports enhanced
stakeholder engagement, improved transparency, and faster time-to-market. However, it requires
strong leadership and clear communication to manage potential conflicts between traditional and
agile practices. Effective governance mechanisms and clearly defined roles are therefore
essential to mitigate these challenges.

4. Area 2: Quality Management (40%)

4.1 Quality Expectations

Quality expectations for this project focus on security, reliability, usability, and regulatory
compliance. The mobile banking application must provide a seamless user experience, ensure
data confidentiality, and demonstrate high availability. These expectations align with ISO/IEC
25010 software quality standards, which emphasise functional suitability, performance
efficiency, security, and usability (ISO, 2011).

4.2 Acceptance Criteria

Acceptance criteria define the measurable conditions under which project deliverables are
considered acceptable by stakeholders. Key acceptance criteria for this project include successful
completion of security penetration testing, compliance with banking regulations, system uptime
of at least 99.9%, and positive user acceptance testing (UAT) outcomes. Acceptance criteria will
be prioritised in collaboration with senior management, compliance officers, and end users.

4.3 Quality Specifications

Quality specifications describe the technical and functional standards the application must meet.
These include encryption standards (e.g. AES-256), multi-factor authentication, response time
thresholds, and compatibility with major mobile operating systems. Compliance with internal IT
policies and external regulatory requirements will be continuously monitored throughout the
project lifecycle.

4.4 Quality Control Measures

Quality control measures include automated testing, code reviews, security audits, and regular
sprint reviews. A dedicated quality assurance team will be responsible for monitoring adherence
to standards and reporting deviations. Continuous improvement practices, such as retrospectives,
will support learning and performance enhancement.
5. Project Schedule and Gantt Chart
A clear and realistic project schedule is essential to ensure effective planning, coordination, and
control of project activities. In line with best practice in project management, a Gantt chart has
been developed to visually represent the project timeline, phase sequencing, durations, and
dependencies (Kerzner, 2022).

The mobile banking application project is planned over a 12-month lifecycle, which is
appropriate given the regulatory, security, and technical complexity associated with FinTech and
banking projects. The schedule reflects the selected Hybrid Agile approach, combining
structured upfront planning with iterative development.

5.1 Gantt Chart Overview

Figure 1 presents the Gantt chart for the project and illustrates six logically sequenced phases:

 Initiation & Business Case (Month 1): Development and approval of the business case,
identification of key stakeholders, and formal authorisation of the project through a
project charter.
 Planning & Regulatory Review (Months 2–3): Detailed requirements gathering,
regulatory and compliance analysis, risk planning, and high-level system architecture
design.
 Agile Development (Sprints) (Months 4–8): Iterative development of the mobile
banking application using Agile sprints, including user interface design, backend
integration, API development, and security configuration.
 System & Security Testing (Months 9–10): Comprehensive system testing, penetration
testing, and user acceptance testing (UAT) to ensure functional reliability, security, and
regulatory compliance.
 Deployment & Training (Month 11): Application deployment to mobile app stores,
staff training, customer onboarding support, and go-live readiness activities.
 Project Closure & Handover (Month 12): Formal project closure, documentation
handover to operations teams, post-implementation review, and capture of lessons
learned.

The Gantt chart clearly demonstrates task dependencies, particularly the requirement for
planning completion before development, and successful testing approval prior to deployment.
Key milestones such as regulatory sign-off, UAT approval, and go-live readiness act as formal
control points within the schedule.

This structured and realistic schedule supports effective progress monitoring, resource allocation,
and risk management, while ensuring alignment with organisational governance and quality
expectations.

Figure 1: Gantt Chart for the Mobile Banking Application Project

--------------|---------------|----------|------------| | Initiation | Business case approval, stakeholder
identification, project charter | Month 1 | None | | Planning | Requirements analysis, regulatory
review, risk planning, architecture design | Months 2–3 | Initiation complete | | Development |
Sprint-based mobile app development, API integration, security configuration | Months 4–8 |
Planning complete | | Testing | System testing, security testing, user acceptance testing (UAT) |
Months 9–10 | Development complete | | Deployment | App store deployment, staff training,
customer onboarding | Month 11 | Testing approved | | Closure | Project review, documentation
handover, lessons learned | Month 12 | Deployment complete |

The Gantt chart clearly identifies critical dependencies, particularly between development,
testing, and regulatory approval stages. Milestones such as regulatory sign-off, UAT approval,
and go-live readiness serve as formal control points. This structured schedule supports effective
progress tracking, resource allocation, and early identification of delays.

6. Critical Reflection and Capability Development

This project highlights key strengths in analytical thinking, stakeholder engagement, and
adaptive leadership. However, it also reveals areas for improvement, particularly in managing
regulatory complexity and cross-functional communication. To enhance project management
capability, targeted professional development in Agile leadership and financial regulation is
recommended. Continuous learning and reflective practice are essential to meeting the demands
of complex FinTech projects.

7. Conclusion
The development of a mobile banking application is a strategically important project within the
FinTech sector. By adopting a Hybrid Agile project management approach and implementing
robust quality management practices, the project is well-positioned to deliver value to both the
organisation and its customers. This Project Management Plan demonstrates systematic
understanding, critical analysis, and practical application of project management theory in a
contemporary business context.

Reference List
Arner, D.W., Barberis, J. and Buckley, R.P. (2017) ‘FinTech and RegTech in a nutshell, and the
future in a sandbox’, Journal of Banking Regulation, 19(4), pp. 1–14.

Boehm, B. and Turner, R. (2004) Balancing Agility and Discipline. Boston: Addison-Wesley.

ISO (2011) ISO/IEC 25010: Systems and software quality models. Geneva: International
Organization for Standardization.

Kerzner, H. (2022) Project Management: A Systems Approach to Planning, Scheduling, and

Controlling. 13th edn. Hoboken: Wiley.

PMI (2021) A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 7th
edn. Newtown Square: Project Management Institute.

Rigby, D.K., Sutherland, J. and Takeuchi, H. (2016) ‘Embracing Agile’, Harvard Business
Review, 94(5), pp. 40–50.

Schwaber, K. and Sutherland, J. (2020) The Scrum Guide. Available at: [Link]