QA Report Guidelines
REPORT OUTLINE
- Summary. Summarize background, evaluation results, and recommendations.
- Background Information. Include the what, when, scope, objectives of the review, and any other supporting data. Include QA activities (planned to actual).
- Evaluation Result. Include significant information only, from the perspective of the reader. If the findings were all good, say that. Reports should cover good news, and not just exist to give bad news.
- Recommendations. Note whether the team already has agreed to implement any of the recommendations, so recipient knows whether there are any unresolved issues. Include the effect of the recommendations on resources, whether the cost of implementing the recommendations (labor hours, people), and project implications.
- Appendixes. Include information that supports the findings and is potentially valuable but not essential to the recipient.
- The QA report provides the necessary information from the perspective of all classes of recipients. The following text describes the classes of recipients.
RECIPIENT: PROJECT TEAM
- Viewpoint
- Responsible for delivery of the product or services
- Project management objectives
- Responsible for resolving noncompliance issues
- Level of detail (Section 2, Background)
- Summarize by process, product, or service
- Single out groups for positive recognition
- Projected attainment of project goals
- Feedback (Section 3, Evaluation Results
- Team experience with the process and products
- May be affected by changes to the procedures/standards
- More enthusiastic about their own recommendations
- Frame recommendations (Section 4, Recommendations)
- What's in it for Me (WIIFM) - productivity with improved quality, positive impact on project cost and schedule
RECIPIENT: PROGRAM MANAGER
- Viewpoint
- Responsible for cost, schedule, and delivery of several projects
- Spread success among projects
- Level of detail (Section 2)
- Project summary
- Process, service, product summary across projects
- Consequences of results on program objectives
- Incorporate agreement of recommendations already agreed upon.
- Identify unresolved issues - and reasons for disagreement.
- Feedback (Section 3)
- Program perspective
- Frame recommendations (Section 4)
- Program objectives, project goals
RECIPIENT: SENIOR MANAGEMENT
- Viewpoint
- Responsible for cost, schedule, and delivery of products and services across the organization
- Level of detail (Section 2)
- Highlight areas of interest and concern.
- Make recommendations specific to projects, program, and organization. Take advantage of success.
- Incorporate recommendations already agreed upon.
- Identify unresolved issues and reasons for disagreement.
- Feedback - Business objectives and long-term strategies (Section 3)
- Frame recommendations (Section 4)
- Organizational improvements to productivity, efficiency, etc.
RECIPIENT: PRODUCT OWNER/ACQUIRER
- Viewpoint
- Oversee QA activities, planned to actual.
- Attainment of quality goals
- Level of detail (Section 2)
- Summarize by process, product, or service.
- Single out groups for positive recognition.
- Projected attainment of project goals
- Feedback (Section 3)
- Provide direction/assistance/approval.
- Frame recommendations (Section 4)
- Ability to meet project QA goals

