If you've ever built software I'm sure you've been asked "Why'd you do X and not Y!?", to which you must go through the whole history of the project and explain why you made that decision.
After running into this issue at multiple companies, I developed the Prototype Maturity Model for evaluating a software prototype. It is intended to be used as a working document for teams that are taking a software prototype from its inception, to mass adoption. This can be used for teams building internal tools, SaaS companies building a new platform, or any team that must make tough decisions when trying to get innovative ideas developed rapidly.
With PMM, you can point people to the project's evaluation history. Without detailing each and every decision, the PMM will give stakeholders the information they need to understand the project history, and easily identify areas they may want to focus their effort in improving the prototype as a whole.
After running into this issue at multiple companies, I developed the Prototype Maturity Model for evaluating a software prototype. It is intended to be used as a working document for teams that are taking a software prototype from its inception, to mass adoption. This can be used for teams building internal tools, SaaS companies building a new platform, or any team that must make tough decisions when trying to get innovative ideas developed rapidly.
With PMM, you can point people to the project's evaluation history. Without detailing each and every decision, the PMM will give stakeholders the information they need to understand the project history, and easily identify areas they may want to focus their effort in improving the prototype as a whole.
Let me know what you think HN.