Date: Fri, 29 Mar 2024 16:16:23 +0100 (CET) Message-ID: <1078085112.17982.1711725383877@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17981_346023526.1711725383876" ------=_Part_17981_346023526.1711725383876 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
State assumptions and hyp= otheses to run your experiments. Document your output and plan for outcome = and impact.
Assumptions document what you think about your product, customers, and p= artners. Once you start identifying assumptions, it will become clearer wha= t other beliefs you hold about how you plan to build, design, distribute, a= nd create value with your product. Making assumptions explicit allows to pu= blish them and discuss them with other stakeholders.
Write your problem hypothesis. This is the hypothesis that you will eith= er validate or (probably) come back and revise.
Publish an impact you want to achieve. Share this information with your = colleagues.
Products used by customers intend to make a change. This change is calle= d outcome.
The output is the artifact created to be employed by user for a specific= outcome and - on the long run - may make an impact.
Assumptions can be resolved in different ways. Define what each resoluti= on implies.
Type-specific category for assumption resolutions.
Type-specific category for assumptions.
Type-specific category for hypotheses based on status.
Type-specific category for hypothesis status.
Type-specific category for hypotheses.
Type-specific category for impacts.
Type-specific category for outcomes.
Type-specific category for outputs.