Fixed up new practices

docs/practices/Deployment-And-Operations/Demand-Management.md

@@ -1,8 +1,8 @@
 ---
 title: Demand Management
-description: The practice of forecasting, planning, and managing the demand for products or services to ensure that they meet the business objectives and customer needs.
+description: The practice of forecasting, planning, and managing the demand for resources to ensure that the best use is made of them.
 tags: 
-  - Planning-Management
+  - Practice
   - Demand-Management
 featured: 
   class: c
@@ -13,19 +13,18 @@ practice:
    - "Demand Forecasting"
    - "Resource Planning"
    - "Capacity Planning"
+   - "Resource Scaling"
   mitigates:
-   - tag: Resource Risk
+   - tag: Scarcity Risk
      reason: "Helps in efficiently allocating resources to meet the demand without overburdening the team."
-   - tag: Schedule Risk
+   - tag: Deadline Risk
      reason: "Ensures that the demand is managed to meet delivery schedules."
    - tag: Market Risk
      reason: "Aligns production with market demand, reducing the risk of under or overproduction."
   attendant:
    - tag: Complexity Risk
      reason: "Forecasting and planning demand can add complexity to project management."
-   - tag: Inflexibility Risk
-     reason: "Strict demand management can limit the ability to respond to unexpected changes."
-   - tag: Accuracy Risk
+   - tag: Funding Risk
      reason: "Inaccurate demand forecasts can lead to resource misallocation."
   related:
    - ../Planning-And-Management/Prioritising

docs/practices/Planning-And-Management/Delegation.md

@@ -2,29 +2,27 @@
 title: Delegation
 description: The practice of assigning responsibility and authority to others to carry out specific activities or tasks.
 tags: 
-  - Planning-Management
+  - Practice
   - Delegation
 featured: 
   class: c
-  element: '<method imgsrc="/public/templates/risk-first/posts/delegation.svg">Delegation</method>'
+  element: '<action>Delegation</action>'
 practice:
   aka: 
    - "Task Assignment"
    - "Empowerment"
    - "Authority Delegation"
    - "Responsibility Allocation"
   mitigates:
-   - tag: Resource Risk
+   - tag: Coordination Risk
      reason: "Ensures optimal utilization of team members' skills and capabilities."
    - tag: Schedule Risk
      reason: "Distributes workload effectively, helping to meet deadlines."
-   - tag: Focus Risk
-     reason: "Allows leaders to focus on higher-priority tasks by delegating routine work."
+   - tag: Process Risk
+     reason: "Delegation can be used to stop processes getting in the way of progress."
   attendant:
-   - tag: Control Risk
+   - tag: Agency Risk
      reason: "Can lead to a loss of control over task execution and quality."
-   - tag: Accountability Risk
-     reason: "Responsibility for outcomes can become unclear, leading to accountability issues."
    - tag: Communication Risk
      reason: "Requires clear communication to ensure tasks are understood and executed properly."
   related:
@@ -38,7 +36,7 @@ practice:
 
 > "Delegation is the assignment of any responsibility or authority to another person to carry out specific activities. It is one of the core concepts of management leadership." - [Delegation, _Wikipedia_](https://en.wikipedia.org/wiki/Delegation)
 
-Delegation involves assigning responsibility and authority to others to carry out specific activities or tasks. This practice is essential for efficient management and helps in optimizing resource utilization, distributing workload, and allowing leaders to focus on higher-priority tasks. Effective delegation requires clear communication and proper accountability to ensure tasks are executed correctly and objectives are met.
+Delegation involves assigning responsibility and authority to others to carry out specific activities or tasks.  Effective delegation requires clear communication and proper accountability to ensure tasks are executed correctly and objectives are met.
 
 See:
 

docs/practices/Planning-And-Management/Meeting.md

@@ -1,12 +1,12 @@
 ---
 title: Meeting
-description: The practice of gathering team members to discuss project progress, address issues, and make decisions.
+description: "The practice of gathering team members to discuss project progress, address issues, and make decisions."
 tags: 
-  - Collaboration
-  - Communication
+  - Meeting
+  - Practice
 featured: 
   class: c
-  element: '<method imgsrc="/public/templates/risk-first/posts/meeting.svg">Meeting</method>'
+  element: '<action>Meeting</action>'
 practice:
   aka: 
    - "Team Meeting"
@@ -16,19 +16,17 @@ practice:
   mitigates:
    - tag: Communication Risk
      reason: "Facilitates clear and direct communication among team members."
-   - tag: Alignment Risk
+   - tag: Coordination Risk
      reason: "Ensures everyone is on the same page regarding project goals and progress."
-   - tag: Issue Management Risk
-     reason: "Provides a platform to identify, discuss, and resolve issues promptly."
   attendant:
-   - tag: Time Management Risk
+   - tag: Schedule Risk
      reason: "Can consume a significant amount of time if not managed effectively."
-   - tag: Participation Risk
+   - tag: Coordination Risk
      reason: "Risk of not having all relevant team members present or engaged."
-   - tag: Decision-Making Risk
+   - tag: Process Risk
      reason: "Decisions may be delayed if consensus is not reached during the meeting."
   related:
-   - ../Collaboration-And-Communication/Stakeholder-Management
+   - ../Planning-And-Management/Stakeholder-Management
    - ../Planning-And-Management/Prioritising
 ---
 
@@ -38,7 +36,7 @@ practice:
 
 > "A meeting is an assembly of people for a particular purpose, especially for formal discussion." - [Meeting, _Wikipedia_](https://en.wikipedia.org/wiki/Meeting)
 
-Meetings are essential for effective team collaboration and communication. They provide a structured environment for discussing project progress, addressing issues, making decisions, and ensuring alignment among team members. Regular meetings help in maintaining transparency and keeping everyone informed about the project's status and any changes.
+Meetings are useful for team collaboration and communication.  Regular meetings help in maintaining transparency and keeping everyone informed about the project's status and any changes.
 
 ## See Also
 

docs/practices/Planning-And-Management/Prioritising.md

@@ -12,7 +12,7 @@ practice:
    - "Roadmapping"
    - "Release Planning"
    - "Task Prioritization"
-   -  Minimum Viable Product"
+   - "Minimum Viable Product"
   mitigates:
    - tag: Schedule Risk
      reason: "Helps in focusing on high-priority tasks and meeting deadlines."

docs/practices/todo.txt

@@ -7,38 +7,20 @@
 
 
 
-3.  My Glossary of Methods / Risks - we need to generate this, rather than writing it directly.
-  - Write something to generate the glossary of risks and practices
-  - 
+3.  My Glossary of Methods / Risks - we need to generate this, rather than writing it directly.   DONE
+  - Write something to generate the glossary of risks and practices  DONE
+  - unit testing / automated testing  DONE
 
+4. DON'T WORK ON THINKING IN THIS BRANCH  DONE
+ - Consider_payoff should use "Bets" tag. DONE
+
+5. FIX LINKS AND RISK DIAGRAMS
 
-unit testing / automated testing
-
-DON'T WORK ON THINKING IN THIS BRANCH
+6. - books for each method.
+7. Variations for each practice, Pressure
 
 
 Looking for balance: 
 
 grep -R " - tag:" docs/practices | sed 's/.*://' | sort | uniq -c
 
-
-Pressure
-
-FIX LINKS AND RISK DIAGRAMS
-
-- books for each method.
-
-
-AFTER MERGE
-
-Consider_payoff should use "Bets" tag.
-
-
-New Practices Introduced While Merging Glossaries
-
-Standardisation
-Meetings
-Demand Management
-Delegation
-
-