Book Errata

We’re not perfect. We’re getting feedback from people about our books, in particularly our new one, Choose Your WoW!, and they’re finding a few bugs in it. So we’re fixing them. This page tracks the errors that we’re finding and when they’re being addressed.

Choose Your WoW!

Fix Release
Book should have a version number on the ISBN page v1.0.1
Chapter 20 – Title should be “Ensure Production Readiness” not “Ensure Deployment Readiness” v1.0.1
Figure 5.4 (goal diagram for Explore Scope) – Explore Quality Requirements decision point was mislabelled as Explore General Requirements v1.0.1
Figure 9.1 (goal diagram for Explore Scope) – Explore Quality Requirements decision point was mislabelled as Explore General Requirements pending

Vi – Although there some great agile coaches – “are” missing

Vi – 7 to 12 percent improves on – replace “improves” with “improvements”

Vii – you that are focused to Construction of a – replace “to” with “on”

5 – about that strategy that would could refer – “would” unnecessary

13 – In Figure 1.7, you see the – should be Figure 1.8

16 (Cartoon) – DAD Guidence Helps Us Choose – spelling mistake

19 – A process tailoring workshop is likely to address a several important – “a” unnecessary

21 – to guide how initially choose your WoW – “to” missing

29 – we would have more deterministic and have predictable outcomes. – “approaches” or a similar word missing after deterministic

31 – following Guided Continuous Improvement strategy – “a” missing

32 – for evolving your organizations overall vision – organization’s

32 – work in a transparent manner although expect reciprocity from others. – expecting

36 – Predictably new generation – “a” missing

37 – pushback against the prescriptive agile scaling framework that – should be plural

39 – it is necessary to Treat everyone with – “Treat” should be lowercase

41 – DAD does the “process heavy lifting” that – “heavy process”

48 – what we need to delivery is something that is – “deliver” not “delivery”

49 – Daily Standup – For the Scrum column, the Coordination meeting should be called a “Daily Scrum” (as per the Scrum Guide)

50 – The further out on the each scale – “the” unnecessary

53 – You may have valid reasons tailoring the roles – “for” missing

53 – information and decisions in timely manner – “a” missing

63 – lest a bunch of Scrum alliance people – “alliance” should be “Alliance”

64 – These have always been teams – “These” should be “There”

65 – we don’t need PMs or BAs is short-sited – spelling mistake

66 – You may have valid reasons tailoring the roles – “for” missing

67 – process goals define high level process outcome – outcome should be plural

67 – process goals guides teams through – guides should be singular

72 – Figure 5.4 has two decision points named “Explore General Requirements” – the second one should be changed to “Explore Quality Requirements”

73 – The Explore Scope process goal described in greater – missing “is” between “goal” and “described”

74 – Explicit List. Enables us to… – there is an extra period (“.”) at the end of the description for the option in Table 5.1.

77 – we get to observe that is actually – should be “what”

77 – may be working on brand-new business idea and are – ideas

77 – Note that some or organizations in the early 1990s – redundant “or”

77 – RUP is a traditional process too – No, it’s – replace the hyphen with a period.

82 – lifecycle will work in very sort iterations, typically – should be “short”

82 – Team following this lifecycles, based on Lean – should be “Teams” and “lifecycle”

84 – Also like Scrum, this lifecycle schedules several of agile – redundant “of”

86 – when they pull it into to be worked on – “into” what?

88 – paying down technical, in particular writing – the word “debt” is missing

91 – then we observe and measure how the work with the MVP(s). – should be “they”

93 – ensuring the each team is doing – should be “that”

94 – the Team Leads will self-organize to manage people issues occurring “cross” teams – should be “across”

96 – choice, particularly when for teams new to agile – redundant “when”

97 – reference to SDFC should read SDCF instead

97 – The two continuous delivery (CD) require the team – “lifecycles” should be inserted before “require”

98 – require less Stakeholder flexibility due to being about to release – should be “able”

102 – Continuous Delivery: Program approach there the subteams – should be “where”

115 – a strategy that we’ve found effective it to first identify which process goals the team is reasonable for addressing – “it” should be “is” and “reasonable” should be “responsible”

119 – they’re from a certain group instead of because being the – redundant “because”

122  – educated on the importance sharing all relevant information – add “of” between the two words

129 – The options table should be Not Ordered (the heading says “Ordered”)

143 – goes a long way towards identify critical technical risks – “identifying”

157 – including #NoEstimates that you we consider – replace “we” with “might” or “could”

159 – The options table should be Ordered (the heading is missing)

159 – (this typically a few hours) – add the word “takes” between “typically” and “a”

159 – (compared with the entire time doing it. – replace “time” with “team” and add the missing parenthesis at the end

164 – It is worth – there is a sentence fragment after the first sentence of the decision point introduction which can be dropped.

166 – several estimation options available to us – It’s important – replace the hyphen with a period.

166 – It does this be choosing a work item – should be “by”

167 – The options table should be Not Ordered (the heading says “Ordered”)

172/181 – The ordering of the Test Environment(s) Platform Strategy options doesn’t match the goal diagram in Figure 12.1. It should be Physical – Virtual – Cloud-based whereas the diagram indicates Virtual – Physical – Cloud-based

181 – It may not be possible fully approximate – add the missing word “to”

182 – or non-functional, requirements for – redundant comma

196 – Continuous integration (CI) server – should be Tool-Generated Metrics (the 2nd option for this goal).

197 – This is better, usually, that not capturing – should be “than”

198 – There’s a reference to CRUFT challenges – that acronym should be in the glossary at the end of the book, and I couldn’t find a reference to CRUFT in chapter 19. The actual reference is in chapter 17 in Figure 17.2.

199 – We may wish to capture your findings – should be “our”

203 – which is sometimes referred to “WaterScrumFall” – “as” needs to be added after “to”

209 – we will likely need to educate some them on – add the word “of” after “some”

219 – your competitors releasing competing offering that you – offering should be plural

225 – Bas will often bring a – BA should be capitalized

227 – Supports addressing existing end users’ perceived or actual issues with the exiting solution – should be “existing”

244 – When we do create documentation is should be JBGE – should be “it”

254 – teams to refactor existing documentation based away from older – not quite sure what is intended by this sentence?

274 – This is a form of quality attribute (ilitity) testing. – should be “ility”

283 – embodiment of Production Ready milestone – add “the” before “Production”

283 – Yes, working software is nice but a consumable (… – the first items (usable + desirable + functional) should go between “software” & “is”

295 – Choose and evolve the teams way of working – it should be “team’s”

300 – enabling the coach to identify what people need coaching in. – the word “in” is unnecessary. Alternately, you can change it to “and in what.”

300 – focused on supporting out employees – should be “our”

307 – discover it needs to coordinate it’s release schedule – should be “its”

307 – provides opportunities for gaining mastery). – drop the closing parenthesis

312 – exploring them in sufficient detail so that understand what – should be “they”

314 – case it may be referred to a Joint Application Requirements – add “as” before the “a”

321 – Continuous Delivery: Agile or Continuous Delivery:Lean. – add the word “lifecycles” at the end

322 – there may no longer be slow/low usage. Periods. – drop the first period, and make “Periods” lowercase

323 – our team shouldn’t be geographical distributed. – should be “geographically”

323 – In Figure 23.6 you there is one person who is – drop the “you”

325 – of complexity factor including team size – should be “factors”

332 – Common and easy want to have – should be “way”

333 – when the team is a room with – should be “is in a”

334 – for nine months, the invest a month – should be “then”

337 – LeSS focuses solving the – add the word “on” after “focuses”

341 – and tooling oriented constraints such as – add a hyphen between “tooling” and “oriented”

342 – change their WoW because they team – change to “the”

348 – particularly one that is natively supports – drop “is”

348 – to evolve over time as the team evolves it’s WoW and – should be “its”

349 – Lean coffee is a structured by agenda-less meeting were people – drop “by” and change “were” to “where”

352 – particularly when the sketches agile models such – add “are of” after “sketches”

352 – A physical tasks that illustrates development – should be “task board”

362 – An example of a risk burndown is show in – should be “shown”

369 – The topic of guidance may address a specific… – change all the “i.e.”‘s in this sentence to “e.g.”‘s as they are examples

370 – technical guidance of the architecture team – add the words “the responsibility of” after “guidance”

371 – will need to invest the time to work with enterprise group responsible – add the word “the” after “with”

374 – might not be a very good fit our actual – add the word “for” after “fit”

374 – The team shares their potential improvement’s with others – drop the apostrophe

378 – not just want is convenient – should be “what”

381 – Many ScrumMasters struggle with because they don’t – put a space between Scrum and Masters and add the word “this” after with

388 – Enables our organization can invest in teams – should be “to”

388 – can use more funding, this many not always – should be “may”

392 – to get a feedback from a wide range of people – drop the “a”

392 – Stakeholders are provided access an internal demo – add the word “to” after “access”

396 – why certain practices are less effect than others – should be “effective”

396 – Take this book it to your retrospectives – drop the “it”

396 – You will be a better agilest, and – should be “agilist”

399 – Of course there are always limits to the . – Not quite sure what was intended by this sentence? Did you mean “Of course there are always limits to the value provided by a certification”?


When we’ve indicated a version number for a fix that means that we’ve uploaded a new file for that format of the book. When we upload a version it takes up to 72 hours to process so it’s a serious decision to release an update. We update both the paperback and the Kindle version at the same time, although either version seems to propagate to the various Amazon sites a different rates. Once we submit the files we have no control over how long it takes to deploy across sites (strangely, the paperback version seems to deploy faster).

When there isn’t a version number indicated for the fix then we have addressed it in the source but have not yet released it to Amazon/Kindle.