Project templates best practices

Learn how to utilize project templates to jumpstart your data science initiatives.

Templates are an excellent starting point for projects. The default template is based on the CRISP-DM methodology, widely used in data science and certified by the Data Science Process Alliance. However, if your organization has its own process, you can follow best practices to get the most out of these project templates.

#1 Customize the default project template for specific needs

Since every organization is different, we suggest tailoring your template to meet your specific needs. For instance, create templates for Analytics, Operations, Machine Learning, etc.

You can modify your project template by changing phases, requirements, and documentation as necessary.

Once you have a customized project template that works for your organization, we recommend you Duplicate this template for future projects.

#2 Color code text placeholders in templates to display information

To make your project template clear, use color coding for different elements. For instance, use one color for phase descriptions, instructions, or purposes, and another for different information.

In the default template, phase details are in blue, which you can edit or delete, while black text is for phase documentation outlines.

#3 Duplicate your projects

Once you have a project template suitable for multiple projects, you can use the "Duplicate Project" feature. This creates a new project, keeping the original template's phases, requirements, and documentation, saving you from starting from scratch. Duplicate a project via Project Settings > Duplicate Project.

When you duplicate a project, the new project will not include the iterations, models, and datasets from the original.

#4 Use common workspaces to share project templates

Share your custom project templates with others in your organization by creating or using a workspace that includes everyone you want to share with. Members can then duplicate the template and choose their desired workspace for the project.

#5 Pre-define phase requirements within your template

In your project template, define the requirements needed for each phase. When shared, users receive the template with these requirements included for completing the phase.

For instance, the data preparation phase in the default template already has necessary requirements.

#6 Move project templates to designated workspaces

When making a project template for a specific group, you can transfer the customized template to the desired workspace. This move keeps all project information, like datasets, models, code, and iterations. It lets you pre-upload datasets and other assets into the template before sharing.

You can transfer projects only to workspaces where you are a member.