3 ms·
This is something I’ve long struggled with: how you capture assumptions tied to decisions so you can revisit the decisions when the facts on the ground change.
by macintux 3y ago
This is something I’ve long struggled with: how you capture assumptions tied to decisions so you can revisit the decisions when the facts on the ground change.
- tuukkah 3y ago(Architectural) Decision Records should explicate assumptions behind the decisions. There will be implicit assumptions too, but at least you can later go back to the records and analyse what was implicit in them.
- sho_hn 3y agoYup, we have a strong culture around this at work. Problem statement, decision drivers, decision criteria, alternate options to seriously evaluate. It should be clear why one is recommended over the other, and under what circumstances other options might be preferable.
- latchkey 3y agoNeat, how is all of this tracked?
- svilen_dobrev 3y agorequirements traceability - dependency tracking/tracing graph, upwards (because of) and downwards (therefore). It is a very tedious process, Very few companies do it. But once the graph is built, one can poke questions on it, like what would/might be affected if node X changes. And any assumptions also counts as requirement of sorts https://en.wikipedia.org/wiki/Requirements_traceability https://en.wikipedia.org/wiki/Requirements_traceability
- latchkey 3y agoWhat tools specifically? Just excel?