---
title: "Guide for Project Design"
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)=
# Guide for Project Design

***This guide covers topics related to effective project planning and management.***

In this guide, we compile best practices and guidance for designing research projects by including different aspects of project management and (iterative) development practices derived from academia and industry.

Before starting a project, researchers must define the project's scope. 
Researchers should start by identifying the main questions they aim to address through their work. Scope definition also includes defining the project goals, possible outcomes, resources requirements, people involved (collaborators, users and target audience) and possible constraints.

Researchers can then proceed to identify the expected minimum viable product of their project, synergies with other projects (similarities as well as differences), measure(s) of success, and the overall impact they hope to achieve.
After these crucial questions are addressed, planning can focus on the operational aspects of the project, including ensuring that the project is usable and compliant with appropriate external guidelines (for instance, ethics requirements and regulatory limitations). 

```{figure} ../../figures/project-design.*
---
name: project-design
alt: A group of people collaboratively developing a project plan by writing on a giant canvas with a giant pencil to signify the importance of design work in the project management process. 
---
 _The Turing Way_ project illustration by Scriberia. Used under a CC-BY 4.0 licence. DOI: [10.5281/zenodo.3332807](https://doi.org/10.5281/zenodo.3332807).
```
When designing a team-based project, it is important to think about all the skills required for the project and the resources needed to access those skills.
The project design also includes aspects such as timeline, budget, risks, expectations, resources for project management and preregistration of research protocols.
With these viewpoints, we welcome chapters defining the requirements in a project in terms of up-skilling, supporting and improving accessibility of different stakeholders.

We hope you will learn from different case studies for small, mid-size, and large projects spanning both short-term and long-term plans.
If you are brave enough, your examples of failed projects will be incredibly valuable for understanding how to avoid making the same (totally understandable) mistakes again.

Check out our [contributing guidelines](#ch-contributing) to get involved.
