Content area
Modern engineering projects, characterized by increasing complexity, challenge traditional methodologies such as Waterfall, Agile, and Systems V models. While these methods are systematic and methodical, they often lack the flexibility to accommodate the evolving demands and uncertainties of large-scale new product development initiatives. Innovations in digital transformation and entrepreneurial eco-system design, driven by AI, machine learning, and Internet of Things (IoT), highlight the need for adaptive, iterative development methods that can reduce product time-to-market durations. Agile methods are typically used for software development and are often difficult to apply in hardware-centric projects. This paper presents an Integrated Agile V-Model framework, that combines Agile's iterative flexibility with the V model's structured, gate-driven approach. This hybrid framework streamlines complex system management, risk mitigation, stakeholder engagement, and cross-functional collaboration throughout the project lifecycle. The framework could particularly be beneficial in sectors such as aerospace, defense, advanced manufacturing, healthcare, construction, energy, automotive, and technology, where adaptability and objective-driven milestones are critical to project success.
Abstract
Modern engineering projects, characterized by increasing complexity, challenge traditional methodologies such as Waterfall, Agile, and Systems V models. While these methods are systematic and methodical, they often lack the flexibility to accommodate the evolving demands and uncertainties of large-scale new product development initiatives. Innovations in digital transformation and entrepreneurial eco-system design, driven by AI, machine learning, and Internet of Things (IoT), highlight the need for adaptive, iterative development methods that can reduce product time-to-market durations. Agile methods are typically used for software development and are often difficult to apply in hardware-centric projects. This paper presents an Integrated Agile V-Model framework, that combines Agile's iterative flexibility with the V model's structured, gate-driven approach. This hybrid framework streamlines complex system management, risk mitigation, stakeholder engagement, and cross-functional collaboration throughout the project lifecycle. The framework could particularly be beneficial in sectors such as aerospace, defense, advanced manufacturing, healthcare, construction, energy, automotive, and technology, where adaptability and objective-driven milestones are critical to project success.
Key Words
Hybrid Agile Methods, Agile, Systems Engineering V, Product Development, Hardware
Abstract ID 5604
1. Introduction
As engineering projects grow in complexity, traditional methods like the Waterfall and V models improving new product development time to market -prompting a shift toward hybrid approaches that integrate Agile principles with systems engineering. Although systematic and foreseeable, traditional project management and systems engineering methods like the Waterfall model, or the V model sometimes struggle to meet the increased need for flexibility and scope change. This is especially true in large, multidisciplinary projects with long development cycles, frequent customer changes, and complex technical challenges. These organizations must manage complex systems while adapting to new information, customer needs, and risks. In the aerospace industry, NASA and SpaceX have highlighted the need for iterative testing and responsive engineering practices during spacecraft development- challenging the predictability of traditional models. Similarly, defense contractors like Lockheed Martin have integrated Agile practices to manage evolving requirements and reduce risk during long-cycle weapons system development. These organizations face pressure from evolving regulatory environments, international collaboration requirements, and the growing use of digital twins, Al-driven design, and the Internet of Things (loT), all of which increase integration and verification complexity. As a result, integrating Agile methodologies-known for short iterations, stakeholder collaboration, and adaptive planning-into systems engineering practices helps organizations respond to change without sacrificing the rigor required for safety-critical systems. Regulatory mandates, safety protocols, and the need for extensive testing and validation-essential parts of systems engineering-require a systematic process that ensures responsibility, oversight, and goal achievement; therefore, a need exists to merge the philosophies of Agile and the systematic V approach. The proposed Integrated Agile V-Model Framework addresses this need by aligning Agile's flexibility with the structured verification and validation gates of the V model, ensuring traceability, accountability, and high reliability while allowing for rapid feedback and cross-functional collaboration.
2. Problem Description
The Challenge of Complexity in Modern Engineering ProjectsContemporary engineering projects face increasing complexity that existing project management and systems engineering models struggle to address. This complexity is driven by rapidly evolving digitalization, automation, globalization, and the integration of advanced technologies such as artificial intelligence (AI), machine learning (ML), and the Internet of Things (loT). Traditional methodologies like the Waterfall model and the V model offer structured, systematic processes valuable for managing compliance, safety, and verification; however, they often lack the flexibility needed to accommodate changing customer requirements and iterative development cycles. This is mostly evident in large-scale, multidisciplinary integration efforts. For instance, aerospace and defense programs typically involve multi-year development timelines and stringent regulatory oversight, yet must still adapt to evolving stakeholder inputs, emergent technologies, and risk mitigation needs. While Agile methods offer adaptability and faster feedback loops, they may fall short in addressing the milestone-driven rigor needed for complex system development and integration. This creates a gap in project management capabilities-one that becomes costly and disruptive when late-stage changes arise. To address this challenge, a hybrid framework is proposed that blends the responsiveness of Agile with the discipline of the V model, offering a balanced solution that supports cross-functional integration, iterative delivery, and the high-assurance needs of complex engineering product development.
3. Research Questions
The integration of traditional and Agile methodologies is the subject of research in hybrid product development methodologies, addressing the challenges and opportunities that emerge. Understanding the differing philosophies between Agile's iterative, flexible planning and the comprehensive, upfront strategies of traditional models is a critical focus. Questions arise regarding the establishment of frameworks that facilitate seamless collaboration between development teams and executive management, thereby assuring alignment and capitalizing on the strengths of both methodologies. Researchers are currently exploring the potential of hybrid models to reconcile the adaptability of Agile with the detailed planning. Additionally, they are exploring the definition of important concepts, such as milestones or completed iterations, within these frameworks. The objective is to create strategies that optimize the application of Traditional and Agile methodologies to new product development initiatives, thereby improving their interoperability. The following research questions have been identified, and answered in this paper, through the literature review process.
RQ1: How can Agile planning be improved to address perceptions of its incompleteness by executive Management? [1]
RQ2: What are the interactions between Agile and classical practices, and how can they be effectively integrated to improve product development outcomes? [2]
RQ3: How does one integrate the planning process of a traditional gated model with the sprint planning model of Agile (plan on the fly)? [3]
Future work will answer the following questions that were also identified in the Literature Review:
RQ1: What should be in a backlog? What does a backlog look like in the hybrid model? [3]
RQ2: What is a sprint deliverable in a hybrid model? What constitutes a done sprint? [3]
4. Methodology
This paper introduces the Integrated Agile V-Model Framework, which blends Agile's iterative adaptability with the systems engineering V model's systematic, gate-driven rigor. This framework is designed to handle the increased complexity of multidisciplinary engineering projects that require quick adaptability and strict project control. This paper uses a hybrid model to show how the Integrated Agile V-Model Framework can reconcile Agile and Waterfall methodologies to improve project planning, risk management, and complex system development. Integrating Agile's iterative methods with the Stage-Gate and V models' structured milestone-driven approach improves systems engineering and project management. Iterative review cycles before each system gate promote stakeholder involvement, making the model a valid contribution. The Integrated Agile V-Model Framework helps define the backlog, especially for physical product development. Unlike classic Agile models that focused primarily on software features, the hybrid framework combines system-level activities needed to develop physical products and systems. The concept concludes by addressing executive & leadership concerns regarding incomplete Agile planning. By combining Waterfall's with Agile's iterative adaptability, the framework provides a mechanism for executive visibility into critical project milestones and deliverables being achieved and mapped to Sprint execution within the Development team. The Integrated Agile V-Model Framework offers a balanced methodology that bridges the gap between Agile flexibility and traditional systems engineering discipline-making it a robust solution for complex engineering environments.
4.1 Integrated Agile V-Model Framework Overview
The Integrated Agile V-Model Framework provides a systematic methodology for planning and executing complex projects by aligning Agile Sprints within the Systems V lifecycle. It combines the Gate reviews of the conventional Waterfall approach with the iterative sprints and Agile Program Increment Cycles, ensuring a cohesive integration of both methodologies. The framework offers a clear visual depiction of the product lifecycle, integrating aspects of conventional project management with Agile principles which facilitates understanding and monitoring of project planning and progress. This framework enables the project team to correlate Sprints to Gates by providing a visual planning and tracking tool for executive management or stakeholders who may lack familiarity with Agile. This agile bridge guarantees both operational flexibilities along with systematic supervision during the project's period of performance.
4.2 Incorporation of MAHD Concepts and Program Integration Cycles
Authors of the Modified Agile for Hardware Development (MAHD) Framework suggest two levels of development cycles [4]. MAHD Iteration Planning and IPAC (Integration, Prototype, Alignment, Customer) Cycles create the game plan for success while sprints provide the execution details. Using that philosophy in the subject framework, Program Integration Cycles (PICs) are used to provide a longer-term vison into each of the sprint planning iterations to ensure proper short-term planning is identified in each of the sprints.
4.3 Hybrid Agile Considerations and Procurement Constraints
Lastly, the Hybrid Agile community frequently engages in discussions regarding the constraints of physicality, particularly as teams work to apply Agile principles to environments that involve hardware, physical components, or manufacturing processes. This model also emphasizes the ongoing and overlapping nature of procurement activities in such contexts by incorporating a procurement activity that extends across multiple sprints to address this challenge. Unlike a pure Agile environment, which is primarily software-focused and does not involve the acquisition of physical parts, Hybrid Agile must consider the logistical complexities, supplier dependencies, and lead times resulting from procurement of physical products. Software-only Agile that adheres strictly to the core principles and practices outlined in the Agile Manifesto (or commonly referred to as Pure Agile [5]) implementations, enable teams to concentrate exclusively on iterative development cycles, free from external supply chain constraints. Nevertheless, in a Hybrid Agile framework, these procurement activities are essential for guaranteeing that physical parts are received in accordance with the sprint objectives and gate milestones. This introduces an additional layer of complexity that necessitates meticulous planning and coordination among development, procurement, supply chain, and other operational teams.
Figure 1 is an overview of the correlation between the V Model and Agile philosophies in linear form. The linear link between the V Model and Agile sprints are shown in Figure 1.
4.4 Sprint Backlogs and the CAB Model
In the Integrated Agile V-Model Framework, backlog artifacts are essential in every sprint cycle, providing the foundation for planning and execution. Figure 2 below is an initial cooncept which provides an overview of the preliminary CAB definition. Each sprint backlog is customized to meet specific deliverables corresponding to the gate reviews in the V model for planning purposes. This includes work packages related to design, integration, and testing that align with essential system requirements. The sprint backlogs ensures that the execution team concentrates on fulfilling both Agile objectives and V milestone needs, providing an inclusive roadmap for systemmatic project development while allowing for adaptation based on a dynamic environment. It correlates the Gate reviews from the conventional waterfall methodology with the iterative sprints and Program Integration Cycles of Agile, allowing for merging the two methodologies. It correlates the Program Inegration Cycles (PICs) and sprints with critical Systems Engineering V Gates, such as SRR, PDR, CDR, MRR, and SVR. An exhaustive list of all engineering artifacts required throughout the period of performance will be completed as part of forward work, which specifies priorities and establishes the criteria for a "done sprint" in terms of both physical deliverables and documentation artifacts. The timeline for each artifact is visually represented by arrows in Excel cells, which indicate the start of work and an "X" denotes the completion point that supports the gate review. This method combines Agile principles with the Systems Engineering V process to ensure all necessary artifacts and deliverables are systematically addressed within the framework of iterative development. This comprehensive strategy allows for the timely completion of all necessary work packages required based on system and project requirements. Finally, the model emphasizes three key components essential for project execution: physical deliveries, continuously updated programmatic artifacts, and comprehensive engineering products.
4.5 Application to Research Questions
The framework answers the research questions identified by the authors identified in paragraph 3. This methodology blends Waterfall's structured Gate reviews with Agile's iterative sprints and offers a sprint backlog based on the Period of Performance to plan and organize work cycles. Stage-Gate's strict phases and Agile's dynamic, on-the-fly planning ensure resource distribution and project execution are in synch, allowing for continual updates and progress tracking. Secondly, the CAB template answers the question of an effective backlog in hybrid models for product development. The sprint backlogs are integrated within the V model milestones, which provides a flexible roadmap that solves product development needs and requirements. Finally, by combining Waterfall's broad project scope with Agile's iterative adaptability, the methodology helps to facilitate executive buy-in by filling Agile planning gaps by ensuring the team is taking into consideration a holistic view of the overall project scope. The methodology helps executives understand and oversee the product lifecycle by visualizing Agile sprints and Waterfall gate-driven reviews in conjunction with each other.
5. Conclusion and Future Work
The Integrated Agile V-Model Framework advances systems engineering by combining Agile's iterative flexibility with the V model's ordered, milestone-focused methodology. This hybrid framework manages complex engineering projects with the flexibility to adapt to changing requirements and the rigor to meet project milestones. The model's repeated sprint cycles before each system gate encourage stakeholder interaction, early verification, and validation, reducing risks, and schedule. The CAB template helps prioritize backlogs to product enhancements and project needs. This strategy enables Agile teams and project management executives to manage and communicate product development initiatives more effectively. Future work will include: (1) completing the CAB, (2) conducting interviews with industry Subject Matter Experts (SMEs) to further explore the practical use and efficacy of the Integrated Agile V-Model Framework, and (3) addressing the additional research questions outlined in Section 3. The interviews will assess the framework's ability to combine the V model's structured, milestone-driven methods with Agile's sprint cycles. Discussions will focus on research alignment, relevance, feasibility, impact, perceptions and experiences. SME feedback will improve the framework and CAB template to match real-world project management methods based on real world applications and experience.
References
[1] Salvato, J. J., & Laplume, A. O. (2020). Agile Stage-Gate Management (ASGM) for physical products. R&D Management, 50(5), 631-643. https://doi.org/10.1111/radm.12428
[2] Gabriel, S., Niewoehner, N., Asmar, L., Kühn, A., and Dumitrescu, R. (2021). Integration of agile practices in the product development process of intelligent technical systems. Procedía CIRP, 100, 427-432. https://doi.org/10.1016/j.procir.2021.05.099
[3] Cooper, R. G., & Sommer, A. F. (2016). The Agile-Stage-Gate hybrid model: A promising new approach and a new research opportunity. Research-Technology Management, 59(1), 21-29. https://doi.org/10.1080/08956308.2016.1117317
[4] Simpson, D., & Hinkle, G. (2023). The benefits of Agile, the needs of physical product development: An introduction to modified Agile for hardware development framework. MAHD Framework LLC. Retrieved from www.mahdframework.com
[5] Borba, J. C. R., Trabasso, L. G., & Pessôa, M. V. P. (2019). Agile management in product development. Research-Technology Management, 63(5), 63-66. https://doi.org/10.1080/08956308.2019.163 8488
Copyright Institute of Industrial and Systems Engineers (IISE) 2025