Added Second Edition Page

risk-first · Apr 19, 2024 · 2aa6e33 · 2aa6e33
1 parent c7f5995
commit 2aa6e33
Show file tree

Hide file tree

Showing 13 changed files with 86 additions and 17 deletions.
diff --git a/dictionary.txt b/dictionary.txt
@@ -324,3 +324,5 @@ outreach
 lifecycle
 accrual
 dietary
+derisking
+fraudulent
diff --git a/docs/Risk-First-Second-Edition.md b/docs/Risk-First-Second-Edition.md
@@ -0,0 +1,44 @@
+---
+title: 'Book: Risk-First Second Edition'
+description: "Risk-First Software Development Second Edition Coming Soon!"
+url: https://riskfirst.org/The-Menagerie
+
+featured: 
+  class: bg1
+  element: '<big-image imgsrc="/public/templates/risk-first/posts/book-grey.png" />'
+tags: 
+ - Front
+sidebar_position: 3
+---
+
+# Coming in 2024
+
+## Risk-First Software Development Second Edition
+
+**Over 20 years ago an "Agile" revolution occurred** in the software development field.  But 20 years later, the very same proponents of the revolution are turning their backs on what they created, arguing that their ideals have been corrupted by zealotry, proscriptive norms, cargo-culting and an "Agile-Industrial Complex" focused on evangelism and certification.
+
+**Risk-First attempts something new:**   to "peel back the onion" and provide a language for understanding and evaluating not just Agile practices but *all practices* in software development.  Unlike the Agile of today, Risk-First is not a methodology telling you what to do, but a toolbox and a pattern language to help you figure out what you should do, and help you communicate with others to make your case.
+
+The book aims to develop a **Pattern Language for understanding software risk**, and develop a practical framework for discussing how the activities we take on a project change the balance of the risks we are exposed to.
+
+## How Can I Get Involved?
+
+### Get Updates
+
+<BoxOut title="Join The Risk-First GitHub Organisation" image="/img/github.png">
+
+If you [Add Your Star on GitHub](https://github.com/risk-first/website) you'll be sent an email invite to join the [Risk-First GitHub Organisation](https://github.com/risk-first/website/discussions) and the associated discussion group!
+
+This is where I will be adding blog materials discussing the content of the new book as it comes together, as well as providing access for beta testers.   
+
+[![GitHub Star](/img/github_star.png) <br /> ☝️ Click This On GitHub ](https://github.com/risk-first/website)
+
+</BoxOut>
+
+### Pre-Order
+
+**Coming Soon!**
+
+### Read It Here
+
+Most of the material in the second edition book is published here on this website, so you can simply [start reading](overview/Start.md).  If you have any feedback, please get in touch.  
diff --git a/docs/The-Menagerie.md b/docs/The-Menagerie.md
@@ -6,8 +6,6 @@ url: https://riskfirst.org/The-Menagerie
 featured: 
   class: bg1
   element: '<big-image imgsrc="/public/templates/risk-first/posts/book-grey.png" />'
-tags: 
- - Front
 sidebar_position: 3
 ---
 

diff --git a/docs/thinking/De-Risking.md b/docs/thinking/De-Risking.md
@@ -1,5 +1,5 @@
 ---
-title: De-Risking
+title: Derisking
 description: What can you do with the risks on a software project?
 url: https://riskfirst.org/thinking/De-Risking
 
@@ -17,24 +17,36 @@ redirect_from:
 tweet: yes
 ---
 
-# De-Risking
+# Derisking
 
-> "To take steps to make (something) less risky or less likely to involve a financial loss." - [De-Risk, _OxfordDictionaries.com_](https://en.oxforddictionaries.com/definition/de-risk)
+In this section, we're going to more closely at [Taking Action](Glossary.md#taking-action) and separate out the ways in which this can be done.   Along the way, I'll introduce the correct risk management terms and we'll see how each of these apply to software development.
 
-Some simple examples of this might be:
+So far in Risk-First, we've talked about [Taking Action](Glossary.md#taking-action) as having two effects:
 
-- **Safety-nets and ropes** de-risk climbing.  But, the activity of climbing itself is otherwise much unchanged.
-- **Backups and Source-Control** de-risk the development process by reducing the impact of computer failure.  Our process is changed _slightly_ by this imposition but we're not massively inconvenienced.
-- **Insurance** de-risks owning a house, going on holiday or driving a car.  Usually, the payment is small enough not to impact us too much.
-- **The National Health Service (NHS)** de-risks medical expense by pooling health-care costs across the entire population.  If you were struck down with a debilitating illness, then at least you wouldn't also have to pay to get better. 
+ 1. It's the way in which we [Meet Reality](Glossary.md#meet-reality) to learn about the world and uncover [Hidden Risks](Glossary.md#hidden-risk).
+ 2. It's the way we change our position on the [Risk Landscape](Glossary.md#risk-landscape) via actions with a positive [Payoff](Glossary.md#payoff).
+
+So the concept of [Taking Action](Glossary.md#taking-action) is doing a lot of heavy lifting.  This second effect is also called [De-Risking](Glossary.md#de-risk):
+
+> "To remove the risk from; to make safe. " - [Derisk, _Wiktionary_](https://en.wiktionary.org/wiki/derisk)
+
+Let's look at some common strategies for derisking.
+
+## Mitigate (or Reduce)
 
-Let's look at some common strategies for De-Risking.
+**Mitigating** risk is taking steps towards minimising the **impact** (as we discussed in the [Evaluating Risk](Evaluating-Risk.md) section) of a risk arising.  
 
-## Mitigate
+> "To reduce, lessen, or decrease and thereby to make less severe or easier to bear." - [Mitigate, _Wiktionary_](https://en.wiktionary.org/wiki/mitigate) 
 
-**Mitigating** risk is taking steps towards minimising either its likelihood or impact (as we discussed in the [Evaluating Risk](Evaluating-Risk.md) section).  
+Some simple examples of this might be:
+
+- **Safety-nets and ropes** mitigates some of the risks of climbing.  The fall damage you'll take when you lose your grip is hopefully much reduced but the activity of climbing itself is otherwise much unchanged.  
+
+- **Backups and Source-Control** mitigates the impact of computer failure.  Hardware _still fails_ but the impact is less if we can restore from a recent backup.  Our process is changed _slightly_ by this imposition but we're not massively inconvenienced.
 
-Safety-nets, for example, mitigate the impact of hitting the ground.  
+- **Insurance** de-risks owning a house, going on holiday or driving a car.  Usually, the payment is small enough not to impact us too much.
+
+- **The National Health Service (NHS)** de-risks medical expense by pooling health-care costs across the entire population.  If you were struck down with a debilitating illness, then at least you wouldn't also have to pay to get better. 
 
 ## Avoid
 
@@ -44,7 +56,7 @@ For example, if you are working in a team which has no experience of relational
 
 _Not_ launching an online service _avoids_ the [Operational Risk](../risks/Operational-Risk.md) involved in running one.  Although you avoid the upsides too.
 
-## Transfer
+## Transfer (sometimes Share)
 
 **Transferring** risk means _making it someone else's problem_.  
 

diff --git a/docs/thinking/Glossary.md b/docs/thinking/Glossary.md
@@ -40,6 +40,10 @@ Taking a decision to move somewhere new on the [Risk Landscape](#risk-landscape)
 
 _See: [Bets (Tag)](/tags/bets)_
 
+### De-Risk
+
+To [Take Action](#taking-action) to make (something) less risky.
+
 ### Feedback Loop
 
 The process of testing an [Internal Model](#internal-model), through [taking action](#taking-action) to [Meet Reality](#meet-reality).  Typically, we talk about short or long feedback loops, depending on the intervals between [Meeting Reality](#meet-reality).  

diff --git a/docs/thinking/Track-Risk.md b/docs/thinking/Track-Risk.md
@@ -108,6 +108,8 @@ Going back to the dinner party example, the above diagram considers solutions to
 
 If I added actions for all the other risks (maybe buying extra snacks, checking the guest's dietary restrictions etc) then this chart gets quite busy.  But clearly, actions to the top and left are the ones we should consider taking, since they have the best payoff.   Those below and to the right of the diagonal line are non-starters as they make our situation worse.
 
+_Really good design_ would be coming up with a course of action that takes care of _multiple risks at the same time_ and creating a really good payoff. 
+
 ## Criticism
 
 One of the criticisms of the [Risk Register](Track-Risk.md#risk-registers) approach is that of [mistaking the map for the territory](../risks/Map-And-Territory-Risk.md).  That is, mistakenly believing that what's on the Risk Register _is all there is_.  

diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -75,8 +75,15 @@ const config = {
 	themeConfig:
 		/** @type {import('@docusaurus/preset-classic').ThemeConfig} */
 		({
-			// Replace with your project's social card
-			image: 'img/docusaurus-social-card.jpg',
+		announcementBar: {
+		      id: 'support_us',
+		      content:
+		        'Risk-First Software Development Second Edition - Coming Soon! <a target="_blank" rel="noopener noreferrer" href="/Risk-First-Second-Edition">Click here for details</a>',
+		      backgroundColor: 'rgb(245, 62,121)',
+		      textColor: '#ffffff',
+		      isCloseable: true,
+		    },	
+			image: 'img/generated/titles/index.png',
 			metadata: [
 				{ name: 'msvalidate.01', content: "3D19A6D7C17D82567867CF4238511ED1" }
 			],

diff --git a/static/img/generated/introduction/cadence.pdf b/static/img/generated/introduction/cadence.pdf
diff --git a/static/img/generated/introduction/hidden_risks.pdf b/static/img/generated/introduction/hidden_risks.pdf
diff --git a/static/img/generated/single/Risk-First-Second-Edition.png b/static/img/generated/single/Risk-First-Second-Edition.png
diff --git a/static/img/generated/titles/Risk-First-Second-Edition.png b/static/img/generated/titles/Risk-First-Second-Edition.png
diff --git a/static/img/github.png b/static/img/github.png
diff --git a/static/img/github_star.png b/static/img/github_star.png