3 ms·
Architectural Retrospectives: The Key to Getting Better at Architecting
- jph 2y agoArchitecture retrospectives sound like a good idea but don't seem to be "the key" because in practice they fail too often. Retrospectives look backwards, and most teams aren't wired that way. And unlike sprint retrospectives, architecture retrospectives turn up issues that are unrealistic/impossible to adjust in real time. Instead, try lightweight architectural decision records, during the selection process, at the start, when things are easiest to change, and can be the most flexible. When teams try ADRs in practice, teamwork goes up, choices get better, and implementations get more realistic. And if someone later on wants to do a retrospective, then the key predictive information is right there in the ADR. https://github.com/joelparkerhenderson/architecture-decision-record/ https://github.com/joelparkerhenderson/architecture-decision...
- 101011 2y agothank you for sharing this! I'd seen formats similar to this but I'd never seen what the format itself is called. very helpful to see it clearly described - I think I'll try to give this a go with our teams
- westurner 2y agoIs there already a good way to link an ADR Architectural Decision Record with Threat Modeling primitives and considerations? "Because component_a doesn't support OAuth", "Because component_b doesn't supported signed cookies" Threat Model: https://en.wikipedia.org/wiki/Threat_model https://en.wikipedia.org/wiki/Threat_model GH topic: threat-modeling: https://github.com/topics/threat-modeling https://github.com/topics/threat-modeling Real and hypothetical architectural security issues can be linked to CWE Common Weakness Enumeration URLs. SBOM tools help to inventory components and versions in an existing architecture and to JOIN with vuln databases that publish in OSV OpenSSF Vulnerability Format, which is useful for CloudFuzz, too.
- jph 2y agoGood question. Yes there are a variety of ways that help. 1. If the team favors lightweight markdown, then add a markdown section for Threat Modeling and markdown links to references. Some teams favor doing this for more kinds of analysis, such as business analysis (e.g. SWOT) and environment analysis (e.g. PESTLE) and risk analysis (e.g. RAID). 2. If the team favors metrics systems, then consider trying a Jupyter notebook. I haven't personally tried this. Teams anecdotally tell me these can be excellent for showing probable effects. 3. If the team is required to use existing tooling such as tracking systems, such as for auditing and compliance, then consider writing the ADR within the tracking system and linking to it internally.
- westurner 2y ago> 1. Add clickable URL links to the reference material for whichever types of analyses. > 2. Jupyter Notebooks often omit test assertions that would be expected of a Python module with an associated tests/ directory. With e.g. ipytest, you can run specific unit tests in notebook input cells (instead of testing the whole notebook). There are various ways to template and/or parametrize notebooks; copy the template.ipynb and include the date/time in the filename__2024-01-01.ipynb, copy a template git repo and modify, jupyterlab_templates, papermill > 3. [...] consider writing the ADR within the tracking system and linking to it internally +1. A "meta issue" or an epic includes multiple other issues. If you reference an issue as a list item in GFM GitHub-Flavored Markdown, GitHub will auto-embed the current issue title and closed/open status: - https://github.com/python/cpython/issues/1 - python/cpython#1 This without the leading `- ` doesn't get the card embed though: https://github.com/python/cpython/issues/1 Whereas this form with hand-copied issue titles, non-obfuscated URLs you don't need to hover over to read, and - [ ] markdown checkboxes works with all issue trackers: - [ ] "Issue title" https://github.com/python/cpython/issues/1 - [x] "Issue title" https://github.com/python/cpython/issues/2
- wodenokoto 2y ago> Architectural Retrospectives differ from Architectural Reviews by focusing not on evaluating and improving the architecture itself, but on examining and improving how the team went about creating the architecture. I don't think the purpose on a retrospective on product A is to improve product A, but to improve how product B gets built.
- Quothling 2y agoIt's hilariously on point that this doesn't mention how any of this would in any way benefit the business. Don't get me wrong, I've spent my time in "architecture" to the point where I was part of the team which defined the national strategy for IT architecture in Denmark called Rammearkitekturen. I've yet to see any form of measured example where architectural work actually provided a measurable net benefit for an organisation though. In my experience it doesn't even lead to better code bases, because focusing too much on it tends to make people over complicate things to a ridiculous degree. Spending time both reviewing and retrospectiving and whatever other bloated pseudo-work terms various well paid consultants will come up with seems like a further waste of time. In my book. Disclaimer: I think architects are pseudo-jobbers who should be replaced by a competent employee who will do actual work. Even in operations I tend to think having full time architects is a gigantic waste of resources. To me, full time architects are only ever going to fill the same role HR management advisors do, which is to make bad managers feel better about the decisions they take.
- jiehong 2y agoBesides, architectures often need to change when the implementation finds assumptions that aren’t holding. The one benefit I see is: ensuring everyone follows a standard ‘blessed’ way, and contain the chaos a bit. What I dislike about most architecture people is the lack of care they tend to have to handle a gradual transition from one architecture to another. This part tends to cost much more than they care.
- rbanffy 2y ago> The one benefit I see is: ensuring everyone follows a standard ‘blessed’ way, and contain the chaos a bit. Never underestimate the ability of a couple hundred developers (and users, POs, domain experts and so on) for creating chaos. The fight is real. BTW, I was once nicknamed Dr. No.
- smokel 2y ago> I've yet to see any form of measured example where architectural work actually provided a measurable net benefit for an organisation though. These things are hard to measure, but I've seen too much of the reverse as well: over-enthusiastic developers with no feel for the customer, no understanding of the domain, and no shared vision, but perfectly happy to ruin a codebase. Especially in the field of having a shared vision, I think a good architect can do wonders. I tend to see an architect as a multiplier for success. A good one has value above 1, the experiences you shared might have resulted in a negative one. Edit: actually read the article, and boy do I agree with your sentiment now :)