- Date: <DATE - when the decision was made>
- Deciders: <DECIDERS - list everyone involved in the decision>
- Status: [PROPOSED | ACCEPTED | SUPERSEDED | DEPRECATED]
- Category: <CATEGORY - use a simple grouping to help organize the set of decisions (e.g. backend, payment, user management, ...)>
If you have related decisions, requirements, documents or guidelines that affect this decision, link them here. When linking another document, also add one sentence describing why the linked document influences this decision. If there are no related documents, remove this section.
Briefly describe the background information required to understand the problem of the decision being made. Try to answer:
- Are there any assumptions for this decision? (think about: cost, schedule, technology, other projects ...)
- Are there any constraints for this decision? (think about: accepted technology standards, common patterns, ...)
Briefly describe alternative 1 and then list arguments in favor for and against alternative X. You may also list harsh numbers, figures, charts, or anything that helps your future self to understand the decision's motivation.
The decision was made in favor for alternative X.
After stating the decision, briefly explain the motivation that led to choosing the alternative (e.g., by stating which arguments were most important to the team).
Mention the consequences the decision has on the project.