You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Document a decision for an option. This is useful to state the reasons and the options that have been evaluated. Later other team members will have it easier to understand the decision.
Properties
The document type decision provides the following properties:
Type
Types allow to group decisions. A project demands its own definition of types via the decision type document type.
Sections
Problem
Defines the problem for which a decision has been made by the team. The problem has these subsections:
Details
Defines the problem that this decision solves.
Relevance
Details why this is relevant for the project and why it should be documented to be referable later.
Implication
Details what implications this decision has on the project.
Problem Constraints
Documents constraints on the problem that influence the decision. These constraints are described in the following subsections:
Requirements
Illustrates the functional and non-functional-requirements that constrain the decision.
Drivers
Details what other drivers are relevant for the decision.
Risks
Details which risks are involved for the decision.
Assumptions
Decisions have to be made in situations where not every information detail is available. Otherwise the path to take would be clear without any doubts. To close the gaps between known and unknown assumptions have to be made. This section allows to document the assumption so that the decision is better understandable later.
Description
Details which assumptions have been made to make the decision. It is assumed that assumptions cannot be proven else this would be a requirement or not mentioned if proven invalid.
Check Assumptions
Describe strategies how the given assumptions can be proofed or refuted?
Risks
Which risks are assumed this assumption has.
Alternatives
A list of alternatives that have or have not been examined.
Decision
Provides information about the decision that has been made.
Statement
The decision statement defines what has been decided to do. This should be a brief statement since this is also rendered in the index document.
Reason
States what reasons led to the decision.
Implication
Details what implications this decision has on the project.
Date
The date of the decision.
Decider
The list of stakeholders that made the decision. If there is uncertainty about why this decision has been made, these stakeholders may provide additional information. Consider then to include this information in this document.
Notes
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 information. 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 suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
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 information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.
