We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Keeping track of architectural-ish decisions in a sustainable way with Juan Saavedra - DCUS 2022
Learn how to record, review and reflect on architectural decisions in a sustainable way, with a focus on collaboration, simplicity and leveraging ADRs to improve software development.
- Define architectural decisions: An architectural decision is a software design choice that is hard to change and has a significant impact on the system.
- Keep track of decisions: Recording architectural decisions helps to capture knowledge, reduce friction, and improve collaboration.
- Use a decision template: A template can help to structure the decision-making process and ensure that important information is captured.
- Involve the right people: Involve the people who will be affected by the decision and those who have the expertise to make informed decisions.
- Consider alternatives: Consider multiple alternatives and their pros and cons to make an informed decision.
- Document the decision: Document the decision, including the context, alternatives, and rationale, to ensure that knowledge is captured and shared.
- Review and reflect: Review and reflect on past decisions to learn from them and improve the decision-making process.
- Keep it lightweight: Keep the decision-making process lightweight and agile to accommodate the fast-paced nature of software development.
- Use ADRs (Architectural Decision Records): Use ADRs to capture architectural decisions and make them easily accessible to the team.
- Involve stakeholders: Involve stakeholders in the decision-making process to ensure that their needs and concerns are considered.
- Consider the impact: Consider the impact of the decision on the system and the team to ensure that it aligns with the overall goals and objectives.