---
title: "Getting Started Checklist"
source: The Turing Way
source_url: https://github.com/the-turing-way/the-turing-way
licence: CC-BY-4.0
domain: data-and-analysis
subdomain: turing-way
date_added: 2026-04-25
---

(pd-checklist)=
# Getting Started Checklist 

We can begin the project design process by identifying different parts of our research, such as main research questions, methods and materials, code and data requirements, workflow, communication channels, ways of working, collaborative practices, and so on. 
This process allows us to be intentional from the start to ensure that our research is reproducible, well-communicated, and inclusive of all stakeholders where decisions are collaboratively made. 
We can explore and select the right tools and methods for reproducibility in our research and promote good practices such as documentation, version control, peer-review processes, testing, workflow, archiving, and data management plans from the beginning. 
Finally, we can plan for publishing and sharing research components before, during, and after the project. 

**Below is a checklist you can use to help identify areas of project planning you might want to look at.**

## Aims & Values 
* Define the main research questions and objectives.
* Identify the core values and principles that guide your project.
* Useful documentation: [project canvas](https://canvanizer.com/new/project-canvas), [values document](https://web.archive.org/web/20240523192550/https://rebelsguidetopm.com/what-are-your-project-values/), [project 1-pagers](https://www.smartsheet.com/content/project-report-templates).

## Timeline & Milestones 
* Establish a project timeline with key milestones, output, and deadlines.
* Break down the project into manageable phases or tasks.
* Useful documentation: [Gantt charts](https://clickup.com/blog/gantt-chart-project-templates/), [roadmaps](https://www.smartsheet.com/free-product-roadmap-templates-smartsheet), or [project boards](https://teamhood.com/project-management/project-board/).

## Methodology
* Determine the appropriate research methods and materials.
* Consider the necessary code and data requirements for your project.
* Document the workflow for data collection, analysis, and interpretation.
* Define data governance processes to ensure data is kept securely, used appropriately, and complies with data regulations in relevant countries/geographic areas. 
* Useful documentation: [data management plan](#rr-rdm-dmp), [code repository](#pd-project-repo), [electronic lab notebooks](#rr-open-notebooks), [Data Governance Chapter](#pd-dg)

## Operations 
* Confirm the budget and any funding policies you need to follow.
* Establish ways of working and collaborative practices for the project team.
* Identify roles and responsibilities within the project team, using the RACI (responsible, accountable, consulted, informed) matrix or the MOCHA (manager, owner, consulted, helper, approver) matrix.
* Complete any institutional processes for project setup, such as ethics approval or contract signing.
* Useful documentation: [RACI matrix](https://project-management.com/understanding-responsibility-assignment-matrix-raci-matrix/), [MOCHA matrix](https://www.managementcenter.org/resources/assigning-responsibilities/#main), [risk register](https://asana.com/resources/risk-register), [project charter](https://www.projectmanager.com/blog/project-charter).

## Stakeholders
* Identify all individuals, groups, or organizations that have an interest or influence in the project. This includes both internal and external stakeholders.
* Create a visual representation or matrix to understand the relationships between stakeholders and the project. Map their level of engagement, influence, and interest at each stage of the project. This helps prioritise engagement efforts and tailor communication strategies accordingly.
* Utilise the ["Facilitating Stakeholder Engagement"](#cl-stakeholder-engagement) chapter for guidance and template resources.
* Useful documentation: stakeholder register, stakeholder map, stakeholder analysis matrix, [personas](#pd-persona).

## Community
If you are intending to build a community for your project or to support participatory research, make a plan!
* Contact communities from your stakeholder mapping and invite them to discuss the project and goals during planning.
* Agree decision making processes for the project involving the community.
* Plan contribution pathways for new participants, establish guidelines for new content, and how you will grow a sense of community.
* Useful documentation: [Code of Conduct](#ch-coc), [Contributing Guidelines](#cl), [READMEs](https://book.the-turing-way.org/collaboration/github-novice/github-novice-firststeps.html?highlight=readmes), [governance documentation](#er-ethics-open-source-governance), [Research Community Managers](#cl-infrastructure-community-managers), [GitHub repo for Research Community Management resources](https://github.com/alan-turing-institute/open-research-community-management)

## Outputs 
* Plan for the different outputs of your research, such as publications, software, or datasets.
* Consider licensing and copyright issues for sharing your outputs.
* Determine how you will manage intellectual property and ownership rights using an IP register.
* Remember to include any required reporting to funders.
* Useful documentation: IP register, [licensing](#rr-licensing) and copyright statement, [data management plan](#rr-rdm-dmp).

## Communications 
* Identify the target audience for your research.
* Plan what you want to communicate to your audiences, when you want or need to share progress or results, and the best channels or mediums to do this.
* Consider open and inclusive practices to involve stakeholders in decision-making.
* Useful documentation: [The Turing Way Guide to Communication](#cm-comms-overview), communication plan.

## Maintenance & Archiving 
* Develop a plan for the long-term maintenance and sustainability of your project.
* Establish procedures for data management, including storage, backup, and access.
* Consider archiving your project's artifacts and documentation for future reference.

### Reporting & Evaluation
* Define how you will judge your project a success (outputs produced, people engaged, milestones reached).
* Define when you will review these metrics and what the criteria is for changing them. 
* Document and understand any external requirements for reporting such as format, timeframe, type, and audience.
