commit fa1fd432ec597bd9c488cad02a5e9a4ddbd70bf9
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Fri Mar 10 08:41:41 2023 -0500

    Updates

diff --git a/background-rw.md b/background-rw.md
index 0e9cf94..a12ac49 100644
--- a/background-rw.md
+++ b/background-rw.md
@@ -1,6 +1,6 @@
 ---
 pagetitle: Writing the Background/Related Work
-version: 1.1
+version: 1.2
 ---
 
 # Writing the Background/Related Work
@@ -38,9 +38,26 @@ organization. The layout and structure of the chapter is a
 contribution of your report.  It represents a unique view of other
 work/technology from your vantage point.
 
+A good approach to tackling the related work is to:
+
+1) Gather resources (blogs and websites and especially peer-reviewed
+papers). Cast a wide net initially, but then narrow down as you get a
+better sense of relevancy.  Read appropriate work in detail and
+summarize with notes.
+
+2) Organize into groups based on similarities.  These groups likely
+become sub-sections in your chapter.  Place them in an outline.
+
+3) Provide a summary of the works in the outline.  Typically: what is
+the approach, what were the methods, what did they find.  Make sure to
+explicitly state the relevance of the work to *your* project. This
+doesn't have to be done for each paper but can be at the end of a
+subsection.
+
 Figures taken from your cited sources are allowed (and often make the
 chapter much better), but should also be cited in the figure caption.
 
 Since nearly all the information in Background and Related Work is
 external, it needs to be cited, accompanied by an entry in the
 References section of the report.
+