Historical errata for Agile Coaching

In Showing not Telling “sidebar”, last sentence of first paragraph is “Now they know how to use the job becomes easier
and they’re happier using the hammer because they understand
how it works.”
I suggest it should be “Now that they know how to use the hammer, the job becomes easier,and they’re happier using the hammer because they understand how it works.”

In How to Read This Book, the first paragraph, second sentence reads “We’ve share these at the end of each chapter together
with our advice on how to clear them.”
I suggest it should be either “We’ll share these…” or “We’ve shared these…”

Under The Aim of this Book, second paragraph, the first sentence is awkward: “Depending on team context, we might give opposite advice to one team than another.”
I suggest it could be “Depending on team context, we might give opposing advice to different teams.”
Also, in the following example, you genderfy the project manager as ‘he’; is this intentional? Perhaps use the neutral ‘they’ (e.g., ‘…recommended that they don’t [attend]’) or just ‘…recommended the opposite.’?

In sidebar, “how to use the job” s/b “how to use it the job”

2nd paragraph, 3rd sentence, “incorrect, this creates bad feeling” s/b “incorrect; this creates bad feelings”

Section 1.3 Getting Ready to Coach, first and third sentences, agile is not capitalized.

4th sentence, “…work, your family are now Agile experts,..” s/b “…work, your family members are now Agile experts,…”

Section Arrange to be Introduced, third sentence, the title “agile coach” should be capitalized.

In sidebar No Formal Introduction, first sentence, agile isn’t capitalized. Also, driven in Test-driven Development isn’t either…should it be?

Section External Coach, first and last sentences, agile isn’t capitalized.

In section External Coach, the last sentence has a superfluous comma after ‘meet’.

In the Internal Coach section, the first sentence is passive voice. Suggest “If your manager has asked you to be a coach…”

In the Extending Your Role section, the first sentence is fragmented. Suggest “…introduce Agile, but you believe…”. Also, agile at the end of the sentence isn’t capitalized.

“team mates” should be one word, “teammates”

the preferred spelling of “focussed” is “focused”

Sidebar: “useful to try and answer” s/b “useful to try to answer”

Sidebar: Responsibilities
“Do any these conflict” s/b “Do any of these conflict”

Learn as You Go (section)
Third paragraph:
“Read books, read blogs, listen to podcasts, and try connect with others who are interested in Agile.”

Suggest to change to:
“Read books, read blogs, listen to podcasts, and try to connect with others who are interested in Agile.”

Foreward should be Foreword

The sentence “These high performance teams
may not be all that much smarter than your team,” seems to say “They’re smarter than you, just not all that MUCH smarter than you.” Perhaps simplifying to “…may not be smarter than your team…” to eliminate the implication.

“Most teams we work with are using a mixture of Scrum and Extreme
Programming (XP) so throughout the book we’ll refer to this as Agile.” should have a comma after (XP)

“I often meet teams who are trying to follow agile practices but
what they’re doing is quite odd and not a good use of their
time.” should have a comma here: “…practices, but…”

First paragraph, third sentence, ‘team mates’ s/b ‘teammates’.

First paragraph, fifth sentence, “Suggest that he calls a meeting…” s/b “Suggest that he call a meeting…”.

First paragraph, second sentence, “…knew each another…” should be “…knew each other…” (or “…knew one another…”)

First paragraph of sidebar: “Showing how agile prac-tices work is one of the main thing we do as agile coaches.”, thing should probably be plural (things)?

1.6 Hurdles -> No Time to Coach -> 2nd paragraph

“… an different …” should be “… a different …”?

First paragraph in the sidebar

“Encourage the team they’re learning new skills, …” should be “Encourage the team when they’re learning new skills, …”?

Sidebar -> Leveraging Resistance -> 1st paragraph, 2nd sentence

“In it he talks what the types of …” should be “In it he talks about what the types of …”?

3.2 Asking Questions -> Third paragraph, 2nd sentence.

“… what what …” should be only one what?

Sidebar, last paragraph, second last paragraph:

“… may be inspired decide to try doing this
themselves.” either inspired or decide should be deleted?

Last sentence of last paragraph on the page:

“This helps them becomes conscious …” should be “This helps them become conscious …”

Last sentence in last paragraph on the page.

“… may be things outside your influence over
as a coach …” might sound better without “over”?

Second to last sentence on second to last paragraph:

“Invite these virtual team members to all the agile meet-ings and include them on emails.” should have “all of” or delete “all”?

Last part of the final sentence doesn’t make sense:

“… about other things, such getting a story done.”

Second last paragraph first sentence:

“The team needs to get good understanding of the different types…”, either needs to have “… get a good …” or “… understanding the different …”

First full sentence on the page starts with:
“Explain, if there’s no …” I think the “Explain” might be a note to yourselves that didn’t get deleted?

the doctor isn’t really listening and doesn’t help to solve the problem

This helps to show the person that you are listening

he says holding the ball out to to Rebecca.

a bit like like Jiminy Cricket

you say James Shore, but the reference is Jim Little…

Chapter 6: and what about the stories that have nothing to do with any user? Architectural stuff, for example…. In larger projects.

Stories or Tasks? (yes, I’ve seen page 118)

idealistic burn down chart. I am still waiting to see a real one that smooth !

idealistic chart. I am still waiting to see a real one that smooth !

Brief the janitorial staff. We found our sticky note nicely in a pile and the white board super clean.

I do not get it…

chapter 10. And what about tests that cannot be done by software. I seem to run into this kind of application more often than the average agilist.
My customers do: marine cartography, landing and takeoff charts, paper mill control, and other kind of embedded, distributed control, … Only a small fraction of the code can lend itself to TDD, to automated acceptance testing etc.

Chapter 11. What about deliberate, intentional technical debt (type II in Steve McConnell’s terms)…. Taking some architectural short-cut in early releases, that are almost impossible to simply “refactor”… Incremental design also leads to this, though less deliberately.
Refactoring is great, but not always the panacea.

Chapter 12: demo: same comment as chapter 10 above. Cannot demo a run of the papermill. (beyond what you write on page 188)

In “It’s not a great joke, but Doctor, Doctor jokes have a common theme:” it seems to me initially that there was a typo and “Doctor” was repeated twice as a mistake. It might be a type of joke but it could be clearer if it was put between " as in “Doctor, Doctor”

Sentence - You may find that people who’ve
grown up in a different culture than you say “yes” to mean “I’m listening,” rather than to mean “Yes, I know how do that.”

Should read “Yes, I know how to do that” ?

Sentence: For large stories, which will take more than a couple of days to build, suggest to the team that they decompose the work into tasks: small pieces of work that contribute to the delivery of a user story (a few hours work not, more than a day)

“a few hours work not, more than a day” should read “a few hours of work, not more than a day” ?

“the team can using magnets” should be “the team can use magnets”