From dc98fe09afb86c04606e1da2680ac60e9592b4e7 Mon Sep 17 00:00:00 2001 From: Giacomo Peru Date: Wed, 28 Oct 2026 16:15:20 +0000 Subject: [PATCH] Add Product Owner and Project Manager personas from RSQKit --- source/03-views/personas.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/03-views/personas.md b/source/03-views/personas.md index 96036f1..8ab4e15 100644 --- a/source/03-views/personas.md +++ b/source/03-views/personas.md @@ -4,7 +4,7 @@ Research software quality considerations vary significantly depending on one's r ### Core Personas in Research Software -The RSQKit identifies five primary personas within the research landscape, each with specific software quality interests and responsibilities: +The RSQKit identifies seven primary personas within the research landscape, each with specific software quality interests and responsibilities: **Researcher who codes**: Scientists and researchers who develop software as part of their research activities, ranging from simple analysis scripts to more complex tools. Their primary focus is often on functionality and getting research results, though they benefit from guidance on maintainability and reproducibility practices. @@ -12,6 +12,10 @@ The RSQKit identifies five primary personas within the research landscape, each **Principal Investigator**: Research leaders responsible for project oversight, funding, and strategic direction. Their software quality interests often center on sustainability, compliance, risk management, and ensuring software supports research objectives and reproducibility. +**Product Owner**: Responsible for ensuring that the software being developed delivers value to its intended users and stakeholders. They act as a bridge between principal investigators (project leaders), Research Software Engineers (RSEs) and infrastructure providers on one end, and users, institutional or community stakeholders on the other. + +**Project Manager**: Responsible for coordinating the successful delivery of software-related projects and managing various resources, including people, tasks and timelines. Their role focuses on planning, organisation, communication, risk management and ensuring that software development activities progress effectively and on time. + **Policy Maker**: Individuals involved in developing guidelines, standards, and policies for research software at institutional, national, or international levels. They focus on frameworks for assessment, recognition, funding criteria, and alignment with broader research integrity goals. **Trainer**: Educators and training coordinators who teach software development skills to researchers. They need to understand quality practices across all levels and translate complex concepts into accessible learning materials appropriate for diverse audiences.