Previous document: Discovery results

Related documents


<aside> πŸ‘‰

The goal of this document is to present an initiative in the most compact and concise form to give stakeholders the opportunity to understand it’s potential impact to effort, dependencies and other necessary factors.

</aside>

<aside> β›³

The outcome of the pitch process a decision to reject or to add this initiative into the Product roadmap.

</aside>

<aside> πŸ‘ͺ

This document is collaborative in its nature, so its various parts are owned and developed by various people.

</aside>

Why & What

Role Position Person
Accountable Product Manager
Responsible Product Manager, Product Designer, Technical Lead
Consulted Key stakeholders
Informed Other stakeholders

Context

<aside> ❓ What lead us to conclusion that there is a problem or opportunity? (Summary of the discovery results)

</aside>

– Write in here

Problem/Opportunity

<aside> ❓ What specific problem are we aiming to solve with this initiative? Is there customer feedback indicating a problem or a metric that is in an unfavourable state? Are there any research results? If this is an opportunity, how is it defined?

</aside>

– Write in here

How & How much

Solution

<aside> ❓ Do we have a specific solution or set of ideas for addressing this problem/opportunity? How can we set its boundaries?

</aside>

– Write in here

Impact Estimation

<aside> ❓ What do you aim to achieve with this new initiative? What impact we are anticipating and how will we measure it?

</aside>

Effort Estimation

Role Position Person Sign off date
Accountable Technical Lead
Responsible Dev team, QA
Consulted Product Manager, Product desinger
Informed Key stakeholders

<aside> ❓ Do we have any preliminary estimates on the development effort required for this feature?

</aside>