Aligning feasible technical requirements to research objectives and steering collaboration: role and responsibilities of the Research Software Analyst in RSE teams

This talk will focus on the role institutionalised at King’s Digital Lab of the Research Software Analyst as key member of the RSE team acting as first point of contact with project partners throughout a project / product lifecycle from collaborative requirements definition (including contribution to funding applications) to project management during evolutionary development (including negotiations around prioritisation of requirements / increments), testing of the solution components and negotiations around acceptance at release phase, to reporting and decommissioning at post-project phase. The competences of this role are relevant for RSEs typically involved in complex research projects which require at minimum an agreed understanding of technical requirements with at least one other individual (e.g. project lead, other researcher / RSE / colleague, funder / sponsor, project partner). The role is particularly relevant for RSE groups and team operating at scale, delivering on complex projects with multiple stakeholders, running in parallel and often requiring concept design if not a full funding application with estimate of effort prior to starting. Building on Agile DSDM roles definitions (https://www.agilebusiness.org/dsdm-project-framework/roles-and-responsibilities.html) and business analysis good practices, the role has evolved based on the specificity of the institutional context and research domains (mainly arts, humanities and social sciences) within which KDL operates; however, the talk will generalise the role profile and functions to enable the audience to identify potential alignment with other contexts and roles across disciplines. The talk will focus on: RSA role description (standard, senior and principal levels) building on the document authored by KDL founding Director; walkthrough project feasibility assessment phase aligned with research objectives and to inform funding applications with associated example/s compliant with KDL project templates; outline of the activities led by the RSA during evolutionary development to monitor progress, steer collaboration with a variety of stakeholders and facilitate the solution development team work. A recording of this session is available on YouTube: https://youtu.be/g2Rb87QNPrk

Institutions

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2025-12-17
DOI
https://doi.org/10.5281/zenodo.17967410
Primary Topic
Scientific Computing and Data Management
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Aligning feasible technical requirements to research objectives and steering collaboration: role and responsibilities of the Research Software Analyst in RSE teams

Zenodo (CERN European Organization for Nuclear Research)
Scientific Computing and Data Management
article

Aligning feasible technical requirements to research objectives and steering collaboration: role and responsibilities of the Research Software Analyst in RSE teams

article en

Abstract

This talk will focus on the role institutionalised at King’s Digital Lab of the Research Software Analyst as key member of the RSE team acting as first point of contact with project partners throughout a project / product lifecycle from collaborative requirements definition (including contribution to funding applications) to project management during evolutionary development (including negotiations around prioritisation of requirements / increments), testing of the solution components and negotiations around acceptance at release phase, to reporting and decommissioning at post-project phase. The competences of this role are relevant for RSEs typically involved in complex research projects which require at minimum an agreed understanding of technical requirements with at least one other individual (e.g. project lead, other researcher / RSE / colleague, funder / sponsor, project partner). The role is particularly relevant for RSE groups and team operating at scale, delivering on complex projects with multiple stakeholders, running in parallel and often requiring concept design if not a full funding application with estimate of effort prior to starting. Building on Agile DSDM roles definitions (https://www.agilebusiness.org/dsdm-project-framework/roles-and-responsibilities.html) and business analysis good practices, the role has evolved based on the specificity of the institutional context and research domains (mainly arts, humanities and social sciences) within which KDL operates; however, the talk will generalise the role profile and functions to enable the audience to identify potential alignment with other contexts and roles across disciplines. The talk will focus on: RSA role description (standard, senior and principal levels) building on the document authored by KDL founding Director; walkthrough project feasibility assessment phase aligned with research objectives and to inform funding applications with associated example/s compliant with KDL project templates; outline of the activities led by the RSA during evolutionary development to monitor progress, steer collaboration with a variety of stakeholders and facilitate the solution development team work. A recording of this session is available on YouTube: https://youtu.be/g2Rb87QNPrk

Zenodo (CERN European Organization for Nuclear Research)
Weatherford College (US)
Openalex Percentile: Top 17%
Scientific Computing and Data Management
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.