Environments Evaluation Team

Definition

Environments Evaluation Team

the team that performs one or more technical evaluations of the the deliverable environments work products and the environments engineering process by which they are produced

Classification

As illustrated in the preceding figure, Environments Evaluation Team is part of the following inheritance hierarchy:

• Type: Concrete
• Superclass: Evaluation Team
• Subclasses:
  • None

Responsibilities

The typical team-specific responsibilities of an Environments Evaluation Team are to:

• Inspect the deliverable environments work products including (but not limited to) the:
  • Documents:
    • Project Environments Description Document
    • Product Selection Report
  • Environments:
    • Development Environments:
      • Reuse Environment
      • Engineering Environment
      • Multimedia Environment
      • Integration Environment
      • Test Environment
      • Staging Environment
    • Production Environments:
      • Client Environment
      • Contact Center Environment
      • Content Management Environment
      • Data Center Environment
• Notify the environments team of any defects found.
• Recommend improvements to the endeavor process including (but not limited to) the:
  • Environments engineering activities and tasks.
  • Standards, templates, and evaluation checklists for the deliverable environments work products.

The environments evaluation team typically inherits general team responsibilities from the team method component.

Roles

The environments evaluation team typically consists of persons playing the following roles:

• Technical Leader, who facilitates the evaluation meeting and evaluates the environments for technical quality.
• Customer Representative, who evaluates the production environment for acceptability.
• Requirements Engineer, who evaluates the production environment for conformity to the requirements.
• System Architect, who evaluates the integration, test, and production environments for conformity to the system architecture.
• Integration Engineer, who evaluates the integration environment for usability.
• Software Designer, who evaluates the development environment for usability.
• Hardware Engineer, who evaluates the environments for implementability.
• Programmer, who evaluates the development environment for usability.
• Security Engineer, who evaluates the environments for compliance with the security requirements and architecture.
• Test Engineer, who evaluates the test environment for usability.
• Quality Engineer, who evaluates the work products for quality and conformance to the endeavor process and relevant conventions.
• Technical Writer,
  • Acts as scribe at the evaluation meeting(s).
  • Summarizes the evaluation team’s findings in the evaluation summary report.
  • Delivers the evaluation summary report to the:
    • Environments Team.
    • Management Team.
    • Quality Team.

Tasks

The environments evaluation team typically performs the following team-specific tasks in an incremental, iterative, parallel, and time-boxed manner:

• Quality Engineering:
  • Quality Control - Environments Evaluation
    Evaluate the environments engineering work products
  • Quality Assurance - In-Progress Review
    Audit the environments engineering process regarding:
    • The environments engineering activity, work flows, tasks, and techniques.
    • The standards, templates, and evaluation checklists for the environments engineering work products.

The environments engineering evaluation team typically inherits the common team tasks from the team method component.

Work Products

The environments engineering evaluation team typically produces the following work products:

• Quality Set:
  • Evaluation Report, which documents an individual evaluator’s findings.
  • Evaluation Summary Report, which summarizes the finding of the entire evaluation team.

Guidelines

• Evaluations should not devolve into walkthroughs that require the work products’ developers to explain them to the evaluators. The work products should stand on their own.
• To the extent practical, the developers of a work product should:
  • Not be the only evaluators of it.
  • Also informally inspect it prior to the evaluation.
• A single person may play multiple roles on an evaluation team if he or she has the necessary expertise to fulfill multiple roles. This is especially true on small endeavors.
• An environments engineering evaluation team typically inherits the common team guidelines from the team method component.