Date: Fri, 29 Mar 2024 15:37:08 +0100 (CET) Message-ID: <906126210.17972.1711723028601@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17971_804525059.1711723028601" ------=_Part_17971_804525059.1711723028601 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Products used by customers intend to make a change. This change is calle= d outcome.
The document type outcome provides the following properties:
Please note that only information about specific properties is provided = here. Common document property used by all document types are documented by= Document Propert= ies.
Specify the type of the outcome to organize them.
Use the outcome = type to define types of outcomes.
List the stakeholders responsible for the outcome.
Automatically lists the users of the parent document.
List users who benefit from this outcome.
Automatically lists the users of the parent document.
In case the short description is not enough, the description secti= on provides room for more detailed information about the outcome.
Describe why this outcome is useful for your business. State the problem= to be solved.
Describe who is involved in the outcome. List the stakeholders that will= support the outcome. There may be stakeholders who will work against it. A= lso specify the stakeholders taking advantage or taking disadvantage even i= f they do not have power to influence the outcome.
Describe how the outcome will be pursued.
Describe the (high-level) deliverables (aka output) required to achieve = the outcome.
List of outputs related= to this outcome.
Child documents of the output type are automatically listed.
In case you need to document a complex outcome by breaking it into its p= arts. Add outcome documents as children to this document.
These are internal notes that are usually not exported and only visible = to team members with write access.
But this is not a safe place to store sensible informat= ion. It is just a convenience for the reader to not be bothered with notes = stored here for the authors for later use. The security level is about supp= ressing the representation by a CSS style. Therefore consider this as a con= venience for the reader, not as a security tool.
The text of notes sections is also indexed.
For a document the references section contains pointers to resources tha= t prove the statements of the document.
Often these proofs are not easily distinguishable from further informati= on. In this case you may want to skip the reference section in favour for t= he resource list.
For further information please refer to References and Resources.
The resources section provides references to further information to the = topic of the document.
This may be information on the internet provided by the resource or info= rmation in the team's information systems. Anything the reader of the resou= rce might want to know, may be listed here.
For further information please refer to References and Resources.