Footnotes

Chapter 3

1. See Chapter 21, “When Cultures Collide,” for an example of a team member who does more harm than good.

Chapter 5

1. See Chapter 3, “Using Team Consultants to Optimize Team Performance.”

Chapter 9

1. Defined in the published [NAGGAPAN] paper as “When software is being developed, a person makes an error that results in a physical fault (or defect) in a software element. When this element is executed, traversal of the fault or defect may put the element (or system) into an erroneous state. When this erroneous state results in an externally visible anomaly, we say that a failure has occurred.”

Chapter 25

1. See Chapter 7, “How Do We Know When We Are Done?,” for more on the team’s definition of done.

Appendix

1. See Chapter ...

Get The Scrum Field Guide: Practical Advice for Your First Year now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.