Agile vs. Waterfall: Comparative Analysis and Methods Selection
Comparative Analysis of Agile vs Waterfall Project Management
Agile, a framework based on an iterative software development process, emphasizes adapting requirements and solutions through inseparable teamwork among self-organizing, multi-functional team members, as shown in Figure 2. It stands for adaptive planning, evolutionary development, early implementation, and continuous improvement, which motivate team members to enable flexibility and responsiveness to change (Gaborov et al., 2022).
Agile addresses projects in shorter time increments, known as sprints, with more room for idea revision and feedback. The waterfall is a project management methodology that is multifold, with tasks executed sequentially through a set of phases, as shown in Figure 1 (Thesing, Feldmann, and Burchardt, 2021). Each stage should be completed before the next, with only minor opportunities to return at the end of certain steps to make necessary changes.


Pros of Agile Methodology
Using the Agile methodology, we get access to various benefits that make this approach a top contender for software development projects. The flexibility allows rolling out updates and improvising when needed until the product is ready to meet all market needs and conditions (Elkhatib et al., 2022). Furthermore, Agile fosters customer satisfaction through the continuous feedback cycle, enabling teams to respond to customer needs and improve product features and functionality with real-time user input.
Cons of Agile Methodology
While agile methodology offers a range of advantages, it also presents a few challenges that teams with the right attitude cannot overcome. Unconditionally, the need for experts is the most notable disadvantage (Kuhrmann et al., 2022). At its core, Agile leverages team members’ most fertile abilities through constant collaboration. Therefore, this requires team members to be highly skilled and committed to productivity (Alsaqqa, Sawalha, and Abdel-Nabi, 2020). A seasoned agile team leader who can identify key principles and best practices can prevent the new team from making mistakes, thereby reducing inefficiency, miscommunication, and project delays.
Pros of Waterfall Methodology
The waterfall method has its pros and unresolved issues, making it suitable for certain project types. The journey of the project management phases is the unifying thread, the indistinctive ground upon which project management teams can build. It offers a clear structure with well-defined phases, but the process is easy to understand and implement, especially for new project management teams (Halani and Jhajharia, 2022). The Waterfall phases are defined to provide clarity and traceability, hence giving the developers a way to stay on the current picture. Waterfall also guarantees forecast and goal achievement; the resources are easily and securely optimized as a project progresses.
Cons of Waterfall Methodology
Nonetheless, Waterfall has drawbacks that may hinder its success if the project is undertaken in a specific context. A key disadvantage is its limited flexibility. With a waterfall’s strict linear-like steps (Iwersen, Zem, and de Penteado Neto, 2023). Secondly, Waterfall often needs more customer involvement, with stakeholder communication usually confined to the initial requirement definition phase. Moreover, Waterfall is a linear process that poses a higher risk of project failure, particularly due to changes in requirements or revisions later in the development cycle.
Justification for More Appropriate Methodology
As the fintech startup in London revises its BNPL app to meet customer needs better, an agile approach is a more advantageous way to navigate its permeability and coexistence amid changing uncertainties and needs. The research in this regard is highly revealing, particularly valuable for software development projects, where even compliance flexibility is vital. We needed help improving the usability and stability of the old version of the app (Zavyalova, Sokolov, and Lisovskaya, 2020).
Another reason for adopting agility is a customer-driven approach that suits this project. While the product’s agility is widely recognized for driving adoption and customer satisfaction, the client’s objectives of customer collaboration and regular bug fixes align perfectly with Agile’s mission (Khan et al., 2020). Furthermore, Agile limits the risk of project failure because the development process is segmented into smaller chunks managed in separate stages, and failures can be detected and resolved in the first stages of development.
Project Tasks, Dependencies, and Critical Path Overview
Table 1: Tasks and activities
Sprint Planning and Scrum Implementation for the BNPL App
Scrum Framework for Developing the BNPL App: Sprint Plan
- Sprint Planning: This is the weekly meeting at the beginning of the sprint, where team members identify the items from the product backlog that will be tackled in a particular sprint. For sprints pertinent to our installment loan product, the team chooses a few user stories or activities from the queue to work on.
- Daily Stand-up (Daily Scrum): These are short and informal daily meetings used to match up activities and prepare for the day. Each team member answers three questions: What was my daily routine yesterday? Today, whether to venture or get a job is my own decision. Do you find there are any burdensome objects in your path?
- Sprint Review: At the close of the sprint, the team will demonstrate the features and functions developed to the stakeholders, receiving comments and evaluation. They take that feedback to start planning for the next sprint.
- Sprint Retrospective: A meeting is usually done right after the sprint review, in which the team considers what went well and what needs to be improved, and eventually identifies the actions for the next sprint.

Sprint Backlog
A sprint backlog is created by selecting tasks from the previously defined Critical Path Analysis (CPA) activity table
Table 2: A sprint backlog
Explanation of the Sprint Cycle
The sprint begins with sprint planning, during which a team selects its tasks from the product backlog based on priority and capacity. The Sprint backlog will consist of user stories covering tasks such as design, requirements gathering, testing, market research, feedback analysis, development, implementation, and training. The team portion of the sprint engages team members in both individual and collective tasks (Ferguson, Harnish, and Chase, 2021). The daily stand-up meetings during this phase ensure that participants work in harmony and that everyone is aware of progress. Tasks are broken down into slightly larger units and completed step by step.
In collaboration with stakeholders, the team puts together what it learned at the sprint’s end. During the sprint review, we showcased the completed work. Lastly, the team benefits from the sprint retrospective, as it can reflect on its processes and identify areas for improvement (Ferguson, Harnish, and Chase, 2021). The continuous cycle means the team becomes increasingly efficient and effective in the discovery process, and by the end of the development process, they will have a successful BNPL app.
Applying PMBoK and PRINCE2 Frameworks in App Development
Advantages of PMBoK
The PMBoK (Project Management Body of Knowledge) framework is considered one of the best. Thus, all its areas are connected so that one can apply them equally in any situation. It demonstrates adaptability, as the processes and methodologies it recommends for software development projects can be tailored to each project’s needs and features (Mahmoud Saleh and Karia, 2022). Adaptability within the team enables it to adopt agile and iterative processes when necessary, and this is made possible by the flexibility and dynamic nature of software development (Čabarkapa, 2019). Moreover, global standardization is an advantage, as it establishes a common language and a reference framework for global project management practitioners.
Disadvantages of PMBoK
PMBOK may encompass many successful project management practices. The implications of PMBoK, as expressed through several documents, terminology, and processes, introduce complexity into project processes. This can be problematic, especially for experienced project managers and teams. Moreover, when opposite approaches, such as scrum and kanban, are compared, one can see some limits of this methodology (Villamil, Pinilla, and Martin, 2019). These demands for change may affect agility and adaptability; flexibility is necessary in dynamic development, where many changes are required because standardized guidelines and expectations are absent.
Advantages of PRINCE2
PRINCE2 offers several benefits over PLM, particularly its structured nature and its focus on business reasons. Through its ladder-like structure, the waterfall model defines responsibilities and processes at each level of the project life cycle to ensure uniform consistency across projects with varying natures. Its second essential attribute is the business justification element, which is crucial for aligning projects with organizational targets and creating tangible value for stakeholders (Kous, 2023). Through this framework, PRINCE2 allocates resources and investments based on business needs, thereby increasing project success rates and ensuring the project remains strategically significant to the organization.
Disadvantages of PRINCE2
The rigid structure inherent in PRINCE2 might cause difficulties in agile or adaptive software development environments that prioritize flexibility. The team’s ability to be innovative and responsive to ongoing consumer needs may become impeded by the rigid adherence to existing processes and documentation. There may be missed opportunities for innovative problem-solving and adaptability, which are pivotal factors in achieving the goals of future projects (Sobieraj, Metelski, and Nowak, 2021). Finally, the extensive bureaucracy and procedures of PRINCE2 could lead to unnecessary project overheads and inefficiencies.
Applicable Processes from PMBoK and PRINCE2 for the BNPL App Development Project
From PMBoK
Executing processes from the PMBOK is key to achieving project management success for software development initiatives similar to BNP, L. First goal: guarantees integration management within each project to achieve a synergistic relationship between objectives and progressively set goals (Sigoals Monaitis, Daukšys, and Mockienė, 2023). The outcomes of this process align the main project components, creating an environment for development and advancing the achievement of project objectives.
Moreover, the Project Scope Management will make the scheme’s limits understandable, and the deliverables will be clearly defined and controlled (Techcanvass, 2022). The team will be responsible for avoiding scope creep and will prioritize the key project objective through detailed scope management. The next task is to make detailed estimates, allocate work to the project timelines, and monitor the project.
From PRINCE2
The use of the three phases from agile-oriented PRINCE2 project management (PMP) theory, namely Starting Up a Project (SU), Initiating a Project (IP), and Managing Product Delivery (MP), will support the success of the BNPL app development assignment. The main advantage of the project management process is that it enables the team to set clear project objectives, define the project approach, and allocate appropriate resources during the initial development phase (PRINCE2, 2024). Subsequently, the IP process is used to develop detailed project plans with full documentation, including the business case for the project’s initiative.
Reference List
Alsaqqa, S., Sawalha, S. and Abdel-Nabi, H. (2020) ‘Agile software development: methodologies and trends‘, International Journal of Interactive Mobile Technologies (iJIM), 14(11), p. 246.
Čabarkapa, J. (2019) ‘Analysis and comparison of ISO 21500 – guidance on project management and PMBOK 6th guide’, Proceedings of the 5th IPMA SENET Project Management Conference (SENET 2019).
Elkhatib, M. et al. (2022) ‘Agile Project Management and project risks improvements: Pros and cons’, Modern Economy, 13(09), pp. 1157–1176.
Ferguson, H.A., Harnish, C. and Chase, J.G. (2021) ‘Using field based data to model Sprint Track Cycling Performance‘, Sports Medicine – Open, 7(1).
Gaborov, M. et al. (2022) ‘The purpose of internet use among pupils during the Covid-19 pandemic‘, Security-Related Advanced Technologies in Critical Infrastructure Protection, pp. 433–442.
Halani, K.R. and Jhajharia, K. (2022) ‘A quantitative study of Waterfall and Agile methodologies with the perspective of project management’, Contemporary Challenges for Agile Project Management, pp. 111–133.
Iwersen, L.H., Zem, L. and de Penteado Neto, R. (2023) ‘Choosing the Best Project Management Methodology for Research and Development Projects: Agile, Waterfall, or hybrid?‘, REVISTA FOCO, 16(11).
Khan, F. Q. et al. (2020) ‘A comparative analysis of RAD and Agile technique for management of computing graduation projects‘, Computers, Materials & Continua, 64(2), pp. 777–796.
Kous, K. (2023) ‘Process-oriented model for managing software development projects using the PRINCE2 method‘, Advances in Business Strategy and Competitive Advantage, pp. 30–59.
Kuhrmann, M. et al. (2022) ‘What makes Agile Software Development Agile?‘, IEEE Transactions on Software Engineering, 48(9), pp. 3523–3539.
Leightley, D. (2022) The Agile development methodology employed during development of the InDex app.
Mahmoud Saleh, F.I. and Karia, N. (2022) ‘Adaptive project management model for the International Development and Aid projects‘, Nonprofit Management and Leadership, 33(2), pp. 383–409.
PRINCE2 (2024) The 7 principles, themes and processes of PRINCE2.
Simonaitis, A., Daukšys, M. and Mockienė, J. (2023) ‘A comparison of the project management methodologies Prince2 and PMBOK in managing repetitive construction projects‘, Buildings, 13(7).
Singh, S. (2022) Agile or Waterfall: which app development approach to consider?
Sobieraj, J., Metelski, D. and Nowak, P. (2021) ‘PMBOK vs. Prince2 in the context of Polish construction projects: structural equation modelling approach’, Archives of Civil Engineering, pp. 551–579.
Techcanvass (2022) Project management principles for complete newcomers.
Thesing, T., Feldmann, C. and Burchardt, M. (2021) ‘Agile versus Waterfall project management: decision model for selecting the appropriate approach to a project’, Procedia Computer Science, 181, pp. 746–756.
Villamil, K.L., Pinilla, H.R. and Martin, J.G. (2019) ‘Proposal of a methodology of project management for SME’s of the building sector through the start-up and planning processes of the PMBOK guide‘, 2019 Congreso Internacional de Innovación y Tendencias en Ingenieria.
Zavyalova, E., Sokolov, D. and Lisovskaya, A. (2020) ‘Agile vs traditional project management approaches‘, International Journal of Organizational Analysis, 28(5), pp. 1095–1112.