Select Product for Validation (User Story)


Select products and product components t be validated and validation methods to be used.


Quantitatively manage the project’s defined process to achieve the established quality objectives for the product being developed.


Products and product components are selected for validation based on their relationship to end user needs. For each product component, the scope of the validation (e.g., operational behavior, maintenance, training, user interface) should be determined.  Examples of products and product components that can be validated include the following:

    • Product and product component requirements and designs
    • Product and product components (e.g., system, hardware units, software, service
    • User interfaces
    • User manuals
    • Training materials
    • Process documentation
      Access protocols
    • Data interchange reporting formats

The requirements and constraints for performing validation are collected. Then, validation methods are selected based on their ability to demonstrate that end user needs are satisfied. The validation methods not only define the approach to product validation, but also drive the needs for the facilities, equipment, and environments. The validation approach and needs can result in the generation of lower level product component requirements that are handled by the requirements development processes. Derived requirements, such as interface requirements to test sets and test equipment, can be generated. These requirements are also passed to the requirements development processes to ensure that the product or product components can be validated in an environment that supports the methods.

Validation methods should be selected early in the life of the project so they are clearly understood and agreed to by relevant stakeholders.  Validation methods address the development, maintenance, support, and training for the product or product component as appropriate.

Examples of validation methods include the following:

    • Discussions with end users, perhaps in the context of a formal review
    • Prototype demonstrations
    • Functional demonstrations (e.g., system, hardware units, software, service documentation, user interfaces)
    • Pilots of training materials
    • Tests of products and product components by end users and other relevant stakeholders
    • Incremental delivery of working and potentially acceptable product
    • Analyses of product and product components (e.g., simulations, modeling, user

Hardware validation activities include modeling to validate form, fit, and function of mechanical designs; thermal modeling; maintainability and reliability analysis; timeline demonstrations; and electrical design simulations of electronic or mechanical product components.


  • Project Charter baseline has been communicated
  • Project Manager is trained on the  processes and Statistical Process Control (SPC) techniques
  • Process Performance Management Plan contains the process performance objectives
  • Process Performance Model based on the past data is established and is approved for usage in the IO organization.


  • Documented Product Quality Plan shall be integrated into Project Plan before reviewing the Project Plan..
  • Project quantitative goals set as per process performance capabilities


  • Product Quality Plan
  • Statistical Process Control Guidelines
  • Process Performance Process

Task Instructions:

Set Project Performance Objectives

    1. Using the <?>, [the ?] with support from <?> is responsible for

Derive Objectives for Life Cycle Phases

    1. Using the <?>, [the ?] with support from <?> is responsible for

Identify Sub-Processes for Performance Objectives

    1. Using the <?>, [the ?] with support from <?> is responsible for

Review and Understand Current Process Performance Capabilities

    1. Using the <?>, [the ?] with support from <?> is responsible for