Elicit stakeholder needs, expectations, constraints, and interfaces for all phases of the product lifecycle.
Eliciting goes beyond collecting requirements by proactively identifying additional requirements not explicitly provided by customers. Additional requirements should address the various product lifecycle activities and their impact
on the product.
Examples of techniques to elicit needs include the following:
· Technology demonstrations
· Interface control working groups
· Technical control working groups
· Interim project reviews
· Questionnaires, interviews, and operational scenarios obtained from end users
· Operational walkthroughs and end-user task analysis
· Prototypes and models
· Brainstorming
· Quality Function Deployment
· Market surveys
· Beta testing
· Extraction from sources such as documents, standards, or specifications
· Observation of existing products, environments, and workflow patterns
· Use cases
· Business case analysis
· Reverse engineering (for legacy products)
· Customer satisfaction surveys
Examples of sources of requirements that might not be identified by the customer include the following:
· Business policies
· Standards
· Business environmental requirements (e.g., laboratories, testing and other facilities, and information technology infrastructure)
· Technology
· Legacy products or product components (reuse product components)
Subpractices
1. Engage relevant stakeholders using methods for eliciting needs, expectations, constraints, and external interfaces.