A-Z Popular Blog Projects Search »
Business Analysis
Related Guides
Related Topics

9 Examples of Requirements Gathering

 , updated on
Requirements gathering is the process of eliciting requirements from stakeholders and refining their quality. Early stage requirements gathering is focused on stimulating creative ideas. The middle stage is about adding assumptions and constraints to focus on the core value of your project or initiative. Late stage requirements gathering involves resolving inconsistencies and getting working prototypes in front of stakeholders. The following are common examples of requirements gathering.


Requirements gathering begins with a kickoff meeting that explains an initiative to stakeholders including elements such as a business case and mission statement.


At first, some stakeholders may have few ideas. Brainstorming is a common early stage technique that encourages people to throw out the first ideas that come to mind.


Interviews led by a business analyst that are designed to explore requirements.

User Stories

Asking users to state their expectations for the project in the format "As a role, I'd like to capability, so that I can goal". For example, as a manager I'd like to be able to reassign tasks so that I can manage employee absences.

Business Rules

Asking users to document business rules. For example, "if a customer leaves their session idle for 30 minutes then their session expires."

Non-Functional Requirements

Non-functional requirements in areas such as design, infrastructure, architecture and technology may be contributed by a variety of subject matter experts. The example, "The site shall use brand colors according to the brand style guide."


Meetings that work through open questions and issues. For example, requirements may be inconsistent or infeasible.


Getting stakeholders using simulations or working prototypes tends to lead to better requirements. Stakeholders often have new ideas when they see things implemented.

Requirements Management

The ongoing process of prioritizing, maintaining and refining requirements. In order to reduce project risk, it is common to implement a small number of requirements in short release cycles. In this case, requirements are viewed as a backlog that may grow with time. This can be a positive thing as it allows all ideas to be captured while only implementing the best ideas you have for each implementation cycle.
Overview: Requirements Gathering
The process of eliciting requirements from stakeholders and refining their quality.
Related Concepts

Business Analysis

This is the complete list of articles we have written about business analysis.
Audience Analysis
Behavioral Requirements
Best In Class
Black Box
Brand Analysis
Budget Planning
Business Analysis
Business Architecture
Business Attributes
Business Case
Business Conditions
Business Models
Business Needs
Business Needs Analysis
Business Plan
Business Requirements
Business Rules
Business Strategy
Business Swot
Business Theory
Capacity Planning
Choice Architecture
Competitive Intelligence
Context Of Use
Cost Benefit Analysis
Success Factors
Data Analysis
Data Dredging
Data Mining
Decision Analysis
External SWOT
Feasibility Analysis
Fishbone Diagram
Gap Analysis
Ishikawa Diagrams
Management Accounting
Market Research
Needs Analysis
Net Present Value
Operations Analysis
Organizing Principle
Pain Points
Performance Analysis
Problem Analysis
Productivity Analysis
Project Charter
Proof Of Concept
Qualitative Analysis
Requirements Gathering
Scenario Planning
Situation Analysis
Statement Of Work
Statistical Analysis
Story Points
Strategic Drivers
SWOT Analysis
Technology Analysis
Terms Of Reference
Total Cost Of Ownership
Use Case
User Stories
Voice Of The Customer
What-if Analysis
Workflow Analysis
If you enjoyed this page, please consider bookmarking Simplicable.


The common types and formats of requirements.

Functional vs Non-functional

The difference between functional and non-functional requirements explained.

Requirements vs Specifications

The difference between requirements and specifications.

Functional vs Behaviorial

The difference between functional and behavioral requirements explained.

Non-Functional Requirements

A few examples of non-functional requirements.

Requirements Traceability

A definition of requirements traceability with examples.

Customer Requirements

The common types of customer requirements.

Function vs Feature

The difference between functions and features.

Requirements Elicitation

The common types of requirements elicitation.

Requirements Management

A definition of requirements management with examples.

Needs Analysis

The common types of needs analysis.

Business Analysis

A list of business analysis techniques and deliverables.

Business Analysis vs Business Architecture

The difference between business analysis and business architecture.

Process Gaps

A few examples of common process gaps.

Best In Class

A definition of best in class with examples.

Data Analysis

The common types of data analysis.

Technical Feasibility

Common types of technical feasibility.


The common types of specification.
The most popular articles on Simplicable in the past day.

New Articles

Recent posts or updates on Simplicable.
Site Map