A system design review can need 150 hours of work.

          One frequently overlooked area in planning is technical reviews and inspections. A technical review requires substantial preparation on the part of the presenters. Documents must be published and distributed and presentation material organized and made into slides or overheads. Practice sessions are conducted by presenters with an audience of critics to prepare for the review.
              The reviewers should read the material, attend the presentations, and write reports. On large projects with many reviews and walk-throughs involving many participants, a substantial number of labor hours can be consumed analyzing documents, attending meetings, and writing reports. For example, a system design review for one module or unit can require 150 labor hours. When overlooked, this labor can result in a very large error in resource and schedule estimation.
          Many projects include risk assessment and risk management as a key part of the planning process and expect the plan to identify specific risk areas. The plan is expected to quantify both probability of failure and consequences of failure and to describe what will be done to contain development risk.
                                 A. Behforooz and F. Hudson. Software engineering fundamentals. Ed. Oxford (adapted).

Based on the text above, judge the following items.