Notes: Project Proposal Title

This document is inspired by Basecamps "Shape up", their process of shaping and betting on things to work on.

The aim is to be a high level document to give as many different people an understanding of "why" and "what".

Problem

Start by defining the problem. This is important for everyone to understand the "why" and the drive behind fixing it.

Context

Add context, essentially the things we can assume going forwards, allows everyone to gain knowledge that we can all assume together.

This could include things such as:

Appetite

How much time is it worth to solve this problem?

This could be 2 weeks of time, 6 weeks of time. As a results of that time what constraints are applied?

Solution

There might be several solutions, however start with the one you're most confident in.

Try to start with a brief one liner to describe what is suggests, and then gradually dive deeper into the details.

Feel free to add diagrams or high level visual mock ups / sketches.

No Gos

Point out the things that specifically won't be covered by the solution.

FAQs

The FAQs section is inspired by Amazons PRFAQ writing structure, where proposals include anticipated questions from an internal and external perspective.

This is a good way to avoid common questions by adding them here as an ongoing log.

Internal FAQs

External