product_specs.md

Functional specification

Purpose and guidelines

This template can be used by teams to help them think through the purpose, goals, and implications of product ideas and features. This should be seen as a living document and should therefore be edited in non-permanent locations such as Dropdbox Paper or Google Docs. These documents should be accessible and editable by the entire team.

Not all sections need to be filled out, and the entire document certainly won't be completed up front. As a living document, fill out what's applicable and available, and add/remove as you go.

---

Project plan — PROJECT NAME

🚀 Product Opportunity Assessment

This is a modified version of Marty Cagan's outline presented in Assessing Product Opportunities.

Exactly what problem will this solve? (value proposition)

For whom do we solve that problem? (target market)

How will we measure success/make money from this product? (metrics/revenue strategy)

What alternatives are out there? (competitive landscape)

What factors are critical to success? (solution requirements)

😬 Dependencies and Risks

Known risks

What should we acknowledge as potential knock-on effects on other projects?

Cross-team dependencies

Do we need help from other teams?

Customer Support impact

Is new help documentation needed? Does existing documentation need to be updated?

Analytics impact

What additional reporting is needed to ensure that the new product or features can be tracked effectively?

😃 Solution overview

General overview of how we plan to address the problem

Breakdown of proposed tasks and release schedule

Estimated time frame