Skip to content
#software testing Review Open access

Requirements elicitation for AI-Enabled process automation: A comparative review of Agile, Waterfall, and Hybrid implementation approaches

Sep 2026 · Gulf Journal of Computer Sciences · 0 citations
Robotic Process Automation Applications

Abstract

Organizations adopting AI-enabled process automation are routinely advised to choose a delivery lifecycle that is agile, plan-driven, or hybrid as though the choice applied uniformly across a whole specification effort. That framing is mis-drawn. Building on the author's antecedent five-gate method for converting an ambiguous business problem into an AI-ready specification (problem framing, decision decomposition, data grounding, behavioural specification, and oversight and acceptance), it argues that the gates impose opposite lifecycle requirements. Gates resolving uncertainty about what the business wants reward short cycles, working artefacts, and rapid feedback; gates establishing fixed conditions reward front-loaded rigour, sign-off, and documentation that survives audit. The defensible prescription is therefore neither agility nor hybridity as a blanket label but a gate-differentiated lifecycle: plan-driven discipline where late discovery is irreversible, iterative discipline where early commitment is guesswork. Because empirical work already reports hybrid delivery as the industrial norm, the contribution is a basis for which hybrid, not an argument for hybridity. It is a structured comparative synthesis of published reviews and empirical work in requirements elicitation, agile and hybrid development, process automation, and process mining, read alongside applied literature of varying provenance; it is not a new systematic review and reports no primary data. Its outputs are a three-archetype classification of automation, an eight-dimension comparison matrix across three lifecycle ideal types, a mapping of elicitation techniques, including process mining, to gates and archetypes, a four-factor contingency model, a survey of how lifecycle pressures appear across applied domains, and eight propositions for testing. Keywords: Requirements Elicitation, Intelligent Process Automation, Agile Requirements Engineering, Software Development Lifecycle, Contingency Model, Process Mining, AI Governance.

Read PDF

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.

Microsoft Research Blog Aug 12, 2026

MindTopo reveals VLMs’ spatial reasoning abilities

A path, a fence, a knot. MindTopo sets a new benchmark for testing how AI understands topological relationships and highlights new opportunities to strengthen spatial reasoning and planning. The post MindTopo reveals VLMs’ spatial reasoning abilities appeared first on Microsoft Research.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.