Removed Feature Access Risk

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

Hide file tree

Showing 4 changed files with 4 additions and 6 deletions.
diff --git a/docs/practices/Deployment-And-Operations/Release.md b/docs/practices/Deployment-And-Operations/Release.md
@@ -14,8 +14,6 @@ practice:
    - "Launch"
    - "Publication"
   mitigates:
-   - tag: Feature Access Risk
-     reason: Users are able to access the features you release to them.
    - tag: Feature Fit Risk
      reason: Putting new features in the hands of users can make your product fit their needs better.
    - tag: Market Risk

diff --git a/docs/practices/Testing-and-Quality-Assurance/Measurement.md b/docs/practices/Testing-and-Quality-Assurance/Measurement.md
@@ -15,7 +15,7 @@ practice:
   mitigates:
    - tag: Operational Risk
      reason: "Provides data to inform decision-making and improve operational efficiency."
-   - tag: Feature Access Risk
+   - tag: Feature Fit Risk
      reason: "Helps in understanding the use of the system."
    - tag: Implementation Risk
      reason: "Identifies areas of improvement in the implementation process."

diff --git a/docs/practices/Testing-and-Quality-Assurance/Performance-Testing.md b/docs/practices/Testing-and-Quality-Assurance/Performance-Testing.md
@@ -13,8 +13,8 @@ practice:
    - "Stress Testing"
    - "Performance Benchmarking"
   mitigates:
-   - tag: Feature Access Risk
-     reason: "Identifies performance bottlenecks that could impact operations."
+   - tag: Feature Fit Risk
+     reason: "Identifies performance bottlenecks that could affect usefulness."
    - tag: Reliability Risk
      reason: "Performance testing software can establish bounds on its reliability."
   attendant:

diff --git a/docs/risks/Staging-And-Classifying.md b/docs/risks/Staging-And-Classifying.md
@@ -72,7 +72,7 @@ Abstraction is everywhere and seems to be at the heart of what our brains do.  B
 
 ![Features And Dependencies](/img/generated/staging-and-classifying/features-and-dependencies.svg)
 
-In the [Feature Risk](/tags/Feature-Risk) section, we looked at the problems of _supplying something for a client to use as a dependency_:  you've got to satisfy a demand ([Market Risk](/tags/Market-Risk)) and service a segment of the user community ([Feature Access Risk](/tags/Feature-Access-Risk)).    
+In the [Feature Risks](/tags/Feature-Risks) section, we looked at the problems of _supplying something for a client to use as a dependency_:  you've got to satisfy a demand ([Market Risk](/tags/Market-Risk)) and service a segment of the user community ([Feature Fit Risk](/tags/Feature-Fit-Risk)).    
 
 However over the rest of the [Dependency Risk](/tags/Dependency-Risks) sections we looked at this from the point of view of _being a client of someone else_:  you want to find trustworthy, reliable dependencies that don't give up when you least want them to.