Project Design, Discovery & Planning Checklist

Project Design, Discovery & Planning Checklist

Checklist Item

Details

Discovery Checklist

Identify & Interview the Stakeholders:

  •  
  • Get their vision/initiate the process of setting goals for the project

  •  
  • Get their vision/initiate the process of setting Success Criteria for the project

  •  
  • Document in main project doc. their overall expectation for the project, which will have to be managed in the future

  •  

Choose the Project Management Approach towards the project, approve with stakeholders and sponsor

  •  

Identify who & where (Slack, email) will receive updates on the project and when (Communication/Reporting Plan)

  •  

Identify how to communicate the changes from customer to PM (slack, email, etc.)

Determine a set of Metrics to track

  •  

Conduct Event Storming/User Story Mapping

  •  

Design Checklist

Site structure

  •  

Resolutions + Mobile/tablet version

  •  

UI kit

  •  

Exportable assets

  •  

SVG icons

  •  

Fonts (paid or free/google fonts link or archive)

  •  

Animations

  •  

Email templates

  •  

404 page

  •  

Thank you page

  •  

Website under construction page (if needed)

  •  

Check images & fonts licences

  •  

Notifications styles (error messages, popup,..)

Favicon

  •  

Project Planning

Create checklists

  •  

Determine QA criterias

Create a Project Space in Confluence to store all developed documentation:

  •  
  • Project Charter (link to template)

  •  
  • Change/Issue/Risk Management ()

  •  
  • Internal/External Reporting (link to template)

  •  

Create Slack channel for internal communication

  •  

Create a project in Jira

  •  

Hold a Technical Analysis meeting after designs are approved:

  •  
  • It’s has to be done by the Tech Lead, who is appointed by CTO (or/and CTO himself), and with the Product Lead support, appointed by the VP of Product.

  •  
  • The result of this meeting should be a detailed understanding of how this project will be developed from technical point of view, and what technical risks will be present.

  •  

Finalize the Scope, create backlog in Jira

  •  

Create Milestone Breakdown and Schedule for the project (Baseline):

  •  
  • This should be done with the team, via in person meetings. Make sure Product Lead is synced with project Sponsor on the priorities and vision for the project. Breakdown the project into milestones, estimate the activities, and develop project schedule.risks

  •  
  • The people who will be execution the project – should estimate it

  •  
  • Estbalish budget for project

  •  
  • Establish a deadline

  •  

Get content from the customer (text, images, etc)

  •  

Go to Prod strategy:

  •  
  • Offer the hosting configuration support, best options for the hosting (WPengine, DigitalOcean)

Establish change proces (design change,etc)

  •  

Kickoff Meeting (by PM and client):

  •  
  • Present development plans with objectives and milestones for the project (timeline, iterations) in a standardised format. Possibly get the client acquainted with the team-lead.

Comments

Leave a Reply