Removed Feature-Drift risk

risk-first · Jan 11, 2025 · 9d79363 · 9d79363
1 parent 6b9ce09
commit 9d79363
Show file tree

Hide file tree

Showing 5 changed files with 3 additions and 7 deletions.
diff --git a/docs/practices/External-Relations/Marketing.md b/docs/practices/External-Relations/Marketing.md
@@ -15,8 +15,6 @@ practice:
   mitigates:
    - tag: Market Risk
      reason: "Promotes the software to reach potential customers and increase market share."
-   - tag: Feature Drift Risk
-     reason: "Make the most of market opportunities while they exist."
    - tag: Communication Risk
      reason: "Facilitates communication of the product's value proposition to the target audience."
   attendant:

diff --git a/docs/practices/Planning-And-Management/Requirements-Capture.md b/docs/practices/Planning-And-Management/Requirements-Capture.md
@@ -20,8 +20,6 @@ practice:
    - tag: Communication Risk
      reason: "Helps in explaining exactly what should be built."
   attendant:
-   - tag: Feature Drift Risk
-     reason: "Requirements will evolve and this can lead to feature drift."
    - tag: Schedule Risk
      reason: "Thorough requirements capture can be time-consuming."
   related:

diff --git a/docs/risks/Environmental-Risks/Operational-Risk/Operations-Management.md b/docs/risks/Environmental-Risks/Operational-Risk/Operations-Management.md
@@ -64,7 +64,7 @@ As the diagram above shows, we can bring [Planning](#planning) to bear on depend
 
 ![Design and Change Activities](/img/generated/risks/operational/design-change.svg)
 
-Since our operation exists in a world of risks like [Red Queen Risk](/tags/Red-Queen-Risk) and [Feature Drift Risk](/tags/Feature-Drift-Risk), we would expect that the output of our [Planning](#planning) actions would result in changes to our operation.  
+Since our operation exists in a world of risks like [Red Queen Risk](/tags/Red-Queen-Risk) and [Market Risk](/tags/Market-Risk), we would expect that the output of our [Planning](#planning) actions would result in changes to our operation.  
 
 While _planning_ is a day-to-day operational feedback loop, _design_ is a longer feedback loop changing not just the parameters of the operation, but the operation itself.
 

diff --git a/docs/risks/Internal-Model-Risk/Internal-Model-Risk.md b/docs/risks/Internal-Model-Risk/Internal-Model-Risk.md
@@ -24,7 +24,7 @@ So there is a translation going on here: observations about the arrangement of _
 
 ## Worked Example
 
-![Feature Drift Risk](/img/generated/risks/posters/internal-model-risk.svg) 
+![Internal Model Risk](/img/generated/risks/posters/internal-model-risk.svg) 
 
 A large software firm struggles to hire effectively and feels it uses a lot of cycles trying to lure the best candidates.
 

diff --git a/docs/risks/Staging-And-Classifying.md b/docs/risks/Staging-And-Classifying.md
@@ -43,7 +43,7 @@ As shown in the above diagram, _using an abstraction you already know_ means:
  - **Mitigating [Feature Risk](/tags/Feature-Risk)**: because the abstraction is providing you with something _useful_.  For example, using the word "London" allows you to refer to a whole (but slightly non-specific) geographic area.
  - **Accepting [Communication Risk](/tags/Communication-Risk)**: because if you are using the abstraction in conversation the people you are using it with _need to understand it too_.
  - **Accepting [Map and Territory Risk](/tags/Map-And-Territory-Risk)**: because the abstraction is a simplification and not the actual thing itself.
- - **Living with [Dependency Risks](/tags/Dependency-Risks)**:  we depend on a word in our language (or a function in our library, or a service on the Internet).  But words are [unreliable](/tags/Reliability-Risk).  Language _changes_ and _evolves_, and the words you are using now might not always mean what you want them to mean.  (Software too changes and evolves:  We've seen this in [Red Queen Risk](/tags/Red-Queen-Risk) and [Feature Drift Risk](/tags/Feature-Drift-Risk).)
+ - **Living with [Dependency Risks](/tags/Dependency-Risks)**:  we depend on a word in our language (or a function in our library, or a service on the Internet).  But words are [unreliable](/tags/Reliability-Risk).  Language _changes_ and _evolves_, and the words you are using now might not always mean what you want them to mean.  (Software too changes and evolves:  We've seen this in [Red Queen Risk](/tags/Red-Queen-Risk) and [Market Risk](/tags/Market-Risk).)
 
 ### Inventing A New Abstraction