Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Document Properties Marker
overridefalse


Short DescriptionDocument 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. 
Doctypedoctypehide
NameDecision 
IDdecision 
SuiteProject Management
SetProject Management hide
Parent
Parent Property
parent-doctypetopic
property-nameName
 
Audience
Name List
doctyperole
render-no-hits-as-blanktrue
propertyAudience
 
Documentation Type
Name List
doctypedoctype-type
render-no-hits-as-blanktrue
namesQ2 - Project
propertyDocumentation Type
 
Categories
Name List
doctypecategory
names/ Project
propertyCategories
 
Tags
Tag List
 
Iteration
Iteration
valuefilled
hide
Sort Keyhide


...

Section
titleProperties


Transclusion
documentNote Box referencing common Document Properties
idsBox


Section
titleType

Group decisions by their type. A project may provide its own set of types via the Decision Type Doctype.


Section
titleSponsors

List the stakeholders that take special interest in this decision and therefore support the effort put into this.


...

Section
titleSections


Section
titleSummary

Give a short summary about what has been decided. Add anything that is of interest for users having a brief look at this document.


Section
titleProblem

Define the problem for which a decision has been made by the team. The problem has these subsections:

Section
titleDetails

Define the problem that this decision solves.


Section
titleRelevance

Provide details why this is relevant for the project and why it should be documented to be referable later.


Section
titleImplication

Provide details what implications this decision has on the project.



Section
titleProblem Constraints

Document constraints on the problem that influence the decision. These constraints are described in the following subsections:

Section
titleRequirements

Illustrate the functional and non-functional-requirements that constrain the decision.


Section
titleDrivers

Provide details what other drivers are relevant for the decision.


Section
titleRisks

Provide details which risks are involved for the decision.



Section
titleAssumptions

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.

Section
titleDescription

Provide 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.


Section
titleCheck Assumptions

Describe strategies how the given assumptions can be proofed or refuted?


Section
titleRisks

List the risks you assume this assumption has.



Section
titleAlternatives

Provide a list of alternatives that have or have not been examined.


Section
titleDecision

Provide information about the decision that has been made.

Section
titleStatement

Define what has been decided to do. This should be a brief statement since this is also rendered in the index document.


Section
titleReason

State what reasons led to the decision.


Section
titleImplication

Provide details what implications this decision has on the project.


Section
titleDate

Specify the date of the decision.


Section
titleDeciders

Provide a list of stakeholders that made the decision. If there is uncertainty about why this decision has been made, these stakeholders may provide additional information at a later time. Consider then to include this information in this document.

 

 

 



Section
titleSubordinate Decisions

Add decisions to this decision as child documents if these decisions are in a close relationship.

 

 

 


Transclusion
documentDocument Sections
idsstandard-sections-bottom

 

...

Section
titleResources
  • For a more detailed introduction to architecure decisions, please refer to Stefan Zörner's book
    Cite
    template$[Name]
    documentPDAC:Zörner2012
    , chapter 3.


Piwik Set Multiple Custom Variables


NameValue
Departmentprojectdoc
Categoryprojectdoc-doctype
Typeproject-management