Skip to content

Add Product Owner and Project Manager personas #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gperu merged 1 commit into from
Oct 29, 2026
Merged

Add Product Owner and Project Manager personas #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion source/03-views/personas.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,18 @@ 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.

**Research Software Engineer (RSE)**: Professional software developers working in research contexts who bring software engineering expertise to research projects. They typically prioritize technical quality dimensions like maintainability, testability, and performance, while also understanding research-specific requirements.

**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.
Expand Down
Loading