Elicit Needs
Elicit stakeholder needs, expectations, constraints, and interfaces
for all phases of the product life cycle.
Eliciting goes beyond collecting requirements by proactively identifying
additional requirements not explicitly provided by customers. Additional
requirements should address the various product life-cycle activities
and their impact on the product.
Examples of techniques to elicit needs include:
- 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)
- Engage relevant stakeholders using methods for eliciting needs,
expectations, constraints, and external interfaces.