In each case, the authors are selling their own approach to software development, so the reader's enthusiasm has to be moderated by a certain amount of scepticism. All the same, some of their points make good sense, and could probably be introduced into Moose with advantage. The Gilb and Graham book seems to be directed at groups who want to introduce inspections into their software development process. It is probably aimed largely at the group leader, since management backing is essential for success. The authors provide detailed descriptions of the phases of an inspection, the documents that are required, the roles of the various people involved, and the actions to be taken.
Inspections work on two levels.
Firstly and obviously, the document being inspected is improved in quality. For example, statistics of the types of faults that are found can suggest reasons why certain faults occur, and indicate improvements like better training for programmers or clearer documentation. However, much, if not most, of this material is relevant for group working. There are some quite useful suggestions, like design notations or checklists for finding programming faults. The control of the software development process is more formally statistical than in Gilb and Graham, and is probably only appropriate in the context of an organization where a dedicated quality control group exists.