# Checklist for New Projects

This document is addressed for all team members involved on the project.

# Before to start

# Ask for the resources

  • Sketch design files
    • Desktop
    • Mobile/Tablet
  • Indesign links
    • Notes with animations description (just in case)
  • Font files

# Ask project details

  • Project Brief Doc
    • Description of all specific functionalities and external services integrations if present:
      • Booking Engine
      • Contact form Engine
      • RFP Engine
      • Multisite
      • Instagram posts
      • Hosting owner
      • And any other …
  • Deadlines
    • QA (external provider)
    • Production release

# Create project channel and tools for the team

  • Slack group
    • Pin a message with all links to the resources (Sketch files, fonts, Invision links, Jira board, Git repo url)
  • Git Repository
    • Project setup
  • Staging server
  • Jira Project & board

# Project scoping

The project lead and/or dev team need to review the design files and define all different modules within it’s different options and specific functionalities in the project (ex: image sizes).

After the project review the Jira tickets should be created and located within sprints.

# Jira Tickets

All Jira tickets should be created with the following info:

  1. Short description of module functionality (if necessary)
  2. Image preview of the module design
  3. Links for references (if necessary)

# QA (External provider)

All the issues detected during this stage should be tackled as soon as possible by the dev team and tagged as QA issues (or similar) on Jira for further metrics.


# Production Release

The production release should be prepared as minimum 2 or 3 days before the release date, this means that every detail like domain owner and setup, infrastructure setup, S3 bucket setup, etc… are tested and prepared for the release. The client should know the last day to do content updates on the staging site to prevent data lost during the release.


# Post Released

Once a month the team should check for plugins and framework updates.