#ContinuousImprovement
The Protocol for Reporting an Error to an Author or Publisher
22 March 2024
BY SCOTT M. GRAFFIUS | ScottGraffius.com
This article covers what to do if you find an error in a book, scientific paper, or other publication. Including supporting information, it's organized into eight sections:
This article does not cover how to handle violation of copyrights or other intellectual property (IP) rights. For IP cases, it is recommended that you consult a qualified attorney.
Introduction
Have you encountered a typo in a book or a factual error in a scientific paper? Errors, whether minor typos or significant inaccuracies, can compromise the credibility, readability, and utility of published works. However, you can make a difference. By reporting these errors to the author or publisher, you contribute to advancing the integrity and value of the respective information.
This article will equip you with information to report errors effectively, irrespective of the subject matter. From identifying the error and crafting a clear report to understanding what happens post-submission, each step is covered. Whether it's enhancing the experience for future readers or upholding the accuracy and integrity of scientific works, your vigilance and action in reporting errors plays a pivotal role.
How to Report an Error
If you discover an error in a publication, here are the recommended steps for reporting it:
STEP 1: Is there a newer edition or update to the publication?
1A. Yes, there is a newer edition or update.
XXX 1A1. Is the error resolved in the newer edition or update?
XXX XXX 1A1A. If yes to 1A1, the error is resolved in the newer edition or update, then no further action is needed.
XXX XXX 1A1B. If no to 1A1, then go to STEP 2.
1B. If no, there is not a newer edition or update, then go to STEP 2.
STEP 2: Is there a publisher’s web page for the publication, or an author’s website which mentions the publication, or an errata/corrections list for the publication at any location (Google the publication’s title and "AND errata OR corrections")?
2A. Yes, there’s a publisher's web page for the publication, an author's website which mentions the publication, or an errata/corrections list for the publication at any location
XXX 2A1. Is the error referenced?
XXX XXX 2A1A. If yes to 2A1, then no further action is needed.
XXX XXX 2A1B. If no to 2A1, then go to STEP 3.
2B. If No, there is not a publisher's web page for the publication, or an author's website which mentions the publication, or an errata/corrections list for the publication at any location, then go to STEP 3.
STEP 3: Does the publication specify the process for reporting an error?
3A. If yes, the publication specifies the process for reporting an error, then follow it to report the error.
3B. If no, the publication does not specify the process for reporting an error, then go to STEP 4.
STEP 4: Does the publisher’s website or author’s website specify the process for reporting an error?
4A. If yes, the publisher’s website or author’s website specifies the process for reporting an error, then follow it to report the error.
4B. If no, neither the publisher’s website nor the author’s website specifies the process for reporting an error, then go to STEP 5.
STEP 5: Does the publication include an email address for the publisher or author?
5A. If yes, the publication includes an email address for the publisher or author, then use it to send an email with your report of the error.
5B. If no, the publication does not include an email address for the publisher or author, then go to STEP 6.
STEP 6: Does the publisher’s website or the author’s website include an email address?
6A. If yes, the publisher’s website or the author’s website includes an email address, then use it to send an email with your report of the error.
6B. If no, the publisher’s website or the author’s website does not include an email address, then go to STEP 7.
STEP 7: Can you find an email address for the publisher or author via other means (such as a Google search)?
7A. If yes, you found an email address for the publisher or author, then use it to send an email with your report of the error.
7B. If no, you could not find an email address for the publisher or author, then you may — or may not — want to contact the publisher or author via another method (such as a direct message on social media).
Suggestions for reporting an error via email:
A Real Example of Reporting an Error
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) is the Project Management Institute’s flagship publication and is a fundamental resource for effective project management in any industry. The book is the global, gold standard for project management. The PMI released the seventh edition of the PMBOK Guide on August 1, 2021.
On November 4, 2021, Scott M. Graffius discovered that a factual error was introduced into the seventh edition of the PMBOK Guide.
The PMI has a process to handle such problems. If/when errors are discovered, the PMI instructs individuals to share findings by completing the PMI Standards Program Comment Form and emailing it to the PMI. The form has two sections: Comment and Suggested Change. Graffius completed the form.
Here’s what Graffius wrote in the Comment section: “Section 4.2.6.1 Tuckman Ladder includes: ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, and performing. Many people add a fifth stage, adjourning.’ The passage is misleading and incorrect. Here’s why. In 1965, Bruce Tuckman introduced his model inclusive of four stages: forming, storming, norming, and performing. (The source/citation: Tuckman, B. W. (1965). Developmental Sequence in Small Groups. Psychological Bulletin, 63: 384-399.) However, Tuckman subsequently discovered adjourning to be so important that he updated his own model in 1977 to include adjourning. (The source/citation: Tuckman, B. W., & Jensen, M. A. C. (1977). Stages of Small-Group Development Revisited. Group and Organizational Studies, 2 (4): 419- 427.) Tuckman says there are five stages: forming, storming, norming, performing, and adjourning. By not including that relevant, informative, and helpful fact — and instead vaguely saying ‘Many people add a fifth stage, adjourning.’ — the passage is misleading and incorrect.”
Here's what Graffius wrote in the Suggested Change section: “For the reason detailed in the Comment section of this form, I suggest changing the passage from ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, and performing. Many people add a fifth stage, adjourning.’ to: ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, performing, and adjourning.’ or ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, performing, and adjourning. He introduced the first four stages in 1965, and he added the fifth stage when he updated his model in 1977.’”
The completed Standards Program Comment Form also included Graffius’ name and email address. He emailed the form to the PMI on November 4, 2021.
What happened next? The story is here.
What Happens After You Report an Error
Error handling varies by organization. Generally, excerpt for cases where a minor error is concerned, any necessary changes (such as updating the publication) will be accompanied by a post-publication notice, which will be linked to the original publication. These changes can take the form of a Correction notice, an Expression of Concern, a Retraction, or a Removal. The four forms are delineated next.
Forms/notices may be called an erratum (plural: errata) or a corrigendum (plural: corrigenda). See the Glossary section of this article for details.
Conclusion
This article provided information on how to report errors effectively. From identifying the problem and crafting a clear report to understanding what happens post-submission, this article shined a light on each step. Whether it's enhancing the experience for future readers or upholding the accuracy and integrity of scientific works, your vigilance and action in reporting errors plays a pivotal role.
Glossary of Terminology
References/Sources
How to Cite This Article
Graffius, Scott M. (2024, March 22). The Protocol for Reporting an Error to an Author or Publisher. Available at: https://scottgraffius.com/blog/files/error-reporting.html. DOI: 10.13140/RG.2.2.18830.98883.
Post-Publication Notes
If there are any supplements or updates to this article after the date of publication, they will appear here.
After the article was published, Scott M. Graffius developed a flowchart of the suggested steps for reporting an error. The flowchart is a draft and it is subject to change.
About Scott M. Graffius
Scott M. Graffius, PMP, SA, CSP-SM, CSP-PO, CSM, CSPO, ITIL, LSSGB is an agile project management practitioner, consultant, thinker, creator, multi-award-winning author, and international public speaker. Founder and CEO of Exceptional PPM and PMO Solutions™ and subsidiary Exceptional Agility™, he has generated over $1.9 billion for Global Fortune 500 businesses and other organizations he has served. Graffius and content from his books, talks, workshops, and more have been featured and used by Microsoft, Oracle, Broadcom, Cisco, Gartner, Project Management Institute, IEEE, National Academy of Sciences, United States Department of Energy, Yale University, Tufts University, and others. He delights audiences with dynamic and engaging talks and workshops on agile project management, AI, Tech leadership, video game development, strategic alignment, the science of high performance teams, and more. To date, he's presented sessions at 89 conferences and other events across 25 countries.
His full bio is available here.
Connect with Scott on:
About Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions
Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive.
There are a variety of frameworks supporting the development of products and services, and most approaches fall into one of two broad categories: traditional or agile. Traditional practices such as waterfall engage sequential development, while agile involves iterative and incremental deliverables. Organizations are increasingly embracing agile to manage projects, and best meet their business needs of rapid response to change, fast delivery speed, and more.
With clear and easy to follow step-by-step instructions, Scott M. Graffius's award-winning Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions helps the reader:
Hailed by Literary Titan as “the book highlights the versatility of Scrum beautifully.”
Winner of 17 first place awards.
Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
About Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change
Thriving in today's marketplace frequently depends on making a transformation to become more agile. Those successful in the transition enjoy faster delivery speed and ROI, higher satisfaction, continuous improvement, and additional benefits.
Based on actual events, Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change provides a quick (60-90 minute) read about a successful agile transformation at a multinational entertainment and media company, told from the author's perspective as an agile coach.
The award-winning book by Scott M. Graffius is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
© Copyright 2024 Scott M. Graffius. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without the express written permission of Scott M. Graffius.
This article covers what to do if you find an error in a book, scientific paper, or other publication. Including supporting information, it's organized into eight sections:
- Introduction
- How to Report an Error
- A Real Example of Reporting an Error
- What Happens After You Report an Error
- Conclusion
- Glossary of Terminology
- References
- How to Cite This Article
This article does not cover how to handle violation of copyrights or other intellectual property (IP) rights. For IP cases, it is recommended that you consult a qualified attorney.
Introduction
Have you encountered a typo in a book or a factual error in a scientific paper? Errors, whether minor typos or significant inaccuracies, can compromise the credibility, readability, and utility of published works. However, you can make a difference. By reporting these errors to the author or publisher, you contribute to advancing the integrity and value of the respective information.
This article will equip you with information to report errors effectively, irrespective of the subject matter. From identifying the error and crafting a clear report to understanding what happens post-submission, each step is covered. Whether it's enhancing the experience for future readers or upholding the accuracy and integrity of scientific works, your vigilance and action in reporting errors plays a pivotal role.
How to Report an Error
If you discover an error in a publication, here are the recommended steps for reporting it:
STEP 1: Is there a newer edition or update to the publication?
1A. Yes, there is a newer edition or update.
XXX 1A1. Is the error resolved in the newer edition or update?
XXX XXX 1A1A. If yes to 1A1, the error is resolved in the newer edition or update, then no further action is needed.
XXX XXX 1A1B. If no to 1A1, then go to STEP 2.
1B. If no, there is not a newer edition or update, then go to STEP 2.
STEP 2: Is there a publisher’s web page for the publication, or an author’s website which mentions the publication, or an errata/corrections list for the publication at any location (Google the publication’s title and "AND errata OR corrections")?
2A. Yes, there’s a publisher's web page for the publication, an author's website which mentions the publication, or an errata/corrections list for the publication at any location
XXX 2A1. Is the error referenced?
XXX XXX 2A1A. If yes to 2A1, then no further action is needed.
XXX XXX 2A1B. If no to 2A1, then go to STEP 3.
2B. If No, there is not a publisher's web page for the publication, or an author's website which mentions the publication, or an errata/corrections list for the publication at any location, then go to STEP 3.
STEP 3: Does the publication specify the process for reporting an error?
3A. If yes, the publication specifies the process for reporting an error, then follow it to report the error.
3B. If no, the publication does not specify the process for reporting an error, then go to STEP 4.
STEP 4: Does the publisher’s website or author’s website specify the process for reporting an error?
4A. If yes, the publisher’s website or author’s website specifies the process for reporting an error, then follow it to report the error.
4B. If no, neither the publisher’s website nor the author’s website specifies the process for reporting an error, then go to STEP 5.
STEP 5: Does the publication include an email address for the publisher or author?
5A. If yes, the publication includes an email address for the publisher or author, then use it to send an email with your report of the error.
5B. If no, the publication does not include an email address for the publisher or author, then go to STEP 6.
STEP 6: Does the publisher’s website or the author’s website include an email address?
6A. If yes, the publisher’s website or the author’s website includes an email address, then use it to send an email with your report of the error.
6B. If no, the publisher’s website or the author’s website does not include an email address, then go to STEP 7.
STEP 7: Can you find an email address for the publisher or author via other means (such as a Google search)?
7A. If yes, you found an email address for the publisher or author, then use it to send an email with your report of the error.
7B. If no, you could not find an email address for the publisher or author, then you may — or may not — want to contact the publisher or author via another method (such as a direct message on social media).
Suggestions for reporting an error via email:
- In the subject line of your email, note “Reporting an error in [name of publication]”
- In the main part of your email, reiterate that you’re writing to report an error in [name of publication]. Specify the page number(s)/location(s) of the respective content and delineate the error or problem. Provide as many details are practical.
- In the closing part of your email, note your email address (even if it’s the same email you used to send the report).
A Real Example of Reporting an Error
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) is the Project Management Institute’s flagship publication and is a fundamental resource for effective project management in any industry. The book is the global, gold standard for project management. The PMI released the seventh edition of the PMBOK Guide on August 1, 2021.
On November 4, 2021, Scott M. Graffius discovered that a factual error was introduced into the seventh edition of the PMBOK Guide.
The PMI has a process to handle such problems. If/when errors are discovered, the PMI instructs individuals to share findings by completing the PMI Standards Program Comment Form and emailing it to the PMI. The form has two sections: Comment and Suggested Change. Graffius completed the form.
Here’s what Graffius wrote in the Comment section: “Section 4.2.6.1 Tuckman Ladder includes: ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, and performing. Many people add a fifth stage, adjourning.’ The passage is misleading and incorrect. Here’s why. In 1965, Bruce Tuckman introduced his model inclusive of four stages: forming, storming, norming, and performing. (The source/citation: Tuckman, B. W. (1965). Developmental Sequence in Small Groups. Psychological Bulletin, 63: 384-399.) However, Tuckman subsequently discovered adjourning to be so important that he updated his own model in 1977 to include adjourning. (The source/citation: Tuckman, B. W., & Jensen, M. A. C. (1977). Stages of Small-Group Development Revisited. Group and Organizational Studies, 2 (4): 419- 427.) Tuckman says there are five stages: forming, storming, norming, performing, and adjourning. By not including that relevant, informative, and helpful fact — and instead vaguely saying ‘Many people add a fifth stage, adjourning.’ — the passage is misleading and incorrect.”
Here's what Graffius wrote in the Suggested Change section: “For the reason detailed in the Comment section of this form, I suggest changing the passage from ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, and performing. Many people add a fifth stage, adjourning.’ to: ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, performing, and adjourning.’ or ‘Bruce Tuckman articulated the stages of team development as forming, storming, norming, performing, and adjourning. He introduced the first four stages in 1965, and he added the fifth stage when he updated his model in 1977.’”
The completed Standards Program Comment Form also included Graffius’ name and email address. He emailed the form to the PMI on November 4, 2021.
What happened next? The story is here.
What Happens After You Report an Error
Error handling varies by organization. Generally, excerpt for cases where a minor error is concerned, any necessary changes (such as updating the publication) will be accompanied by a post-publication notice, which will be linked to the original publication. These changes can take the form of a Correction notice, an Expression of Concern, a Retraction, or a Removal. The four forms are delineated next.
- Correction Notice. When a work is impacted by an error (or omission) but the scholarly integrity remains intact, a Correction Notice or similar communication will be issued. Some publishers classify errors as major or minor. With that bifurcation, major errors (such as missing text) are addressed by a Correction Notice, and minor errors (such as typos) are addressed by either a Correction Notice or another action — such as a footnote or other notation added to the publication detailing that the publication has been corrected.
- Expression of Concern. In certain cases, such as a protracted active investigation into potential research or publication misconduct, an Expression of Concern may be issued. At the conclusion of the investigation, a Correction Notice or Retraction may be disseminated.
- Retraction. Where a major error invalidates the academic integrity of the publication or where misconduct has taken place, a Retraction will be issued.
- Removal. In circumstances where problems cannot be handled via a Correction Notice or Retraction, a Removal will be performed. Note: This is rare.
Forms/notices may be called an erratum (plural: errata) or a corrigendum (plural: corrigenda). See the Glossary section of this article for details.
Conclusion
This article provided information on how to report errors effectively. From identifying the problem and crafting a clear report to understanding what happens post-submission, this article shined a light on each step. Whether it's enhancing the experience for future readers or upholding the accuracy and integrity of scientific works, your vigilance and action in reporting errors plays a pivotal role.
Glossary of Terminology
- Addendum. Used for additional information that wasn't available at the time of publication but needs to be included for completeness.
- Correction Notice. A broad term that can encompass any of the following scenarios. When a work is impacted by an error (or omission) but the scholarly integrity remains intact, a Correction Notice or similar communication will be issued. Some publishers classify errors as major or minor. With that bifurcation, major errors are addressed by a Correction Notice, and minor errors are addressed by either a Correction Notice or another action — such as a footnote or other notation added to the publication detailing that the publication has been corrected.
- Corrigenda. See: Corrigendum.
- Corrigendum. Singular: Corrigendum. Plural: Corrigenda. Formality: Corrigendum is a more formal term used to correct errors in books, journals, or other publications. Publication: A corrigendum is typically issued by the publisher as a separate notice that accompanies the original publication. Scope: It usually addresses significant errors that affect the overall content, such as factual inaccuracies, incorrect data, or major typos. Format: A corrigendum provides a clear description of the errors and the corrected information, usually including page numbers or sections where the corrections should be applied. Also see: Errata, Major Error, Minor Error.
- Errata. Singular: Erratum. Plural: Errata. Formality: Errata is a more informal term used to indicate errors in books, articles, or other publications. Inclusion: Errata may be included directly in the publication itself, often as a list of corrections at the beginning or end of the book or article. Scope: It can address both minor and major errors. Format: Errata are usually presented as a list, highlighting the errors and providing the corrected information without the formal structure of a corrigendum. Also see: Corrigendum.
- Erratum. See: Errata.
- Factual Error. An inaccuracy in the information presented. Factual errors are usually considered to be major errors.
- Formatting Error. Mistakes related to layout, style, or referencing. Formatting errors are usually considered to be minor errors.
- Major Error. Major errors are errors or omissions (such as missing text) that can impact the interpretation of the publication but where the scholarly integrity of the work remains intact. Also see: Minor Error.
- Minor Error. Minor errors are errors (such as typos or formatting errors) which do not impact the readers’ understanding of the content. Also see: Major Error.
- Reader Report. In academic publishing, this refers to feedback provided by reviewers who identify errors or suggest improvements before publication.
- Retraction. A retraction is a disavowal of a work. It's typically done when findings in the work are not considered trustworthy due to scientific misconduct or error — when a significant error invalidates the findings or conclusions, when the work is found to have plagiarized or infringed on the copyright of another work, or when the work is found to have violated ethical guidelines.
- Typo. The term typo is short for typographical errors (e.g., spelling and grammar mistakes). Typos are classified as minor errors.
References/Sources
- Alter, Alexandra (2019, September 22). It’s a Fact: Mistakes are Embarrassing the Publishing Industry. Available at: https://www.nytimes.com/2019/09/22/business/publishing-books-errors.html.
- American Psychological Association (2019, November). Correction Notices. Available at: https://apastyle.apa.org/style-grammar-guidelines/research-publication/correction-notices.
- Association for Computing Machinery (ACM) (2018, November 15). ACM Publications Policy on the Withdrawal, Correction, Retraction, and Removal of Works from ACM Publications and ACM DL. Available at: https://www.acm.org/publications/policies/retraction-policy.
- Cambridge University Press (n.d.). Publishing Ethics. Available at: https://www.cambridge.org/core/journals/flow/information/journal-policies/publishing-ethics.
- Committee on Publication Ethics (COPE) (n.d.). Post-Publication Discussions and Corrections. Available at: https://publicationethics.org/postpublication.
- Elsevier (n.d.). Policy and Best practice: Errata & Corrigenda. Available at: https://www.elsevier.com/editor/perk/policy-and-best-practice-errata-and-corrigenda.
- Emerald Publishing (n.d.). Article Withdrawal & Correction. Available at: https://www.emeraldgrouppublishing.com/publish-with-us/author-policies/article-withdrawal-correction.
- Faust, Jessica (2007, October 3). Typos and Errors After Publication. Available at: https://bookendsliterary.com/typos-and-errors-after-publication.
- Graffius, Scott M. (2021, November 10). An Error Was Introduced Into the Seventh Edition of 'A Guide to the Project Management Body of Knowledge (PMBOK)'. Available at: https://scottgraffius.com/blog/files/pmbok7.html.
- Idunn (n.d.). Publishing and Research Ethics Policy. Available at: https://www.idunn.no/info/publiseringsetikk.
- IEEE (n.d.). Publishing Ethics: Guidelines and Policies: Post-Publication Policies. Available at: https://books.ieeeauthorcenter.ieee.org/book-publishing-at-ieee/publishing-ethics/guidelines-and-policies/post-publication-policies.
- Institute for Operations Research and the Management Sciences (INFORMS) (n.d.). Guidelines for Ethical Behavior in Publishing. Available at: https://pubsonline.informs.org/page/opre/guidelines-for-ethical-behavior-in-publishing.
- IntechOpen (n.d.). Retraction and Correction Policy. Available at: https://www.intechopen.com/page/retraction-and-correction-policy.
- Marasović, Tea; Utrobiĉić, Ana; and Maruŝić, Ana (2018, March 31). Transparency of Retracting and Replacing Articles. The Lancet, 391 (10127): 1244-1245.
- Nature (n.d.). Editorial and Publishing Policies. Available at: https://www.nature.com/srep/journal-policies/editorial-policies.
- O’Reilly Media (n.d.). Errata for Java in a Nutshell. Available at: https://www.oreilly.com/catalog/errata.csp?isbn=0636920030775.
- Palgrave Macmillan (n.d.). Corrections and Retractions. Available at: https://www.palgrave.com/gp/editorial-policies/corrections-and-retractions.
- Pearson Education / InformIT (n.d.). Contact Us: Submit Errata. Available at: https://www.informit.com/about/contact_us/index.aspx?ContactUs_Topics_Partners_id=9d39709c-c911-4c96-ac2c-2c5a22d68ba9.
- Project Management Institute (PMI) (n.d.). PMI Standards Program Comment Form. Available at: https://www.pmi.org/-/media/pmi/documents/public/pdf/pmbok-standards/pmi-standards-program-comment-form.pdf.
- Project Management Institute (PMI) (n.d.). Standards Errata Sheets. Available at: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/errata-sheets.
- Public Library of Science (PLOS) (n.d.). Corrections, Expressions of Concern, and Retractions. Available at: https://journals.plos.org/plosone/s/corrections-and-retractions.
- SAE International (n.d.). ARINC Standard – Errata Report Template. Available at: https://wcm14.sae.org/site/binaries/content/assets/itc/content/arinc/errata-form.docx [note: selecting the link will download the file].
- Sage Publications (n.d.). Sage Corrections and Retractions Policy. Available at: https://us.sagepub.com/en-us/nam/sage-corrections-and-retractions-policy.
- Science Publishing Group (n.d.). Ethical Guidelines. Available at: https://www.sciencepublishinggroup.com/information/ethical-guidelines.
- Springer (n.d.). Editorial Policies: Corrections and Retractions. Available at: https://www.springer.com/gp/editorial-policies/corrections-and-retractions.
- Taylor & Francis (n.d.). Publishing Ethics for Journal Editors: FAQs. Available at: https://editorresources.taylorandfrancis.com/publishing-ethics-for-editors/publishing-ethics-faqs.
- Ubiquity Press (n.d.). Correction and Retraction Policy. Available at: https://ubiquitypress.com/site/corrections.
- Warner, Brooke (2019, April 26). How to Publish a Perfect Book. Available at: https://www.publishersweekly.com/pw/by-topic/authors/pw-select/article/79902-how-to-publish-a-perfect-book.html.
- Wiley (n.d.). Best Practice Guidelines on Research Integrity and Publishing Ethics. Available at: https://authorservices.wiley.com/ethics-guidelines/index.html.
- Wiley Author Services (n.d.). Wiley's Policy for Handling Retractions, Withdrawals, and Expressions of Concern. Available at: https://authorservices.wiley.com/ethics-guidelines/retractions-and-expressions-of-concern.html.
- World Intellectual Property Organization (WIPO) (n.d.). Managing Intellectual Property in the Book Publishing Industry. Available at: https://www.wipo.int/edocs/pubdocs/en/copyright/868/wipo_pub_868.pdf.
How to Cite This Article
Graffius, Scott M. (2024, March 22). The Protocol for Reporting an Error to an Author or Publisher. Available at: https://scottgraffius.com/blog/files/error-reporting.html. DOI: 10.13140/RG.2.2.18830.98883.
Post-Publication Notes
If there are any supplements or updates to this article after the date of publication, they will appear here.
After the article was published, Scott M. Graffius developed a flowchart of the suggested steps for reporting an error. The flowchart is a draft and it is subject to change.
About Scott M. Graffius
Scott M. Graffius, PMP, SA, CSP-SM, CSP-PO, CSM, CSPO, ITIL, LSSGB is an agile project management practitioner, consultant, thinker, creator, multi-award-winning author, and international public speaker. Founder and CEO of Exceptional PPM and PMO Solutions™ and subsidiary Exceptional Agility™, he has generated over $1.9 billion for Global Fortune 500 businesses and other organizations he has served. Graffius and content from his books, talks, workshops, and more have been featured and used by Microsoft, Oracle, Broadcom, Cisco, Gartner, Project Management Institute, IEEE, National Academy of Sciences, United States Department of Energy, Yale University, Tufts University, and others. He delights audiences with dynamic and engaging talks and workshops on agile project management, AI, Tech leadership, video game development, strategic alignment, the science of high performance teams, and more. To date, he's presented sessions at 89 conferences and other events across 25 countries.
His full bio is available here.
Connect with Scott on:
About Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions
Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive.
There are a variety of frameworks supporting the development of products and services, and most approaches fall into one of two broad categories: traditional or agile. Traditional practices such as waterfall engage sequential development, while agile involves iterative and incremental deliverables. Organizations are increasingly embracing agile to manage projects, and best meet their business needs of rapid response to change, fast delivery speed, and more.
With clear and easy to follow step-by-step instructions, Scott M. Graffius's award-winning Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions helps the reader:
- Implement and use the most popular agile framework―Scrum;
- Deliver products in short cycles with rapid adaptation to change, fast time-to-market, and continuous improvement; and
- Support innovation and drive competitive advantage.
Hailed by Literary Titan as “the book highlights the versatility of Scrum beautifully.”
Winner of 17 first place awards.
Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
- 🇧🇷 Brazil
- 🇨🇦 Canada
- 🇨🇿 Czech Republic
- 🇩🇰 Denmark
- 🇫🇮 Finland
- 🇫🇷 France
- 🇩🇪 Germany
- 🇬🇷 Greece
- 🇭🇺 Hungary
- 🇮🇳 India
- 🇮🇪 Ireland
- 🇮🇱 Israel
- 🇮🇹 Italy
- 🇯🇵 Japan
- 🇱🇺 Luxembourg
- 🇲🇽 Mexico
- 🇳🇱 Netherlands
- 🇳🇿 New Zealand
- 🇳🇴 Norway
- 🇪🇸 Spain
- 🇸🇪 Sweden
- 🇨🇭 Switzerland
- 🇦🇪 UAE
- 🇬🇧 United Kingdom
- 🇺🇸 United States
About Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change
Thriving in today's marketplace frequently depends on making a transformation to become more agile. Those successful in the transition enjoy faster delivery speed and ROI, higher satisfaction, continuous improvement, and additional benefits.
Based on actual events, Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change provides a quick (60-90 minute) read about a successful agile transformation at a multinational entertainment and media company, told from the author's perspective as an agile coach.
The award-winning book by Scott M. Graffius is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
- 🇦🇺 Australia
- 🇦🇹 Austria
- 🇧🇷 Brazil
- 🇨🇦 Canada
- 🇨🇿 Czech Republic
- 🇩🇰 Denmark
- 🇫🇮 Finland
- 🇫🇷 France
- 🇩🇪 Germany
- 🇬🇷 Greece
- 🇮🇳 India
- 🇮🇪 Ireland
- 🇯🇵 Japan
- 🇱🇺 Luxembourg
- 🇲🇽 Mexico
- 🇳🇱 Netherlands
- 🇳🇿 New Zealand
- 🇪🇸 Spain
- 🇸🇪 Sweden
- 🇨🇭 Switzerland
- 🇦🇪 United Arab Emirates
- 🇬🇧 United Kingdom
- 🇺🇸 United States
© Copyright 2024 Scott M. Graffius. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without the express written permission of Scott M. Graffius.
Side-by-Side Comparison of Retrospectives and Hot Washes
18 November 2024
BY SCOTT M. GRAFFIUS | ScottGraffius.com
Participants at conferences and other events where Scott M. Graffius has delivered talks and workshops have sought clarity on the distinctions between retrospectives and hot washes. Particularly by those possibly in intelligence or military communities, the question has been asked with increasing frequency. Based on that, Graffius decided to develop this concise article.
Retrospectives (including post-project reviews) and hot washes are valuable practices for distilling actionable insights and enhancing future performance. But they serve distinct purposes and contexts including differences in timing and intent. Retrospectives are usually conducted at the end of an agile sprint or project, where the team reflects on what went well, what didn’t go well, and any changes to be implemented as improvements going forward. Hot washes happen immediately after a high-stakes event or operation to address real-time challenges and inform swift adjustments or decisions.
The visual shown at the top of this article provides a side-by-side comparison of retrospectives and hot washes including the typical characteristics and strategies unique to each. See the Permission Request Information section of this article if you'd like to request use of the copyrighted visual. If your request is approved, Graffius will give you an authorization/license and, if applicable, high-resolution files of the visual.
Here's the text from the visual:
Retrospectives
Hot Washes
Read on to see and learn:
About Scott M. Graffius
Scott M. Graffius is a global leader in agile project management, an expert on teamwork tradecraft, an authority on temporal dynamics on social media platforms, a creator, a consultant, a trainer, an award-winning author, and an international public speaker.
See his bio to learn more.
About Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions
Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive.
There are a variety of frameworks supporting the development of products and services, and most approaches fall into one of two broad categories: traditional or agile. Traditional practices such as waterfall engage sequential development, while agile involves iterative and incremental deliverables. Organizations are increasingly embracing agile to manage projects, and best meet their business needs of rapid response to change, fast delivery speed, and more.
With clear and easy to follow step-by-step instructions, Scott M. Graffius's award-winning Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions helps the reader:
Hailed by Literary Titan as “the book highlights the versatility of Scrum beautifully.”
Winner of 17 first place awards.
Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
About Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change
Thriving in today's marketplace frequently depends on making a transformation to become more agile. Those successful in the transition enjoy faster delivery speed and ROI, higher satisfaction, continuous improvement, and additional benefits.
Based on actual events, Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change provides a quick (60-90 minute) read about a successful agile transformation at a multinational entertainment and media company, told from the author's perspective as an agile coach.
The award-winning book by Scott M. Graffius is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
References/Sources
Permission Request Information
To request permission to use the visual shown at the top of this article, email Scott M. Graffius. If your request is approved, Graffius will give you an authorization/license and, if applicable, high-resolution files of the visual.
How to Cite This Article
Graffius, Scott M. (2024, November 18). Side-by-Side Comparison of Retrospectives and Hot Washes. Available at: https://scottgraffius.com/blog/files/retrospectives-and-hot-washes.html.
Post-Publication Notes
If there are any supplements or updates to this article after the date of publication, they will appear here.
Short Link for Article
The short link for this article is https://bit.ly/retro-hot
JPG | PNG
Copyright
Copyright © Scott M. Graffius. All rights reserved.
Content on this site—including text, images, videos, and data—may not be used for training or input into any artificial intelligence, machine learning, or automatized learning systems, or published, broadcast, rewritten, or redistributed without the express written permission of Scott M. Graffius.
Participants at conferences and other events where Scott M. Graffius has delivered talks and workshops have sought clarity on the distinctions between retrospectives and hot washes. Particularly by those possibly in intelligence or military communities, the question has been asked with increasing frequency. Based on that, Graffius decided to develop this concise article.
Retrospectives (including post-project reviews) and hot washes are valuable practices for distilling actionable insights and enhancing future performance. But they serve distinct purposes and contexts including differences in timing and intent. Retrospectives are usually conducted at the end of an agile sprint or project, where the team reflects on what went well, what didn’t go well, and any changes to be implemented as improvements going forward. Hot washes happen immediately after a high-stakes event or operation to address real-time challenges and inform swift adjustments or decisions.
The visual shown at the top of this article provides a side-by-side comparison of retrospectives and hot washes including the typical characteristics and strategies unique to each. See the Permission Request Information section of this article if you'd like to request use of the copyrighted visual. If your request is approved, Graffius will give you an authorization/license and, if applicable, high-resolution files of the visual.
Here's the text from the visual:
Retrospectives
- Also Known as: Post-project review, lessons learned meeting, post-mortem, sprint retrospective, project debriefing, project review
- Intent: Provide actionable insights for future projects or iterations
- Context: Project management (agile or otherwise) in technology or business
- Examples of Use Cases: Evaluating a sprint, project completion, or a product launch
- Participants: Scrum team or project team; sometimes others participate as well
- Scheduling: Scheduled in advance
- Timing: End of a sprint, project phase, or entire project
- Duration: 30-90 minutes
- Focus: Identifying successes, challenges, and changes to be made for future work
- Goal: Drive continuous improvement
- Strategy: Structured and reflective, use prompts (see Questions to Ask)
- Questions to Ask: What worked well? What didn’t? What should we change going forward?
- Facilitator Role: Scrum Master, project manager, or team leader
- Methods Employed: Retrospective frameworks, whiteboards, sticky notes, collaborative applications like Miro or Trello
- Documentation: Usually formal (written), with a report documenting findings and recommendations
- Emotional Tone: Fostering openness, introspection, and learning in a collaborative setting
Hot Washes
- Also Known as: Hot debrief, mission debrief, operational debrief, rapid debrief, tactical debrief, after-action review, immediate action review, post-event analysis
- Intent: Capture lessons while fresh and inform immediate adjustments or decisions
- Context: High-stakes operational settings such as intelligence, military, or emergency response
- Examples of Use Cases: Assessing a high-stakes intelligence operation or an emergency response
- Participants: Individuals involved in the immediate event or operation
- Scheduling: Not scheduled in advance; occurs as needed
- Timing: Immediately after an event, incident, mission, or exercise
- Duration: 15–30 minutes, focused on speed and efficiency
- Focus: Assessing immediate challenges and corrective actions required now
- Goal: Implement real-time changes as needed
- Strategy: Rapid, real-time, and conversational—focused on urgent issues
- Questions to Ask: What went wrong? What needs immediate attention? What actions should we take now?
- Facilitator Role: Team leader, mission commander, or operational lead
- Methods Employed: Quick debriefs, oral discussions, brief note-taking
- Documentation: Often informal (verbal), with key points summarized quickly for immediate use; there may or may not be a written report
- Emotional Tone: Urgent, action-oriented, and often high-energy
Read on to see and learn:
- About Scott M. Graffius,
- References/Sources,
- Permission Request Information,
- How to Cite This Article,
- and more.
About Scott M. Graffius
Scott M. Graffius is a global leader in agile project management, an expert on teamwork tradecraft, an authority on temporal dynamics on social media platforms, a creator, a consultant, a trainer, an award-winning author, and an international public speaker.
See his bio to learn more.
About Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions
Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive.
There are a variety of frameworks supporting the development of products and services, and most approaches fall into one of two broad categories: traditional or agile. Traditional practices such as waterfall engage sequential development, while agile involves iterative and incremental deliverables. Organizations are increasingly embracing agile to manage projects, and best meet their business needs of rapid response to change, fast delivery speed, and more.
With clear and easy to follow step-by-step instructions, Scott M. Graffius's award-winning Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions helps the reader:
- Implement and use the most popular agile framework―Scrum;
- Deliver products in short cycles with rapid adaptation to change, fast time-to-market, and continuous improvement; and
- Support innovation and drive competitive advantage.
Hailed by Literary Titan as “the book highlights the versatility of Scrum beautifully.”
Winner of 17 first place awards.
Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
- 🇧🇷 Brazil
- 🇨🇦 Canada
- 🇨🇿 Czech Republic
- 🇩🇰 Denmark
- 🇫🇮 Finland
- 🇫🇷 France
- 🇩🇪 Germany
- 🇬🇷 Greece
- 🇭🇺 Hungary
- 🇮🇳 India
- 🇮🇪 Ireland
- 🇮🇱 Israel
- 🇮🇹 Italy
- 🇯🇵 Japan
- 🇱🇺 Luxembourg
- 🇲🇽 Mexico
- 🇳🇱 Netherlands
- 🇳🇿 New Zealand
- 🇳🇴 Norway
- 🇪🇸 Spain
- 🇸🇪 Sweden
- 🇨🇭 Switzerland
- 🇦🇪 UAE
- 🇬🇧 United Kingdom
- 🇺🇸 United States
About Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change
Thriving in today's marketplace frequently depends on making a transformation to become more agile. Those successful in the transition enjoy faster delivery speed and ROI, higher satisfaction, continuous improvement, and additional benefits.
Based on actual events, Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change provides a quick (60-90 minute) read about a successful agile transformation at a multinational entertainment and media company, told from the author's perspective as an agile coach.
The award-winning book by Scott M. Graffius is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.
- 🇦🇺 Australia
- 🇦🇹 Austria
- 🇧🇷 Brazil
- 🇨🇦 Canada
- 🇨🇿 Czech Republic
- 🇩🇰 Denmark
- 🇫🇮 Finland
- 🇫🇷 France
- 🇩🇪 Germany
- 🇬🇷 Greece
- 🇮🇳 India
- 🇮🇪 Ireland
- 🇯🇵 Japan
- 🇱🇺 Luxembourg
- 🇲🇽 Mexico
- 🇳🇱 Netherlands
- 🇳🇿 New Zealand
- 🇪🇸 Spain
- 🇸🇪 Sweden
- 🇨🇭 Switzerland
- 🇦🇪 United Arab Emirates
- 🇬🇧 United Kingdom
- 🇺🇸 United States
References/Sources
- Abel-Hamid, T.K., & Madnick, S.E. (1990, Fall). The Elusive Silver Lining: How We Fail to Learn from Software Development Failures. Sloan Management Review, Fall 1990: 39-48.
- Agile Alliance (n.d.). Heartbeat Retrospective. Available at: https://www.agilealliance.org/glossary/heartbeat-retrospective.
- AgileScrumGuide.com (2017, August 21). Side-by-Side Comparisons of Agile Scrum and Waterfall Models: A Quick Look at Integration Management. Available at: https://agilescrumguide.com/blog/files/Side-by-Side-Comparisons-of-Agile-Scrum-and-Waterfall-Models-A-Quick-Look-at-Integration-Management.html.
- AgileScrumGuide.com (2017, August 24). Side-by-Side Comparisons of Agile Scrum and Waterfall Models: A Quick Look at Communications Management. Available at: https://agilescrumguide.com/blog/files/Side-by-Side-Comparisons-of-Agile-Scrum-and-Waterfall-Models-A-Quick-Look-at-Communications-Management.html.
- AgileScrumGuide.com (2017, August 7). Side-by-Side Comparisons of Agile Scrum and Waterfall Models: A Quick Look at Quality Management. Available at: https://agilescrumguide.com/blog/files/Side-by-Side-Comparisons-of-Agile-Scrum-and-Waterfall-Models-A-Quick-Look-at-Quality-Management.html.
- Amsterdam Public Health Research Institute (2021). APH Quality Handbook. Amsterdam: Amsterdam Public Health Research Institute.
- Bellet, C., De Neve, J., & Ward, G. (2019 October 14). Does Employee Happiness Have an Impact on Productivity? Saïd Business School WP 2019-13. Oxford, UK: Oxford University.
- Bennett, M., Gadlin, H., & Marchand, C. (2018). Collaboration Team Science: Field Guide. Rockville, MD: National Institutes of Health.
- Boddie, J. (1989, December 7). The Project Postmortem. Computerworld.
- Carn-Bennett, Erin (2024, June 19). Using the Army’s Hot Wash Debrief Technique in Civilian Healthcare Simulation. Available at: https://www.healthysimulation.com/healthcare-simulation-hot-wash-debrief/.
- Cassell, Greg (2024, September 20). IAFC Releases New “Hot Wash” For Major Incidents and Training Exercises. Available at: https://www.iafc.org/blogs/blog/iafc/2024/09/23/iafc-releases-new-hot-wash-for-major-incidents-and-training-exercises.
- Coleman, Stan (2009. November 25). Hot Wash—A Tool For Feedback. Available at: https://www.dobbins.afrc.af.mil/News/Article-Display/Article/171803/hot-wash-a-tool-for-feedback/.
- Collier, B, DeMarco, T., & Fearey, P. (1996, July), A Defined Process for Project Post Mortem Review. IEEE Software, 13 (4): 65-72.
- Creately (2024, August 23). After Action Review: What is it and How to Use it to Improve Team Performance. Available at: https://creately.com/guides/after-action-review/.
- DevOps Institute (2021). 2021 Upskilling Enterprise DevOps Skills Report. Boca Raton, FL: DevOps Institute.
- Exceptional Agility (2023, January 1). Making Teams More Agile: Strategies and Benefits. Available at: https://exceptionalagility.com/blog/files/teams.html.
- Farr, J. V., & Brazil, D. M. (2012, September 5). Leadership Skills Development for Engineers. IEEE Engineering Management Review, 40 (3): 13-22.
- Fletcher, Angus; Cline, Preston B.; & Hoffman, Matthew (2023, January 12). A Better Approach to After-Action Reviews. Harvard Business Review. Available at: https://hbr.org/2023/01/a-better-approach-to-after-action-reviews.
- GitLab (2019, December 13). Strengthen Your Agile Teams with Tuckman's Stages of Group Development. At: about.gitlab.com. San Francisco, CA: GitLab, Inc.
- Graffius, Scott M. (2016, January 21). 2014 NSDM Publication on Leadership by National Security Affairs Professor Mary Raum Featured the 2008 Edition of Scott M. Graffius’ Work on Team Development. Available at: https://scottgraffius.com/blog/files/nsdm-leadership.html. DOI: 10.13140/RG.2.2.22276.33920.
- Graffius, Scott M. (2016). Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions. North Charleston, SC: CreateSpace.
- Graffius, Scott M. (2018, August 25). Retrospectives and Continuous Improvement in the Agile Scrum Framework [Workshop]. Session at private event in Las Vegas, NV. 10.13140/RG.2.2.16620.51843
- Graffius, Scott M. (2018, October 18). Agile Scrum Helps Innovators, Disruptors, and Entrepreneurs Develop and Deliver Products at Astounding Speed Which Drives Competitive Advantage [Presentation]. Talk delivered at Techstars Startup Week Conference. DOI: 10.13140/RG.2.2.25009.12647.
- Graffius, Scott M. (2019). Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change. Scotts Valley, CA: CreateSpace.
- Graffius, Scott M. (2021, February 20). But First, the Team! [Presentation]. Talk delivered at the Brno, Czech Republic DevConf.CZ 2021 Conference. Digital Object Identifier (DOI): 10.13140/RG.2.2.29016.72964.
- Graffius, Scott M. (2021, June 21). DevOps and Team Leadership [Workshop]. Session at private event in Las Vegas, NV. DOI: 10.13140/RG.2.2.15380.22401.
- Graffius, Scott M. (2021, May 13). But First, the Team! [Presentation]. Lecture delivered at DevOps Pro Europe 2021 Conference. Based and simulcast live from Vilnius, Lithuania. DOI: 10.13140/RG.2.2.30524.36481.
- Graffius, Scott M. (2021, November 10). An Error Was Introduced Into the Seventh Edition of 'A Guide to the Project Management Body of Knowledge (PMBOK).’ Los Angeles, CA: Scott M. Graffius.
- Graffius, Scott M. (2021, November 8). Bruce Tuckman’s Model (Forming, Storming, Norming, Performing, and Adjourning) is Highly Relevant and Beneficial, But It Doesn’t Please Everyone. Los Angeles, CA: Scott M. Graffius.
- Graffius, Scott M. (2021, October 5). Navigate the Phases of Team Development with Speed and Agility for Happier and More Productive Teams [Presentation]. Talk delivered at the Institute of Electrical and Electronics Engineers IEEE Day 2021 Conference. Digital Object Identifier (DOI): 10.13140/RG.2.2.20055.19365.
- Graffius, Scott M. (2022, February 4). Team Development Tradecraft: A Source of Competitive Advantage [Workshop]. Session at private event in Adelaide, Australia. DOI: 10.13140/RG.2.2.14092.80002.
- Graffius, Scott M. (2022, May 13). Want Happier and More Productive DevOps Teams? [Presentation]. Talk delivered at DevOpsDays Geneva, Switzerland 2022 Conference. Digital Object Identifier (DOI): 10.13140/RG.2.2.22252.85127.
- Graffius, Scott M. (2023, April 26). The Science of High-Performance Teams [Presentation]. Talk delivered at the DevOps Institute’s SKILup Day 2023 Conference. Digital Object Identifier (DOI): 10.13140/RG.2.2.15888.28169.
- Graffius, Scott M. (2023, July 15). Successful Video Game Development Teams Leverage an Extensive Range of Hard Skills and Soft Skills. Available at: https://scottgraffius.com/blog/files/gamedev.html.
- Graffius, Scott M. (2023, June 29). What Successful AI Teams Have in Common [Presentation]. Talk delivered at Conf42 Quantum Computing 2023 Conference. Digital Object Identifier (DOI): 10.13140/RG.2.2.29382.45120.
- Graffius, Scott M. (2023, May 1). Fueling the Development of Innovative and Life-Changing AI Solutions [Presentation]. Talk delivered to an audience of Technology professionals (including Data Scientists, Machine Learning Engineers, Data Engineers, AI Researchers, Project Managers, Business Analysts, UX Designers, Software Developers, Cloud Architects, Data Privacy and Security Specialists, and others involved or interested in AI) at a private event in Mountain View, California, United States. Digital Object Identifier (DOI): 10.13140/RG.2.2.27956.73601.
- Graffius, Scott M. (2024, January 8). Scott M. Graffius’ Phases of Team Development: 2024 Update. Available at: https://scottgraffius.com/blog/files/teams-2024.html. DOI: 10.13140/RG.2.2.28629.40168.
- Graffius, Scott M. (2024, July 16). Consider Asking and Answering These Questions at Your Next Retrospective, Post Project Review or Debrief Meeting (But Not a "Hot Wash"). Available at: https://x.com/ScottGraffius/status/1813233611212222578.
- Helgesen, Sally (2022, June 8). How Wash, Cold Wash. Available at: https://allrise.substack.com/p/hot-wash-cold-wash.
- Jovanovic, M., Mesquida, A., Radaković, N., & Mas, A. (2016). Agile Retrospective Games for Different Team Development Phases. Journal of Universal Computer Science, 22: 1489-1508.
- Kerzner, Harold (2022). Innovation Project Management: Methods, Case Studies, and Tools for Managing Innovation Projects (Second Edition). Hoboken, NJ: Wiley.
- Luckner, M. (2020, November 18). Data Science Workshop (Version 1.1). Warsaw, Poland: Warsaw University of Technology.
- Microsoft (2019, June 15). Is the Latest Technology the Key to Your Team’s Success, or is There Something Else? Microsoft Developer Support. Accessed at: https://devblogs.microsoft.com/premier-developer/is-the-latest-technology-the-key-to-your-teams-success-or-is-there-something-else. Redmond, WA: Microsoft.
- Project Management Institute (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition. Newtown Square, PA: Project Management Institute.
- Raum, Mary (2014, April 10). Leader Theory Explanations and Original Texts. Newport, RI Naval War College. NSDM.
- Rowley, D., & Lange, M. (2007). Forming to Performing: The Evolution of an Agile Team. IEEE Computer Society Proceedings. Agile 2007, 1: 408-414.
- Salas, E., Grossman, R., Hughes, A.M., and Coultas, C.W. (2015), Measuring Team Cohesion: Observations from the Science. Human Factors, 57 (3): 365–374.
- Scaled Agile, Inc. (2023, March 14). Working Successfully in Agile with Remote Team Members. Available at: https://scaledagileframework.com/working-successfully-in-agile-with-remote-team-members/.
- Scrum Alliance (2020). Learning Objectives Examples. Denver, CO: Scrum Alliance.
- Scrum Alliance (n.d.). The Sprint Retrospective. Available at: https://resources.scrumalliance.org/Article/sprint-retrospective.
- Sutherland, Rory (2019). Alchemy: The Dark Art and Curious Science of Creating Magic in Brands, Business, and Life. New York, NY: William Morrow and Company, an imprint of HarperCollins.
- Tuckman, Bruce W. (1965). Developmental Sequence in Small Groups. Psychological Bulletin, 63: 384-399.
- Tuckman, Bruce W., & Jensen, M. A. C. (1977). Stages of Small-Group Development Revisited. Group and Organizational Studies, 2 (4): 419-427.
- United States Army (2015). Innovative Learning: A Key to National Security. Washington, DC: United States Army.
- United States General Services Administration, Office of the CTO (2021). GSA Tech Guides: Establishing an Agile Team Working Agreement. Washington, D.C.: United States General Services Administration.
- University of Waterloo (2021). SE Capstone Design Project Handbook. Edited by Derek Rayside. Waterloo, Ontario, Canada: University of Waterloo.
- Williams, T., Eden, C., Ackermann, F., Howick, S., Bergamini, V., Daley, A., & Gill, K. (2001, November). The Use of Project Post-Mortems. Paper presented at Project Management Institute Annual Seminars & Symposium, Nashville, TN. Newtown Square, PA: Project Management Institute.
- Yahoo News (2021, August 17). National Security Adviser Calls for a 'Hot Wash' to Review U.S. Withdrawal from Afghanistan. Available at: https://www.yahoo.com/news/national-security-adviser-calls-hot-191627245.html.
- Yu, Shuo; Bedru, Hayat Dino; Lee, Ivan Lee; and Xia, Feng (2019, February). Science of Scientific Team Science. Computer Science Review, 31: 72-83. DOI: 10.1016/j.cosrev.2018.12.001.
Permission Request Information
To request permission to use the visual shown at the top of this article, email Scott M. Graffius. If your request is approved, Graffius will give you an authorization/license and, if applicable, high-resolution files of the visual.
How to Cite This Article
Graffius, Scott M. (2024, November 18). Side-by-Side Comparison of Retrospectives and Hot Washes. Available at: https://scottgraffius.com/blog/files/retrospectives-and-hot-washes.html.
Post-Publication Notes
If there are any supplements or updates to this article after the date of publication, they will appear here.
Short Link for Article
The short link for this article is https://bit.ly/retro-hot
JPG | PNG
Copyright
Copyright © Scott M. Graffius. All rights reserved.
Content on this site—including text, images, videos, and data—may not be used for training or input into any artificial intelligence, machine learning, or automatized learning systems, or published, broadcast, rewritten, or redistributed without the express written permission of Scott M. Graffius.