How product is my wow product More we score, more product we have.
Count score: fgrep '(y)' product-checklist.md |grep -v "Count score"|wc -l
Yes:
No:
Open:
Does it have one name (n) Does it have an owner (n) Does it have one owner (n) http://firstround.com/review/square-defangs-difficult-decisions-with-this-system-heres-how/
Has it been (re-)classified in the last 3 months (n) Does it have a documented purpose (n) Does it have a stated scope (n) E.g. what it is and what it is not.
Does it have a product specification (n) Including external/system requirements, and limitations where applicable.
Definition
Does it have a documented description (n) How it fits or relates to our other products or product families?
Does it have documented features (n) Is every major feature documented (n) In a sexy way with pictures
Does it have a getting started tutorial (n) Does it have sales collateral / marketing material (n) Does it have lead qualification guidelines (n) Is the marketing material publicly available (n) Does it have a sales demo available at least to sales (n) Does it have a customer (n) Has customer paid for it in the past (n) Are customers paying for it as a subscription (n) Are customers paying for its support and maintenance (n) Does it have a deployment story (n) Does it have its own repository (n) Does it have a README.md (n) Does it have a high level architecture diagram (n) Including outside interfaces.
Does it have releases (n) Is the latest release installed / running / used somewhere (n) Can our co-workers access the latest release running somewhere (n) Are the changes in the release documented (n) Does it have CI enabled (n) Does it have CI running tests (n) Does it have CI building releases automatically when requested to do so (n) Does it have automatised setup of development environment (n) Is it documented in the README.md (n) Does it include mock data / inputs (n) Does it have an enforced coding style (flake8, eslint, ...) (n) Does it have performance benchmarks (n) Do we keep the performance benchmark history (n) Do we compare release results against benchmark history (n) Have we captured the design goals, choises, plans, drawings, etc (n) Have we reviewed the security of its design? (n) In a review meeting and notes documented.
Have we reviewed the security of its implementation (n) In a review meeting and notes documented.
Have we done it in the last 3 months (n) Does it have reference customers Does it have success stories Does it have testimonials Does it have RoI-calculation