Required agreements with/information from PO *before* a project starts

We don't have these captured ***anywhere*** and are often quick to rush into projects (because decisions on moving ahead are usually made pretty last minute) without ensuring that all of the work that the Product Owner (PO) needs to do ***ahead of the start of a project*** has had adequate (if any) thought go into it.

As such, the POs are somewhat surprised when we ask them for 'all this information' once the project has begun. They need to be captured and importantly _systematised_.

+ Is contract signed and filed?
+ What is the `definition of done` for the project?
+ What does `success` look like for the project?
+ What is the [OMTM](https://github.com/dwyl/hq#one-metric-that-matters) that is measuring that success?
+ Describe all users for the website and create personas > https://github.com/club-soda/club-soda-guide/issues/93
+ Determine what the content types are https://github.com/club-soda/club-soda-guide/issues/94
+ What metrics do we need to capture in order to determine `success` for each of these content types and users? https://github.com/club-soda/club-soda-guide/issues/97 The key is to know at every step that we are building something people _want_ and this is the only way to be sure of that