# Software project brief

Fone · Version 1.0 · 2026-09-29
Free to copy and adapt for your own projects and client work.

## 1. Problem and audience
- Who needs this product?
- What do they do today?
- What result would make the project useful?

## 2. One complete journey
- Starting point:
- User action:
- Inputs:
- System response:
- Output and who reviews it:
- Failure/recovery path:

## 3. Release boundary
| Include in first release | Later | Outside scope |
| --- | --- | --- |
| | | |

## 4. Existing context
- Current product / source repository:
- Integrations and API documentation:
- Data sources and who can authorize access:
- Design assets and content:
- Hosting / operating constraints:
- Never paste passwords, secrets or confidential customer data here.

## 5. Acceptance
| User journey | Observable result | Evidence | Reviewer |
| --- | --- | --- | --- |
| | | | |

## 6. Unknowns and assumptions
| Question or assumption | Owner | How to resolve it | Effect on scope |
| --- | --- | --- | --- |
| | | | |

## 7. Responsibilities
- Product decision owner:
- Technical lead:
- Collaborators and responsibilities:
- Access required by each person:
- Release approver:
- Operating/support owner after launch:

## 8. Constraints and next step
- Target date and why it matters:
- Budget range and currency, if known:
- Dependencies or deadlines outside our control:
- Next review and the decision it should produce:

This is a planning aid, not a quote or delivery guarantee.
More context: https://fone.cc/insights/scope-a-software-project/