The Short Story
As stated in the IPAR topic, sometimes you'll have to produce an External PARs (document) to be delivered to the customer (in PDF format).Why is that? Isn't this duplicating work? Yes and no.
Remember that it could be counter-productive to disclose all information being collected in the Internal PAR, or that the customer can have template / specific standard requirements that will make him ask for that extra deliverable (see the Proposal/Contract for the specific project).
The Long Story (TOC)
Example TOC for External QA Reports (External PARs):- Planning documentation progress status
- Development activities status
- Modules / Components development progress
- Code Metrics
- Verification activities status
- Completeness / correctness statistics for Code reviews, Module Testing, Integration Testing
- QA activities status
- Reports, CM check-ups, On-process (SPA Log Book), etc.
- Summary of CAs / NCs status
- Activities / Actions to be performed before the next report
