Skip to content
#software testing Open access

Beyond Productivity: Human-Centered Guardrails for AI-Assisted Research Software Workflows

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research)
Software Engineering Techniques and Practices Software Engineering Research

Abstract

AI-assisted development tools can reduce friction in routine software work, but generation speed alone does not establish software quality. In research software engineering, AI-assisted changes still need to be reviewable, reproducible, maintainable, and usable across contributors and environments. This talk presents a proposed three-checkpoint guardrail framework for AI-assisted research software workflows. It builds on a published exploratory study of AI-assisted frontend development that evaluated productivity across three stages: drafting, verification, and refinement. The study also compared AI-assisted and manual development on a small set of UI tasks, with a focus on accessibility checks. The results showed that productivity should consider how much time is spent on verifying and refining the code and not just how quickly we were able to produce the first draft. The framework uses three checkpoints: reviewability, reproducibility, and human-centered quality. Reviewability means making sure an AI-assisted change is very clear, in scope, and supported by good documentation for another contributor to review and verify it. Reproducibility means the change can be built, tested, and run consistently across different environments. Human-centered quality means checking how the software would behave for the people who maintain and use it, including accessibility and usability issues that basic automated tests might have missed. The talk uses accessibility as an example of how the three checkpoints can be applied in practice. An AI-generated user interface may appear complete while still missing accessible names, semantic errors, keyboard or focus failures, or have unclear error feedback. Applying the checkpoints means the change should be understandable to a reviewer, reproducible in a consistent environment, and evaluated with automated checks with targeted semantic, keyboard, focus, and interaction verification before we begin integration. The framework is presented as an adaptable workflow model rather than a broadly validated standard. Attendees will leave with a practical way to evaluate AI-assisted changes by asking not only, “Did AI make this faster?” but also whether another person can review it, reproduce it, maintain it, and use it.

View source

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

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring 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.