Historical errata for Fixing Your Scrum

In the next paragraph the word ‘the’ can be removed:
Worse is when companies rename their old practices with shiny new Scrum labels and immediately expect twice the work in the half the time.
The word

Repeated “be” in the following paragraph:
Initially, changing direction based on experience (empiricism) may be be difficult to get people to buy into, but positive results will help you win them over.

or assisting them in them being transparent to the team and stakeholders about a value hypothesis they have formed.

The word “them” is repeated in “assisting them in them being”

“and explain why a having a single product owner is a better approach”

“a” can be removed from “why A having”

This is simialr to our advice earlier in this chapter: trace the money.

Typo in word “simialr” -> “similar”

“There doesn’t seem to be an end goal or objective, just more work to work to do.”

Repeated words “work to”

It’s scary situation that we’ve seen happen, and it comes with dire consequences.

“It’s scary situation” should say “It’s A scary situation”

Cutting corners by ignoring the definition of done trades short-term gains for a long-term losses.

“for a long-term losses” should say: “for long-term losses”

… so it’s common for companies that a new to Scrum to organize their dev teams this way

“that a new to Scrum” should say: “that ARE new to Scrum”

“There aren’t many sports that 29-person teams.”

Sentence is not entirely clear

“If it looks like the team isn’t making decision about their work, brainstorm ways the team can correct the imbalance in decision making.”

“isn’t making decision” should say: “isn’t making decisionS”

“Let’s see if we can more precicely quantify the value of a Scrum master.”

Typo “precicely” -> “preciSely”

“If someone is only a part-time Scrum master, do you think it’s really possible for them perform these three levels of service in a way that makes a meaningful impact on the organization?”

“for them perform” should say: “for them TO perform”

“For example, if the coders are getting ahead of the testers every sprint, eventually they coders will be a full sprint ahead and the testers will be a full sprint behind.”

“eventually they coders” should say: “eventually THE coders”

“Even if the development team has minimized the handoffs, made work as collaborative as possible, and fully integrated their work with systems and others teams”

“others teams” should say: “OTHER teams”

“The development team members know who they need to accomplish the sprint goal.”

“know who they need” should say: “know WHAT they need”

“The product owner was in this situation was having a really tough time.”

“The product owner WAS in this situation WAS” should say “The product owner in this situation WAS”

“A sprint is fixed period of time that you’ve decided to use to capitalize on an opportunity in the marketplace.”

“A sprint is fixed period of time” should say: “A sprint is A fixed period of time”

“The number of weeks that your team decides on isn’t nearly important as the reasoning behind the choice and the collaborative discussions that led to that decision.”

“isn’t nearly important” should say: “isn’t nearly AS important”

“These activities include adding details, estimating, decomposing, discussing implementation plans, and performing any other product backlog activities that are necessary to prepae for upcoming sprints.”

typo “prepae” -> “prepare”

“The product owner has a hypothesis the addition of digital payments is something that will be widely used by customers.”

“has a hypothesis the addition” should say: “has a hypothesis THAT the addition”

“In many organizations, there are be many impediments that must be removed before teams can release products on demand.”

“there are be” should either say: “there are” or “there will be”

“Also, keep in mind is that this event is for the Scrum team only.”

“keep in mind IS that” should say: “keep in mind that”

“When the focus is on individual status updates, you’ve lost most of the value of the saily scrum.”

“saily” should say: “daily”

“You lose transparency, and put the sprint goal is at risk because the focus is on individual statuses”

The word “is” can be removed from: “put the sprint goal IS at risk”

3. Once they’ve explored these ideas in pairs, have the pairs form foursomes
and spend four minutes sharing and developing these ideas even further, paying special attention to the simularities, differences, and patterns they notices during their discussion.

Typo “simularities” -> “similarities”

3. Once they’ve explored these ideas in pairs, have the pairs form foursomes
and spend four minutes sharing and developing these ideas even further, paying special attention to the simularities, differences, and patterns they notices during their discussion.

Typo: “and patterns they noticeS”

“If team members simplay aren’t aware that they can speak up”

Typo: “simplAy” -> “simply”

You’ll often hear generic answers, overly technical answers, vague hand waving about work getting done “soon,”” and other unprepared answers.

Extra ” after soon.

If your Daily Scrum doesn’t suffer from any of the major anti-patterns we discussed in this chapter but you still feel like it could be more productivre, here are a few things that you can try during your next Daily Scrum:

Typo: “productivRe” -> “productive”

4. Skip attending the Daily Scrum every once in a while and see what hap- pens. Hopefully the development team will still hold the event, align on their work, and develop a plan for the day that helps the them achieve the Sprint goal.

Word “the” can be removed in “that helps THE them achieve”

Many product owners love the sprint review precicely because it gives them a chance to show stakeholders how hard and complicated the Scrum team’s work is.

Typo: “precicely” -> “precisely”

Stakeholders should know the reasoning behind the sprint goal the that team accomplished as well as the direction the project is headed.

“behind the sprint goal THE THAT team accomplished” should say: “behind the sprint goal THAT THE team accomplished”

A Scrum master should facilitate the sprint review in an engaging, collaborative way that involves everyone in attendancee.

Typo: “attendanceE” -> “attendance”

It contains some excellent info ABOUT ON what motivates human beings.

Should either say: “info about what” or “info on what”.

in the sentence “As we’ve discussed, the plan the dev team devised during sprint planning will likely substantially change as they executes the work”“executes” should be “execute”

In the sentence “In our example workflow chart, an PBI becomes active when it moves from the “To-do” column to the “In dev” column, and it finishes when it moves to the “Done” column" “an PBI” should be “a PBI”.

Bullet point 3 on the page starts with “Boot the peanut ballery”, the last word should be gallery.

Fifth bullet point on the page states “How do we increase the odds that the most important thing get to done?”, this should be corrected by replacing “get” with “gets”.

In “Joe asks,” the footnote for “planning poker” is displayed in markdown format. it needs to be in PML format to generate the footnote.

In “Joe asks,” the cross-reference to the Sprint Planning chapter is in markdown format. In order to generate the cross-reference, it needs to be in PML.

In the third line of point 2. I assume it should say “work will emerge during the sprint - it’s important to be cognizant of that” instead of “sprint -i’s important”

I think I just found a typo at the top of page 53, chapter 5. When you are talking about imagining a stakeholder asking when feature d will be done, you say feature “a” instead of d later in the same paragraph. You then explain the math in the next paragraph.

“The techniques and practices this vary, but…” I think this is meant to say The techniques and practices to do this may vary or something like that. This is at the bottom of page 84 in printed version, 3/4 of the way through the Rotating Scrum Master section.

4th bullet of Loving the Details of Delivery when explaining a manager who wanted everyone to do estimates the same way. Last sentence I think is wrong as if the manager prevailed the team would then not have been able to self-organize. “The manager eventually prevailed, preserving the development team’s ability to make decisions that enabled self-organization.”

First bullet at bottom of page 127 within Letting Debt Build Up. I believe it should say “Is there ‘any’ way that…”