I can tell by your word choice you want to distinguish between "the important unit" (the feature, the test, the process step) vs. the "patterns" or "descriptions of state" (de-duplication, automated, agile).
Have you ever found a simple/easy way to get an audience to see the difference between these?
I once had a Board that thought it was discussing "risk" even though it was not the asset at risk, nor the process touching that asset, nor the vulnerability identified on the process, nor even fix/control to reduce that risk... not even the process for identifying and tracking such risks... no, they wanted to evaluate the process for managing the risk process.
I wanted a short, pithy corrective like: "We need to discuss the painting but we're still discussing the frame-maker's chiseling technique."
I can tell by your word choice you want to distinguish between "the important unit" (the feature, the test, the process step) vs. the "patterns" or "descriptions of state" (de-duplication, automated, agile).
Have you ever found a simple/easy way to get an audience to see the difference between these?
I once had a Board that thought it was discussing "risk" even though it was not the asset at risk, nor the process touching that asset, nor the vulnerability identified on the process, nor even fix/control to reduce that risk... not even the process for identifying and tracking such risks... no, they wanted to evaluate the process for managing the risk process.
I wanted a short, pithy corrective like: "We need to discuss the painting but we're still discussing the frame-maker's chiseling technique."