Skip to content

Commit a8fbd1b

Browse files
committed
Fixed links
1 parent d8e5526 commit a8fbd1b

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+445
-405
lines changed

docs/ai/Start.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ tweet: yes
1212
sidebar_position: 7
1313
---
1414

15-
A risk framework addressing societal-level risks due to Artificial Intelligence (AI). This was developed for discussion in the AI Risks chapter of the [Risk-First Software Development](/books/Risk-First-Second-Edition) book.
15+
A risk framework addressing societal-level risks due to Artificial Intelligence (AI). This was developed for discussion in the AI Risks chapter of the [Risk-First Software Development](/Risk-First-Second-Edition) book.
1616

1717
If you want a much more comprehensive view of what is going on in the world of risk management for AI, please take a look at the [MIT AI Risks Database](https://airisk.mit.edu) which covers hundreds of different AI Risk Frameworks. One of the reasons for such proliferation is that there are many different domains that are impacted by AI.
1818

docs/ai/_category_.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
position: 10
2-
label: 'AI Risk'
2+
label: 'AI'
33
link:
44
type: doc
55
id: Start

docs/methods/Start.md

Lines changed: 19 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Software Development Risk Frameworks
3-
description: Some rough groupings of practices by development method.
2+
title: Risk Framework
3+
description: A description of the Risk Framework concept and a list of Risk Frameworks mapped by Risk-First.
44

55
featured:
66
class: c
@@ -10,12 +10,27 @@ cat: Complexity
1010
tags:
1111
- Front
1212
- Read All About It
13+
- Risk Framework
1314
sidebar_position: 5
1415
tweet: yes
1516
---
1617

17-
This is a categorisation of practice by risk framework (or methodology).
18+
# Software Development Risk Frameworks
1819

19-
Consider this to be incomplete but may be useful to get a sense of which risks different risk frameworks focus on.
20+
A **Risk Framework** is a structured way of identifying, categorising, and addressing risks within a domain. It typically combines a breakdown of risks with recommended actions to manage them.
21+
22+
![Risk Framework](/img/generated/introduction/risk_framework_2.svg)
23+
24+
As the diagram shows, a risk framework employs **practices** (actions you can take) that address **risks** which obstruct your **goals**. The framework's value lies in having already identified which risks matter and which practices are effective against them.
25+
26+
Software methodologies like Scrum, XP, Lean, and DevOps are all risk frameworks. Each one prescribes a particular process—a set of actions to take—which is really a particular approach to managing risks on software projects.
27+
28+
**Pattern languages**—like the famous [Design Patterns](https://en.wikipedia.org/wiki/Design_Patterns) book—are also risk frameworks. They describe common problems, the risks involved, and proven solutions. The [TVTropes](https://tvtropes.org) website is a pattern language for fiction. [MITRE ATT&CK](https://attack.mitre.org/) is a pattern language for cybersecurity threats.
29+
30+
## Mapping a Framework
31+
32+
There's value in adopting a framework: it reduces cognitive load and provides battle-tested practices. But it's critical to match the framework to your project's risk profile. A framework that works well for a startup may be wrong for a regulated industry; one that suits web development may fail for embedded systems.
33+
34+
The frameworks below are mapped by the risks they address and the practices they recommend.
2035

2136
<TagList tag="Risk Framework" />
Lines changed: 21 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,47 +1,43 @@
11
---
22
title: Prototyping
33
description: Creating early models of the software to test concepts and ideas.
4-
tags:
4+
tags:
55
- Prototyping
66
- Practice
7-
featured:
7+
featured:
88
class: c
9-
element: '<action>Prototype</action>'
9+
element: "<action>Prototype</action>"
1010
practice:
11-
aka:
12-
- "Mockups"
13-
- "Pilot Models"
14-
- "Early Models"
11+
aka:
12+
- "Mockups"
13+
- "Pilot Models"
14+
- "Early Models"
1515
mitigates:
16-
- tag: Feature Fit Risk
17-
reason: "Allows early validation of features and design with stakeholders."
18-
- tag: Communication Risk
19-
reason: "Facilitates clear communication of concepts and requirements."
20-
- tag: Implementation Risk
21-
reason: "Helps identify potential issues before full-scale development."
16+
- tag: Feature Fit Risk
17+
reason: "Allows early validation of features and design with stakeholders."
18+
- tag: Communication Risk
19+
reason: "Facilitates clear communication of concepts and requirements."
20+
- tag: Implementation Risk
21+
reason: "Helps identify potential issues before full-scale development."
2222
attendant:
23-
- tag: Schedule Risk
24-
reason: "Prototyping can be time-consuming and delay the project timeline."
25-
- tag: Funding Risk
26-
reason: "Creating prototypes can incur additional costs."
23+
- tag: Schedule Risk
24+
reason: "Prototyping can be time-consuming and delay the project timeline."
25+
- tag: Funding Risk
26+
reason: "Creating prototypes can incur additional costs."
2727
related:
28-
- ../Testing-and-Quality-Assurance/User-Acceptance-Testing-(UAT)
29-
- ../Communication-and-Collaboration/Demo
30-
- ../Planning-And-Management/Prioritising
28+
- ../Testing-and-Quality-Assurance/User-Acceptance-Testing-(UAT)
29+
- ../Communication-and-Collaboration/Demo
30+
- ../Planning-And-Management/Prioritising
3131
---
3232

33-
<PracticeIntro details={frontMatter} />
33+
<PracticeIntro details={frontMatter} />
3434

3535
## Description
3636

3737
> "Prototyping is an iterative, trial-and-error method of system development in which requirements are converted to a working system that is continually revised through close work between an analyst and user until the latter is satisfied that an acceptable system has been developed." - [Prototyping, _Wikipedia_](https://en.wikipedia.org/wiki/Prototyping)
3838
3939
Prototyping in software development involves creating early models or mockups of the software to test concepts and gather feedback. This practice helps in validating design choices, identifying potential issues, and ensuring that the final product meets the users' needs and expectations.
4040

41-
See:
42-
- [Spike Solution (Coding Bets)](/bets/Coding-Bets#spike-solutions-a-new-technology-bet)
43-
44-
4541
## See Also
4642

4743
<TagList tag="Prototyping" />
Lines changed: 23 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,47 +1,45 @@
11
---
22
title: Estimating
33
description: Estimating the time and resources needed for tasks.
4-
tags:
4+
tags:
55
- Practice
66
- Estimating
7-
featured:
7+
featured:
88
class: c
9-
element: '<action>Estimate</action>'
9+
element: "<action>Estimate</action>"
1010
practice:
11-
aka:
12-
- "Forecasting"
13-
- "Budgeting"
14-
- "Effort Estimation"
11+
aka:
12+
- "Forecasting"
13+
- "Budgeting"
14+
- "Effort Estimation"
1515
mitigates:
16-
- tag: Deadline Risk
17-
reason: "Provides realistic timelines helps hit important deadlines."
18-
- tag: Funding Risk
19-
reason: "Accurate estimation helps in securing and managing funding."
20-
- tag: Agency Risk
21-
reason: "Helps in planning and managing staff usage effectively."
16+
- tag: Deadline Risk
17+
reason: "Provides realistic timelines helps hit important deadlines."
18+
- tag: Funding Risk
19+
reason: "Accurate estimation helps in securing and managing funding."
20+
- tag: Agency Risk
21+
reason: "Helps in planning and managing staff usage effectively."
2222
attendant:
23-
- tag: Schedule Risk
24-
reason: "Inaccurate estimates can lead to schedule overruns."
25-
- tag: Deadline Risk
26-
reason: "Can create dependencies on estimated timelines and resources."
27-
- tag: Agency Risk
28-
reason: "Can put unnecessary pressure on staff to hit deadlines."
23+
- tag: Schedule Risk
24+
reason: "Inaccurate estimates can lead to schedule overruns."
25+
- tag: Deadline Risk
26+
reason: "Can create dependencies on estimated timelines and resources."
27+
- tag: Agency Risk
28+
reason: "Can put unnecessary pressure on staff to hit deadlines."
2929
related:
30-
- ../Planning-and-Management/Prioritising
31-
- ../Communication-and-Collaboration/Documentation
32-
- ../Development-and-Coding/Coding
30+
- ../Planning-and-Management/Prioritising
31+
- ../Communication-and-Collaboration/Documentation
32+
- ../Development-and-Coding/Coding
3333
---
3434

35-
<PracticeIntro details={frontMatter} />
35+
<PracticeIntro details={frontMatter} />
3636

3737
## Description
3838

3939
> "Estimation is the process of finding an estimate, or approximation, which is a value that can be used for some purpose even if input data may be incomplete, uncertain, or unstable." - [Estimation, _Wikipedia_](https://en.wikipedia.org/wiki/Estimation)
4040
4141
Estimation in software development involves predicting the time, effort, and resources needed to complete tasks or projects. Accurate estimation is crucial for planning, budgeting, and managing the development process, helping to set realistic expectations and reduce the risk of overruns.
4242

43-
See the Risk-First section on [Estimating](/estimating/Start) for a thorough breakdown of this topic.
44-
4543
## See Also
4644

4745
<TagList tag="Estimation" />
Lines changed: 16 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,45 @@
11
---
22
title: Dependency Risks
3-
description: Risk faced by depending on something else, e.g. an event, process, person, piece of software or an organisation.
3+
description: Risk faced by depending on something else, e.g. an event, process, person, piece of software or an organisation.
44

5-
featured:
5+
featured:
66
class: c
77
element: '<risk class="dependency" />'
88
sidebar_position: 6
99
tags:
10-
- Dependency Risks
10+
- Dependency Risks
11+
- Risk Category
1112
tweet: yes
1213
slug: /risks/Dependency-Risks
1314
part_of: Operational Risk
1415
---
1516

1617
# Dependency Risks
1718

18-
[Dependency Risks](/tags/Dependency-Risks) are risks you take on whenever you have a dependency on something (or someone) else.
19+
[Dependency Risks](/tags/Dependency-Risks) are risks you take on whenever you have a dependency on something (or someone) else.
1920

20-
One simple example could be that the software service you write might depend on hardware to run on: if the server goes down, the service goes down too. In turn, the server depends on electricity from a supplier, as well as a network connection from a provider. If either of these dependencies aren't met, the service is out of commission.
21+
One simple example could be that the software service you write might depend on hardware to run on: if the server goes down, the service goes down too. In turn, the server depends on electricity from a supplier, as well as a network connection from a provider. If either of these dependencies aren't met, the service is out of commission.
2122

22-
Dependencies can be on _events_, _people_, _teams_, _work_, _processes_, _software_, _services_, _money_ and pretty much _any resource_, and while every project will need some of these, they also _add risk_ to any project because the reliability of the project itself is now a function involving the reliability of the dependency.
23+
Dependencies can be on _events_, _people_, _teams_, _work_, _processes_, _software_, _services_, _money_ and pretty much _any resource_, and while every project will need some of these, they also _add risk_ to any project because the reliability of the project itself is now a function involving the reliability of the dependency.
2324

2425
## Why Have Dependencies?
2526

26-
Luckily for us, the things we depend on in life are, for the most part, abundant: water to drink, air to breathe, light, heat and most of the time, food for energy.
27+
Luckily for us, the things we depend on in life are, for the most part, abundant: water to drink, air to breathe, light, heat and most of the time, food for energy.
2728

28-
This isn't even lucky though: life has adapted to build dependencies on things that it can _rely_ on.
29+
This isn't even lucky though: life has adapted to build dependencies on things that it can _rely_ on.
2930

30-
Although life exists at the bottom of the ocean around [hydrothermal vents](https://en.wikipedia.org/wiki/Hydrothermal_vent), it is a very different kind of life to ours and has a different set of dependencies given its circumstances.
31+
Although life exists at the bottom of the ocean around [hydrothermal vents](https://en.wikipedia.org/wiki/Hydrothermal_vent), it is a very different kind of life to ours and has a different set of dependencies given its circumstances.
3132

3233
This tells us a lot about [Dependency Risk](/tags/Dependency-Risks) right here:
3334

34-
- On the one hand, _depending on something_ is very often helpful, and quite often essential. (For example, all life seem to depend on water).
35-
- Successful organisms _adapt_ to the dependencies available to them (like the thermal vent creatures).
36-
- However, as soon as you have dependencies, you need to take into account their _reliability_. (Living near a river or stream gives you access to fresh water, for example).
37-
So, dependencies are a trade-off. They give with one hand and take with the other. Our modern lives are full of dependency (just think of the chains of dependency needed for putting a packet of biscuits on a supermarket shelf, for example), but we accept this risk because it makes life _easier_.
38-
- There is likely to be _competition_ for a dependency when it is scarce (think of droughts and famine).
39-
35+
- On the one hand, _depending on something_ is very often helpful, and quite often essential. (For example, all life seem to depend on water).
36+
- Successful organisms _adapt_ to the dependencies available to them (like the thermal vent creatures).
37+
- However, as soon as you have dependencies, you need to take into account their _reliability_. (Living near a river or stream gives you access to fresh water, for example).
38+
So, dependencies are a trade-off. They give with one hand and take with the other. Our modern lives are full of dependency (just think of the chains of dependency needed for putting a packet of biscuits on a supermarket shelf, for example), but we accept this risk because it makes life _easier_.
39+
- There is likely to be _competition_ for a dependency when it is scarce (think of droughts and famine).
4040

4141
## Types Of Dependency Risk
4242

4343
In order to avoid repetition, and also to break down this large topic, we're going to look break this down into some specific sub-types (shown below).
4444

45-
<TagList tag="Dependency Risks" />
46-
47-
48-
45+
<TagList tag="Dependency Risks" />

0 commit comments

Comments
 (0)