Historical errata for Agile Retrospectives

In the paragraph beginning “Sometimes teams come up with…”, at the end of the first sentence, change “can overwhelm you ability” to “can overwhelm your ability”.

In the variations section, “For example:” is printed twice consecutive.

I think “been been” should be replaced with a single “been” in this page’s final sentence: "Using this type of check-in is helpful when there has been been conflict or failure

page 176 of 185, printed page 158. Link to article is cut off. See bibliography [Mac03]. It should be … XP%20Call%20In%20the%20social%20workers%20-%20Final.pdf

It seems that this is common problem if link is to long. It is not folded on right margin but extended to the right and then cut off on paper border.

Reference [Sch94] author’s name is misspelled. S/B Schwarz, not Schwartz.

Under the heading of Phase: Generate Insights, the Report Out and Synthesis section includes the word “treads” which should probably be “trends”, or perhaps “threads”.

under variations, For example: is repeated, and used again in the next paragraph.

"We have collected several variations on the timeline activity. We use
index cards, sticky notes, markers and dots in a number of ways to
pull out both fact and feelings data. For example: For example:

Ask people to select a cluster that they want to work on refining.
It’s if no one chooses some of the clusters.

—> It’s OK if no one..

The text for #5 is: Ask people to select a cluster that they want to work on refining. It’s if no one chooses some of the clusters.

The second sentence is missing a word. I think “ok” should be the second word in the sentence.

Tip: Introducing Activities, second paragraph, second sentence
“Saying the words is different reading them or thinking them.” -> “Saying the words is different [than or from] reading them or thinking them.”

First paragraph, should say “described” rather than “describe”: “The four-step debriefing method describe in Chapter 3”

Diana Larsen mentioned during the “Agile Retrospective” course in Taastrup, Denmark that they had shifted from talking about the “goal” of a retrospective to talking about a “focus” because the former could limit peoples thinking (as if the “solition” was given already).

The term “goal” is used in many places throughout the book, this is just the first occurance I stumbled upon.

General suggestion - Size of the group impacts retros Team size & Retros DON’t start retros for the first time with a large team or multiple teams together. DO start holding retros with small teams or sub teams of larger team and hold each separately. When you have a retrospective culture and teams are used to focusing on improving themselves instead of finger pointed, then you may want to hold larger retros with either the large group together or representatives of each group. Project timeline retros could be appropriate for a large group. - Expect large group retros to take longer and be more painful.

At the top of the page, it reads “we’ll need to look further than the our previous two-week iteration.” The starred word should be omitted.