- Date: <DATE - when the decision was made>
- Driver: <DRIVER - list a single person driving consenus and decision making>
- Stakeholders: <STAKEHOLDERS - list all relevant stakeholders affected by this decision>
- Status: [PROPOSED | DECIDED | SUPERSEDED]
- Categories: <CATEGORIES - use a simple grouping to help organize the set of decisions (e.g. backend, payment, user management, ...)>
- Outcome: <OUTCOME - once decided, provide a short summary of the decision outcome here>
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, ...)
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 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.
Pros:
- You may list advantages using bullet points that speak for this alternative.
Cons:
- Oftentimes, you find that pros of one alternative are cons to another. In this case you can also reference another "all the pros of alternative Y are cons here", or you can add some additional context on why these are actually cons.
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.