# Errata for Risk-First Software Development, Second Edition B2.0

**URL:** <https://forum.devtalk.com/t/errata-for-risk-first-software-development-second-edition-b2-0/222586>\
**Category:** PragProg Customers\
**Tags:** book-risk-first-software-development-second-edition, errata\
**Created:** [13 November 2025 22:30 UTC](https://forum.devtalk.com/t/errata-for-risk-first-software-development-second-edition-b2-0/222586 "2025-11-13T22:30:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ASchaetti](https://forum.devtalk.com/user_avatar/forum.devtalk.com/aschaetti/32/7783_2.png) [@ASchaetti](https://forum.devtalk.com/u/ASchaetti)\
**Post date:** [13 November 2025 22:30 UTC](https://forum.devtalk.com/t/errata-for-risk-first-software-development-second-edition-b2-0/222586/1 "2025-11-13T22:30:49Z")

</div>

Thanks for letting me review this book. I’ve noticed the following errata while reading the book (PDF version B2.0):

- Page 35

- Page 54, last paragraph: as shown **in** below → as shown below _or_ as shown in **the figure** below _or_ as shown in **Figure 4.3** below

- Page 60, 1st paragraph: rather than **in** let it surface → rather than let it surface

- Page 62, missing beginning of sentence: […] _the same actions Waterfall prescribes_

- Page 65, paragraph starting with _The Gamma et al._: try and **and** explain → try and explain

- Page 66, 1st bullet point: and the **the** risks of → and the risks of

- Page 98, quotation in section _Risk Answer_: risk appetite **and risk appetite**. → risk appetite.

- Page 109, 1st bullet point in section _Example: The Financial Crisis_: fix wording: the risk that the **amount some asset** is going to change in value

- Page 110, last paragraph: financial services still **uses** the categories → financial services still **use** the categories

- Page 116, threat _Over-Complication_: **as much** as many → as many

- Page 129

- Page 130, threat _Safety_: resulting in **you** under-billing → resulting in **your** under-billing

- Page 138, 2nd bullet point: missing second part of sentence: “The bus to work leaves at 7:30am” or […]

- Page 141, threat _Upstream Dependencies_: remove or put in parentheses: The less reliable **Reliability Risk** your dependencies are…

- Page 142, 1st paragraph: won’t **be get** → won’t be **getting** _or_ wont’ **get**

- Page 144, 1st paragraph: **reduced** costs → **reduce** costs

- Page 145

- Page 150

- Page 165, section _Practices Addressing Communication Risk_: while stakeholder management **or** ensures → while stakeholder management ensures

- Page 177

- Page 189, 2nd bullet point of threat _Hardware Supply Chain Threats_: in **a** network routers → in network routers

- Page 193, section _Anecdote Corner_: **the its** use of the Java APIs → its use of the Java APIs _or_ the use of the Java APIs

- Page 200, section _Anecdote Corner_: risk management failures\*\*,\*\* → risk management failures\*\*.\*\*

- Page 208, Faceook → Facebook

- Page 216, 1st paragraph of section _The Longer Term: Future Risks For AI Integrators_: close parentheses after _and so on_.

- Page 229, 2nd paragraph: take other side → take **the** other side

- Page 230, This is **the** just the first example → This is just the first example

- Page 240, 4th paragraph: tends to be **the** even more ephemeral → tends to be even more ephemeral

- Page 244, 1st paragraph: to be able to **effective** triage risk → to be able to **effectively** triage risk

In addition, generally in the ePub version, the figure captions contain two labels: one with a continuous index and one with a per-chapter index, e.g. _Figure 28. Figure 5.2._

Kind regards,  
Andreas